From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Re: "# <<tag>>" should stick to the following text
Date: Sun, 06 May 2012 20:41:13 -0400 [thread overview]
Message-ID: <86wr4orffa.fsf@mercure.progiciels-bpi.ca> (raw)
In-Reply-To: <87397dgg9a.fsf@gmail.com> (Nicolas Goaziou's message of "Sun, 06 May 2012 23:18:41 +0200")
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> "# <<tag>>" is a deprecated construct.
Sigh! I just spent a few hours adding many of those and making sure
everything is regular.
When some feature is being deprecated, the Org manual should tell us,
then ! :-) And at least where that feature is documented. Currently,
the manual says:
The preferred match for a text link is a dedicated target: the same
string in double angular brackets.
This is not ultra clear to me, my English is not ultra solid either. I
interpreted it as meaning that the preferred way for a text link was
such "# <<tag>>" constructs, that is, all the contrary of a deprecation.
> I suggest to avoid bothering with it.
I'll adapt of course, but to what? If not "# <<tag>>", then what is the
way to create a named anchor at an arbitrary place in an Org file?
Explicit HTML code? That does not look at all like an improvement:
1. it would be limited to HTML,
2. Org will not likely not follow links to these from within Emacs,
3. if explicit HTML is introduced through specialized Org comments,
they suffer exactly from the edit problem "# <<tag>>" demonstrated,
being tied to the preceding text instead of the following text.
So, Nicolas, I would surely avoid bothering with this problem, but I do
not feel I have that choice (yet). I hope the letter I wrote at the
beginning of this little thread is not going to be dismissed or ignored.
François
next prev parent reply other threads:[~2012-05-07 0:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 20:35 "# <<tag>>" should stick to the following text François Pinard
2012-05-06 21:18 ` Nicolas Goaziou
2012-05-07 0:41 ` François Pinard [this message]
2012-05-07 1:44 ` François Pinard
2012-05-07 7:10 ` Nicolas Goaziou
2012-05-07 8:24 ` Eric S Fraga
2012-05-07 16:52 ` François Pinard
2012-05-08 14:14 ` Nick Dokos
2012-05-07 1:08 ` Nick Dokos
2012-05-07 5:14 ` Eric S Fraga
2012-05-08 8:33 ` Bastien
2012-05-07 5:34 ` Christian Moe
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=86wr4orffa.fsf@mercure.progiciels-bpi.ca \
--to=pinard@iro.umontreal.ca \
--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).