From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: org-html-use-unicode-chars breaks source code blocks
Date: Sun, 09 Aug 2015 21:32:04 +0200 [thread overview]
Message-ID: <86r3nc2r7v.fsf@example.com> (raw)
In-Reply-To: olu8u9lmqry.fsf@med.uni-goettingen.de
Andreas Leha <andreas.leha-A1rZ2h3LdSKGMSlLMZIubhS11BummzK+@public.gmane.org> writes:
> [ deleted: discussion on beatification ]
>
>> My initial reaction was to kill it as well. But I might feel like this a
>> bit to often (I feel the same way about headline keywords like COMMENT).
>
> There has been repeated 'bashing' of the COMMENT keyword lately on this
> list. Let me just raise a voice in defence. I do not mind the syntax
> too much, but the functionality of commenting a whole subtree without
> loosing the outline functionality is really handy. Especially also in
> distinction to the equally handy :noexport: tag.
>
> So, even if there is probably not a high risk for the COMMENT keyword to
> be dropped I just wanted to express my support for it.
+1
Both COMMENT and :noexport: are necessary, for achieving different tasks.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2015-08-09 19:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 13:40 org-html-use-unicode-chars breaks source code blocks Vladimir Alexiev
2015-08-04 17:35 ` Rasmus
2015-08-04 18:37 ` Nicolas Goaziou
2015-08-07 9:56 ` Rasmus
2015-08-07 10:37 ` Nicolas Goaziou
2015-08-07 10:57 ` Rasmus
2015-08-08 21:09 ` Andreas Leha
2015-08-09 19:32 ` Sebastien Vauban [this message]
2015-08-16 13:48 ` Bastien Guerry
2015-08-16 18:47 ` Brady Trainor
2015-08-17 8:01 ` Nicolas Goaziou
2015-08-17 8:41 ` Brady Trainor
2015-08-17 16:44 ` Rasmus
2015-08-16 14:03 ` Bastien Guerry
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=86r3nc2r7v.fsf@example.com \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).