From: Rasmus <rasmus@gmx.us>
To: tsd@tsdye.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Org equivalent to \chapter*
Date: Wed, 06 Aug 2014 19:38:10 +0200 [thread overview]
Message-ID: <87wqalzfgd.fsf@gmx.us> (raw)
In-Reply-To: <m28un1edzm.fsf@tsdye.com> (Thomas S. Dye's message of "Wed, 06 Aug 2014 07:15:25 -1000")
Thomas,
tsd@tsdye.com (Thomas S. Dye) writes:
> Rasmus <rasmus@gmx.us> writes:
>
>> Alan L Tyree <alantyree@gmail.com> writes:
>>
>>> I'm sure this has been asked before, but I can't seem to find it. Is
>>> there an org markup that produces a starred latex heading?
>>>
>>> In a book, for example, I want the Preface to be at chapter level, but
>>> not included in the numbering. Same for HTML export, of course.
>>
>> You would probably need some sort of filter for this. Most certainly
>> you will be able to find implementations on this list.
>>
>> Here's something from my init file that works with LaTeX. Other
>> formats such as txt and html are harder since Org generates section
>> numbers and the TOC.
>
> Thanks for sharing this. It will be useful for book authors.
>
> Do you think it is possible to write a general headline filter that
> takes care of all the various LaTeX possibilities?
I don't like *one* filter to rule them all. Of course, if it's a
collection of other function calls that is OK. As your recent
question showed execution order may matter,
(e.g. with :ignoreheading:clearpage:).
Of course it's possible to bundle a couple of filters generally useful
for ox-latex and provide a "consistent" interface. Alternatively, one
could make a ox-latex+.el that provides a derived class with extra
options. That's may be more work, and may be harder to hack.
In fact Aaron started ox-extra.el, with the intention of providing
"semi-official" extensions but Worg may be a better means of
communication.
> Right now Iʻm using tags to ignoreheading, clearpage, and newpage.
> In addition to your nonum filter, Eric S. has a filter that gets rid
> of a heading and promotes the content, which I havenʻt had occasion
> to use, but also has its own tag.
Yes, Eric has cool tree-based filter(s). I want to study them more
carefully. Quite possibly, it's easier to provide elegant filters
with trees. For instance, you have direct access to the element
representation. In my filters I "hack" my way to this using
text-properties.
> From the LaTeX authorʻs point of view, it would be great to have a set
> of tags (and options) that "just work."
Would you want this as a derived class or filters? Perhaps it's
easier to have a derived class with an alternative headline
function. . .
> Do you (and others) think the "tag and filter" approach can achieve
> this? Or, are there too many moving parts to make it feasible?
Yes.
The ox-koma-script interface is basically controlled via tags. I
think it's nice.
—Rasmus
--
If you can mix business and politics wonderful things can happen!
next prev parent reply other threads:[~2014-08-06 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 0:11 Org equivalent to \chapter* Alan L Tyree
2014-08-06 1:11 ` Thorsten Jolitz
2014-08-06 2:28 ` Nick Dokos
2014-08-06 8:09 ` Thorsten Jolitz
2014-08-06 9:18 ` Rasmus
2014-08-06 17:15 ` Thomas S. Dye
2014-08-06 17:38 ` Rasmus [this message]
2014-08-06 19:52 ` Thomas S. Dye
2014-08-06 22:46 ` Alan L Tyree
2014-08-07 10:05 ` Rasmus
2014-08-07 22:07 ` Alan L Tyree
2014-08-08 8:42 ` Rasmus
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=87wqalzfgd.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).