From: "Roland Winkler" <winkler@gnu.org>
To: Bastien <bzg@altern.org>
Cc: 13668@debbugs.gnu.org
Subject: bug#13668: 24.2.93; strike-through in org mode
Date: Sun, 10 Feb 2013 11:08:03 -0600 [thread overview]
Message-ID: <20759.54259.751629.173184__25253.7636356012$1360516174$gmane$org@gargle.gargle.HOWL> (raw)
In-Reply-To: <87zjzc2kxx.fsf@bzg.ath.cx>
On Sun Feb 10 2013 Bastien wrote:
> > Why put this in a separate FAQ? Aren't the info pages the first
> > source of information for such things?
>
> Depends. We try to keep the info manual readable, and it's already
> quite long. If you can find a good place in the manual, please send
> a patch.
I do not find the info nodes on "Structural markup elements"
particularly overloaded. The node "Emphasis and monospace" is just
one short paragraph, and org-fontify-emphasized-text could esily be
mentioned there -- unless this variable also affects other things,
so that it should be mentioned higher up in the node hierarchy.
If such things get distributed among different places, an info
manual plus a separate FAQ, they get yet more confusing, in
particular for casual users of org mode. Many users will not even
know (or expect) that the info manual does not give them the full
story, but they need to consult other sources, too.
Take the elisp manual: it's pretty big. But I like it because its
authors are pretty good in making it an *efficient* and *reliable*
source of information. (Here I'd like to put these words in bold,
because I really appreciate this!)
next prev parent reply other threads:[~2013-02-10 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 23:35 bug#13668: 24.2.93; strike-through in org mode Roland Winkler
2013-02-10 4:25 ` Bastien
[not found] ` <87halkn6bz.fsf@bzg.ath.cx>
2013-02-10 13:00 ` Roland Winkler
2013-02-10 16:27 ` Bastien
2013-02-10 17:08 ` Roland Winkler [this message]
2013-02-10 17:12 ` Bastien
2013-02-10 17:33 ` Roland Winkler
[not found] ` <20759.55782.687925.263736@gargle.gargle.HOWL>
2013-02-11 14:04 ` Bastien
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='20759.54259.751629.173184__25253.7636356012$1360516174$gmane$org@gargle.gargle.HOWL' \
--to=winkler@gnu.org \
--cc=13668@debbugs.gnu.org \
--cc=bzg@altern.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.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).