From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org,
=?utf-8?Q?Fran=C3=A7ois?= Pinard <pinard@iro.umontreal.ca>,
"Nicolas Goaziou" <n.goaziou@gmail.com>
Subject: Re: "# <<tag>>" should stick to the following text
Date: Mon, 7 May 2012 14:44:53 +0930 [thread overview]
Message-ID: <87sjfctvw2.fsf@ucl.ac.uk> (raw)
In-Reply-To: <4141.1336352894@alphaville> (Nick Dokos's message of "Sun, 6 May 2012 21:08:14 -0400")
Nick Dokos <nicholas.dokos@hp.com> writes:
> Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>
>> Hello,
>>
>> François Pinard <pinard@iro.umontreal.ca> writes:
>>
>> > I'm not sure I'm using "# <<tag>>" correctly, but my feeling is that it
>> > should stick to the following text in various Org operations. Let's say
>> > I have something like (as I think it):
>>
>> "# <<tag>>" is a deprecated construct. I suggest to avoid bothering with
>> it.
>>
>>
>
> With all due respect, that is not a satisfactory answer. I, for one (or
> for two: François would surely appreciate it too), would appreciate a
> pointer to the deprecation notice (I don't remember seeing one but that
> doesn't mean much), and a pointer (if different) to whatever construct
> is supposed to replace it.
>
> Thanks,
> Nick
>
Isn't the deprecation the need to put the <<xxx>> in a comment (i.e. #)?
The angle bracket syntax remains, I thought.
But maybe I also am confused as to the current direction this is
taking...
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org release_7.8.09-529-g035ab3.dirty
next prev parent reply other threads:[~2012-05-07 5:15 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
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 [this message]
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=87sjfctvw2.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--cc=nicholas.dokos@hp.com \
--cc=pinard@iro.umontreal.ca \
/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).