From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-hide-emphasis-markers not mentioned in the org manual
Date: Wed, 15 Nov 2017 10:27:45 -0500 [thread overview]
Message-ID: <87k1yry32m.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 23051.4978.1475.216563@frac.u-strasbg.fr
Alain.Cochard@unistra.fr writes:
> Thomas Rikl writes on Tue 14 Nov 2017 14:10:
>
> > (and perhaps other customization variables)
> >
> > Version: Release 9.1.2 (release 9.1.2-192-gc029c4)
> > of the org manual
> >
> > regards Thomas R.
>
> In a recent (late sept.) discussion on this list ("Confused about the
> explanation for 'org-cycle"), it was argued by Org experts that
> documenting every customization variable was not the best way to go.
That's not quite right: it should say
" ... documenting every customization variable *in the manual* was not
the best way to go."
*All* customization variables should be documented. You can get that documentation
with
C-h v <variable name> RET
If there is no such documentation, that's a bug. You can also use "customize" to
list such variables (or groups of related variables).
The manual is a good way to start, but it does noe wander into the darker corners.
Fortunately, emacs provides enough flash lights to illuminate them. Knowing about
these is important: it makes your (emacs) life easier, more productive and more
enjoyable.
> So maybe this also applies for the particular case of
> org-hide-emphasis-markers...
>
> Regards
--
Nick
prev parent reply other threads:[~2017-11-15 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 13:10 org-hide-emphasis-markers not mentioned in the org manual Thomas Rikl
2017-11-14 16:01 ` Alain.Cochard
2017-11-15 15:27 ` Nick Dokos [this message]
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=87k1yry32m.fsf@alphaville.usersys.redhat.com \
--to=ndokos@gmail.com \
--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).