From: Masataro Asai <guicho2.71828@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: section subtitle in latex export
Date: Thu, 2 May 2013 20:05:05 +0900 [thread overview]
Message-ID: <CAL2JeXXsOApVC-RG8W8EGXRnrBJuqOmvmB3bTv1CiYKf2ubQPg@mail.gmail.com> (raw)
In-Reply-To: <87ip31iy7z.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2114 bytes --]
Nicolas,
sorry for my offending remarks in the second message. i was just a little
nervous about that unexpected behavior for me.
org latex classes can be considererd as a template. template is somewhat
similer to lambda. you wouldnt want any function to be modified by another
function which recieved it as its argument.
so if something may be inserted in the template without notice, instead it
should be better if it has more arguments. say additional %s. if only there
is two of them in the template you can add alternative title, this may be
an option. amother option is, giving altered version explicitly. which may
make it accept four templates per sectioning,
numbered,unnumbered,alternative numbered, altered unnumbered. some people,
at least not me, may want this feature.
if user can modify that behavior it would be definitrly better. well, that
may inflate the list of vars in customs, but thats another ploblem.
the reason of cancelling the alt title, the situation im in is written in
the
first message. one journal template throws an error because it does not
recognize altered titles.
maybe i can write a script which regex all alt titles out, but i wanted to
contribute to the development of org.
sorry for many typos, im currentry wrting on android.
masataro
2013/05/02 17:26 "Nicolas Goaziou" <n.goaziou@gmail.com>:
> Hello,
>
> Masataro Asai <guicho2.71828@gmail.com> writes:
>
> > Reply to myself:
> >
> > I edebugged the ox-latex and studied what's happening.
> > Who wrote this code?
>
> Obviously, not you.
>
> > you shouldn't do things like this... The code is overwriting the
> > defcustom'ed sectioning format, no one knows.
>
> Doing what? Would you mind giving an example of that overwriting thing?
>
> > the best answer for this problem would be changing the structure of
> > org-latex-classes
>
> Really?
>
> > but I dont want to do that right now. so I just gave an option for
> > alternative-heading.
>
> Why would you want to remove every optional title? That would break
> things like tags:not-in-toc and ALT_TITLE properties.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>
[-- Attachment #2: Type: text/html, Size: 2616 bytes --]
next prev parent reply other threads:[~2013-05-02 11:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 1:49 section subtitle in latex export Masataro Asai
2013-05-02 3:26 ` Masataro Asai
2013-05-02 4:46 ` Aaron Ecay
2013-05-02 8:06 ` Rasmus
2013-05-02 8:29 ` Nicolas Goaziou
2013-05-03 8:18 ` Aaron Ecay
2013-05-02 8:26 ` Nicolas Goaziou
2013-05-02 11:05 ` Masataro Asai [this message]
2013-05-02 14:00 ` Nicolas Goaziou
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=CAL2JeXXsOApVC-RG8W8EGXRnrBJuqOmvmB3bTv1CiYKf2ubQPg@mail.gmail.com \
--to=guicho2.71828@gmail.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
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).