From: Julius Gamanyi <julius.gb@gmail.com>
To: Bernt Hansen <bernt@norang.ca>,
Carsten Dominik <carsten.dominik@gmail.com>
Cc: Bastien Guerry <bastienguerry@googlemail.com>,
emacs-orgmode list <emacs-orgmode@gnu.org>
Subject: Re: Re: Produce a pdf outline using the latex outline package of the notes in org file
Date: Fri, 7 Jan 2011 08:36:07 +0000 [thread overview]
Message-ID: <AANLkTinu+Tsu4zezF8hVubYdzona7Oqq-2-emoGDSnU9@mail.gmail.com> (raw)
In-Reply-To: <DE0B9E97-1A3D-49E6-8C8D-812EA153D452@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2631 bytes --]
On 7 January 2011 06:40, Carsten Dominik <carsten.dominik@gmail.com> wrote:
>
> On Jan 7, 2011, at 3:22 AM, Bernt Hansen wrote:
>
> Hi Julius,
>>
>> Julius Gamanyi <julius.gb@gmail.com> writes:
>>
>> While adding the changes to the current development code, I ran into an
>>> obstacle: I couldn't find org-install.el even with the find command; but
>>> org-install.el is part of the stable release.
>>> Is org-install.el only added before a stable release or I'm I missing
>>> something else?
>>>
>>
>> You can create lisp/org-install.el with
>>
>> make lisp/org-install.el
>>
>
Thanks, this works and now I can see org-install.el. Since org-install.el is
generated,
I think it's best if I don't change it but make sure that the autoload
comments are
picked up from org-latex-outline.el.
>
>>
>>> Another question: must all the contributions be stored in the contrib
>>> directory?
>>>
>>
>> I think only contributions from people who haven't signed the FSF papers
>> need to be limited to the contrib directory but Bastien or Carsten would
>> have a more official comment on that.
>>
>
> The contrib directory contains both stuff where no FSF papers
> have been signed, and also things where it has not yet been determined
> if they are generally useful and if they will be used by a significant
> number of people. Normally such new contributions are added to
> contrib/lisp, and then moved to lisp/ once it has been decided to do so.
> So I would recommend that your initial patch puts it into contrib/lisp,
> with corresponding changes to the org-modules variable in lisp/org.el
> and in contrib/README. And, if you like, documentation on Worg.
>
I'll move the patches to contrib/lisp and make the updates.
> This is how I used to handle this - the decision about
> org-latex-outline.el will of course be made by Bastien.
>
> One thing: all files in lisp/ must have names which are
> unique within the first 8 characters, due to Emacs rules
> which require unique names for, I believe, MS-DOS.
> org-latex-outline.el would not fulfill this requirement.
> Maybe org-ltxol.el or so? Or maybe even better the code
> can eventually simply be integrated into org-latex.el?
>
If the outline proves useful, then integrating it with org-latex.el would be
much better.
It consists of a copy-and-paste job of the functions
(org-export-as-latex and org-export-latex-make-header) in org-latex.el. It
adds the
\end{outline} to org-export-as-latex and \begin{outline}[enumerate]
to org-export-latex-make-header while removing the table of contents.
It was the easiest thing that worked at the time but not the cleanest.
Julius
[-- Attachment #1.2: Type: text/html, Size: 4140 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2011-01-07 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 19:58 Produce a pdf outline using the latex outline package of the notes in org file Julius Gamanyi
2011-01-07 2:22 ` Bernt Hansen
2011-01-07 6:40 ` Carsten Dominik
2011-01-07 8:36 ` Julius Gamanyi [this message]
2011-01-18 9:17 ` Bastien
2011-01-18 12:05 ` Julius Gamanyi
2011-01-18 15:52 ` Bastien
2011-01-20 17:00 ` Julius Gamanyi
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=AANLkTinu+Tsu4zezF8hVubYdzona7Oqq-2-emoGDSnU9@mail.gmail.com \
--to=julius.gb@gmail.com \
--cc=bastienguerry@googlemail.com \
--cc=bernt@norang.ca \
--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).