From: Rasmus <rasmus@gmx.us>
To: jonathan.leechpepin@gmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: template for writing Emacs manuals in Org
Date: Wed, 18 May 2016 18:43:53 +0200 [thread overview]
Message-ID: <87mvnnfh9y.fsf@gmx.us> (raw)
In-Reply-To: <87bn43xrqs.fsf@saiph.selenimh> (Nicolas Goaziou's message of "Wed, 18 May 2016 18:20:27 +0200")
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:
>
>> I’m trying to remember why I didn’t implement indexes as properties
>> (it may well have been because I simply didn’t consider it). Assuming
>> there’s nothing in the exporter to prevent converting properties to
>> text after headlines it could work. Treat comma separated values as
>> separate entries.
>
> Index entries are not section wide. It doesn't sound right to attach
> them to properties drawers.
In many cases an index entry is referring explicitly to a specific
heading. Example:
** Installation
:PROPERTIES:
:DESCRIPTION: How to install a downloaded version of Org-mode
:END:
#+cindex: installation
In such cases I’d prefer to able to attach the index specifically to the
heading. Much the same way that I prefer to give a heading a custom_id
property rather than putting a <<label>> after a headline.
> Besides, the {{{cindex()}}} macro is not used anymore. There is the
> CINDEX keyword, which is slightly better.
My bad, I must have accidentally looked at the version before your recent
changes. The keyword is already better.
> I guess we could use #+INDEX instead, but it would require to add an
> information specific to Texinfo (index type), which would probably
> defeat the simplicity of the solution.
Either is fine. Though I don’t think it’s less simple to have a key.
#+index: key :type cindex.
Rasmus
--
This is the kind of tedious nonsense up with which I will not put
next prev parent reply other threads:[~2016-05-18 16:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 7:21 template for writing Emacs manuals in Org Eric Abrahamsen
2016-05-16 17:37 ` Kaushal Modi
2016-05-16 17:55 ` John Hendy
2016-05-16 18:08 ` Rasmus
2016-05-16 18:40 ` Thomas S. Dye
2016-05-16 20:02 ` Nicolas Goaziou
2016-05-16 21:33 ` Thomas S. Dye
2016-05-17 5:52 ` Nicolas Goaziou
2016-05-17 14:44 ` Thomas S. Dye
2016-05-17 15:37 ` Nicolas Goaziou
2016-05-17 18:36 ` Thomas S. Dye
2016-05-17 18:56 ` Charles C. Berry
2016-05-17 18:56 ` Nick Dokos
2016-05-18 9:21 ` Rasmus
2016-05-18 14:56 ` Jonathan Leech-Pepin
2016-05-18 16:20 ` Nicolas Goaziou
2016-05-18 16:43 ` Rasmus [this message]
2016-05-17 0:23 ` Eric Abrahamsen
2016-05-17 3:32 ` Thomas S. Dye
2016-05-17 4:16 ` Eric Abrahamsen
2016-05-17 7:35 ` Rasmus
2016-05-17 8:34 ` Eric Abrahamsen
2016-05-17 13:24 ` Phillip Lord
2016-05-18 23:59 ` Ciaran Mulloy
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=87mvnnfh9y.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@gnu.org \
--cc=jonathan.leechpepin@gmail.com \
/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).