From: Nicolas Goaziou <n.goaziou@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [org-e-texinfo] generate menu items
Date: Sat, 17 Nov 2012 23:33:26 +0100 [thread overview]
Message-ID: <877gpjn9l5.fsf@gmail.com> (raw)
In-Reply-To: <m1fw47q4sr.fsf@tsdye.com> (Thomas S. Dye's message of "Sat, 17 Nov 2012 11:48:36 -1000")
tsd@tsdye.com (Thomas S. Dye) writes:
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>> tsd@tsdye.com (Thomas S. Dye) writes:
>>
>>> Agreed. Perhaps a new property, OPTIONAL_TITLE? The texinfo back-end
>>> could use this in menus and the latex back-end could pass it to the
>>> sectioning command, e.g., \chapter[optional]{title} (if this isn't
>>> already possible).
>>
>> Back-ends can indeed use specific properties (Beamer back-end does it
>> with "BEAMER_ENV" and so on). Though, I suggest to prefix the property
>> name with the name of the backend: "TEXINFO_OPTIONAL_TITLE" (perhaps
>> a bit verbose).
>>
>> Then, one can access to it from the headline translator with:
>>
>> (org-element-property :texinfo-optional-title headline)
>>
>> Anyway, Jonathan Leech-Pepin will decide what to do about that.
>
> I looked in org-e-latex.el but didn't find a way to set the optional
> argument to a sectioning command. Is there currently a way to set this
> argument?
No there isn't.
I had overlooked the fact that you wanted the property to be effective
across back-ends. So, it would define how the entry should appear in the
table of contents in every back-end where it makes sense.
That's a bit of work, because, so far, node-property values are not
parsed. So it would require to define a new class of node-properties:
those with a parsed value. But then, how to decide which properties have
their value parsed are parsed and which have not?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-11-17 22:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 18:10 [org-e-texinfo] generate menu items Thomas S. Dye
2012-11-17 18:50 ` Nicolas Goaziou
2012-11-17 19:56 ` Thomas S. Dye
2012-11-17 21:11 ` Nicolas Goaziou
2012-11-17 21:48 ` Thomas S. Dye
2012-11-17 22:33 ` Nicolas Goaziou [this message]
2012-11-17 23:24 ` Thomas S. Dye
2012-11-18 9:02 ` Nicolas Goaziou
2012-11-18 16:22 ` Thomas S. Dye
2012-11-21 16:31 ` Jonathan Leech-Pepin
2012-11-23 23:44 ` Thomas S. Dye
2013-02-23 23:04 ` Nicolas Goaziou
2013-02-25 16:00 ` Jonathan Leech-Pepin
2013-02-25 16:09 ` Nicolas Goaziou
2013-02-25 16:12 ` Jonathan Leech-Pepin
2013-02-25 17:02 ` Thomas S. Dye
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=877gpjn9l5.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).