emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: tsd@tsdye.com (Thomas S. Dye)
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [org-e-texinfo] generate menu items
Date: Sat, 17 Nov 2012 13:24:24 -1000	[thread overview]
Message-ID: <m1boevq0d3.fsf@tsdye.com> (raw)
In-Reply-To: <877gpjn9l5.fsf@gmail.com> (Nicolas Goaziou's message of "Sat, 17 Nov 2012 23:33:26 +0100")

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> 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?

Thanks for the information and explanation.  Back-end-specific
properties should work nicely in this case.

I'll wait to see what Jonathan thinks about the original query.

All the best,
Tom

-- 
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com

next prev parent reply	other threads:[~2012-11-17 23:24 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
2012-11-17 23:24           ` Thomas S. Dye [this message]
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=m1boevq0d3.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@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

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).