emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Dates in headlines
Date: Sat, 28 Jan 2023 15:12:27 +0700	[thread overview]
Message-ID: <tr2ldc$77n$1@ciao.gmane.io> (raw)

On 19/08/2022 12:58, Ihor Radchenko wrote:
> Ypo writes:
> 
>> I found it again:
>>
>> "If the headline contains a timestamp, it is removed from the link,
>> which results in a wrong link—you should avoid putting a timestamp in
>> the headline."
>>
>> https://orgmode.org/manual/Handling-Links.html#FOOT28
> 
> Unless I miss something, this footnote is plain wrong. The timestamps
> are not removed. At least not when I run M-x org-store-link on a
> headline with timestamp with emacs -Q.

I have realized that "first wins" parsing principle (consider +a =b+ 
c*d=) may mean a problem for timestamp at the end of link text. So

     [[file:test.txt][Test [2023-01-28 Sat]]]

requires a zero-width space after the bracket closing the timestamp. The 
same is applicable to fuzzy link to headings. So either

     [[*Heading \[2023-01-28 Sat\]][Heading [2023-01-28 Sat]​]]
ZWS in between--------------------------------------------^^

or

     [[*Heading \[2023-01-28 Sat\]]]

should be used. `org-insert-link' handles it correctly, but when typing 
links from keyboard, users should be aware of such kind of pitfall. So 
timestamps in headings may be source of some inconvenience.

May it happen that in some old Org version timestamps at the end of 
headings were removed due by code intended to handle statistics cookie 
[1/10]?



             reply	other threads:[~2023-01-28  8:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28  8:12 Max Nikulin [this message]
2023-02-02 20:37 ` Dates in headlines Ihor Radchenko
2023-07-14 12:57   ` Max Nikulin
2023-07-18  9:24     ` Ihor Radchenko
2023-07-19 16:27       ` Max Nikulin
  -- strict thread matches above, loose matches on Subject: below --
2022-08-16 17:45 Ypo
2022-08-19  5:58 ` Ihor Radchenko
2022-06-28  9:06 Ypo
2022-06-28 21:13 ` Jean Louis
2022-06-28 23:23 ` Samuel Wales
2022-06-29 18:11   ` Ypo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='tr2ldc$77n$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).