From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bastien <bzg@altern.org>
Cc: "emacs-orgmode@gnu.org List" <emacs-orgmode@gnu.org>,
"Dominik, Carsten" <C.Dominik@uva.nl>,
Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Exporter question
Date: Sun, 24 Feb 2013 10:31:21 +0100 [thread overview]
Message-ID: <87ppzqys5y.fsf@gmail.com> (raw)
In-Reply-To: <8738wmax8h.fsf@bzg.ath.cx> (Bastien's message of "Sun, 24 Feb 2013 10:15:42 +0100")
Bastien <bzg@altern.org> writes:
>> Do you think it's still necessary to provide an equivalent for
>> `org-export-remove-timestamps-from-toc'? It's only a matter of copying
>> the headline title in the property, without timestamp.
>
> org-html|latex-format-headline-function allow these arguments:
>
> TODO the todo keyword (string or nil).
> TODO-TYPE the type of todo (symbol: `todo', `done', nil)
> PRIORITY the priority of the headline (integer or nil)
> TEXT the main headline text (string).
> TAGS the tags as a list of strings (list of strings or nil).
>
> Why not having another TRIM-REGEXP argument to selectively trim
> the content matched by a regexp against TEXT?
Because it would have to mach TEXT against destination code, so it would
be fragile (i.e. if you modify how timestamps are transcoded, you have
to modify this regexp accordingly).
If it has to be implemented, it's far easier to remove objects from
parsed data (e.g. in `org-export-get-optional-title').
> `org-export-with-timestamps-in-toc', if nil, would use this arg;
> but users could remove anything from the headlines (and the TOC),
> not just from the TOC.
>
> And `org-export-with-timestamps' could be set to 'from-toc or
> 'from-headline. And we could extend `org-export-with-tags'
> similarily.
>
> (I think `org-export-with-timestamps-in-toc' is better than
> `org-export-remove-timestamps-from-toc' because `org-export-with'
> is more widely used for the same purposes.)
>
> Just a suggestion for combining backward compatibility and adding
> some flexibility thanks for the new engine.
I have a patch ready with `org-export-with-timestamps-in-toc' variable,
but as I was writing it, I realized it might not be necessary to apply
it. I'd like to avoid over-engineering as much as possible, hence the
question.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-02-24 9:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 12:52 Exporter question Dominik, Carsten
2013-02-12 19:46 ` Nicolas Goaziou
2013-02-12 20:00 ` Carsten Dominik
2013-02-12 22:12 ` Nicolas Goaziou
2013-02-24 8:55 ` Nicolas Goaziou
2013-02-24 9:15 ` Bastien
2013-02-24 9:31 ` Nicolas Goaziou [this message]
2013-02-24 9:50 ` Bastien
2013-02-24 10:48 ` Carsten Dominik
2013-02-24 14:00 ` Nicolas Goaziou
2013-02-24 14:02 ` Carsten Dominik
2013-02-24 19:01 ` Bastien
2013-02-25 15:06 ` Nicolas Goaziou
2013-02-26 13:46 ` Bastien
2013-02-26 19:43 ` Aaron Ecay
2013-02-27 18:06 ` Eric S Fraga
2013-02-26 23:12 ` Nicolas Goaziou
2013-02-27 8:53 ` Bastien
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=87ppzqys5y.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=C.Dominik@uva.nl \
--cc=bzg@altern.org \
--cc=carsten.dominik@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).