From: Bastien <bzg@gnu.org>
To: nicholas.dokos@hp.com
Cc: "=?utf-8?Q?Fran=C3=A7ois?=" Pinard <pinard@iro.umontreal.ca>,
emacs-orgmode@gnu.org
Subject: Re: Multiple (natural) languages in a single org-file
Date: Wed, 11 Apr 2012 08:30:56 +0200 [thread overview]
Message-ID: <87iph6aifz.fsf@gnu.org> (raw)
In-Reply-To: <3699.1334121814@alphaville> (Nick Dokos's message of "Wed, 11 Apr 2012 01:23:34 -0400")
Hi Nicholas,
(btw, do you prefer "Nick" or "Nicholas"?)
Nick Dokos <nicholas.dokos@hp.com> writes:
> None of this is an argument for leaving the manual as is: if you had a
> problem finding the information, then others will too, so the manual
> should be improved.
Done.
> But the information is there, and moreover, learning how to find it in
> this instance has the huge advantage of teaching one how to find it for
> all the other options as well. The question as always is how far to go
> in documenting all the options: it would be good to document them all
> (as Bastien would say: "patches are welcome"), but is it better to learn
> searching tricks or to submit patches to improve the doc? Each one of us
> would probably answer that question differently (we have different
> "breaking points").
The "how far" question is related to the "where" question.
- The Org compact guide: "vital" options should be there. This guide
should also point to the manual for further exploration.
- The Org manual: the most used/useful options should be there. The
manual should point to a specific Worg page for more.
- Worg: anything else.
Of course, "vital" and "used/useful" are moving targets, but that's why
we have the mailing list and the discussions. To shoot them together.
What we really *really* is a good tutorial on how to digg all the
documentation aspects of Emacs. Basically, how to go from checking the
manual to checking with C-h v and other functions.
Any taker?
> So you might prepare a doc patch (please do!) - I
> might go on a searching expedition and find things you didn't [fn:1].
> The first one benefits everybody, the second one benefits mainly me, but
> sometimes I can find a teaching moment and tell other people how to do
> something: which is why I spent a half-hour writing this :-) [fn:2]
I hope the community realizes how precious are all these hours that you
spent in patiently fighting with everyone issues... at least here, this
is immensely appreciated! So, thanks again for this.
--
Bastien
next prev parent reply other threads:[~2012-04-11 6:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 10:45 Multiple (natural) languages in a single org-file Carlos Russo
2012-03-01 11:05 ` Carlos Russo
2012-03-01 12:37 ` Nicolas Goaziou
2012-04-11 1:19 ` François Pinard
2012-04-11 5:23 ` Nick Dokos
2012-04-11 6:30 ` Bastien [this message]
2012-04-11 6:18 ` 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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iph6aifz.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--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).