From: Julius Gamanyi <julius.gb@gmail.com>
To: Bastien <bastien.guerry@wikimedia.fr>
Cc: emacs-orgmode list <emacs-orgmode@gnu.org>
Subject: Re: Produce a pdf outline using the latex outline package of the notes in org file
Date: Tue, 18 Jan 2011 12:05:05 +0000 [thread overview]
Message-ID: <AANLkTi=C+zC7kPHiOz-AL9RQXhweaU+JLeir8k2afo+4@mail.gmail.com> (raw)
In-Reply-To: <87oc7eefle.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1716 bytes --]
Hi Bastien,
Lately, it's been hectic at work. I'm hoping to get some free time in the
next 2 days to send the patches.
Thanks,
Julius
On 18 January 2011 09:17, Bastien <bastien.guerry@wikimedia.fr> wrote:
> Hi Julius,
>
> Julius Gamanyi <julius.gb@gmail.com> writes:
>
> > On and off reader and first time poster.
>
> Welcome on the list!
>
> > I previously used the latex outline package and added a few
> > modifications to get the output I liked. I added the changes to an old
> > stable version of org-mode (org-6.33f), which worked nicely.
> > The code is on github: https://github.com/juliusgb/emacs-org-tex-outline
> >
> > I'd like to add the changes to the current development version.
>
> Please send a patch to the development version with the change you
> propose, many people follow the development version and will be happy
> to test your code.
>
> > Another question: must all the contributions be stored in the contrib
> > directory?
>
> Only useful ones.
>
> > I added the org-latex-outline.el in the lisp directory because all the
> > other output formats, which depended on org-exp.el, org-install.el were
> > in the lisp directory. The org-latex-outline.el also depends on
> > org-latex.el and I wanted to avoid the sorrow of parting them.
>
> We can have contributions in contrib/ that depend on code in lisp/,
> requiring core librairies from the contributed package is standard
> practice - even for exporters (see contrib/lisp/org2rem.el).
>
> > Maybe there's a better setup that I can use. I'm all ears.
>
> Please let us know about your code!
>
> > In addition, I've already signed the appropriate papers with FSF.
>
> Which will certainly ease things.
>
> Thanks!
>
> --
> Bastien
>
[-- Attachment #1.2: Type: text/html, Size: 2542 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-18 12:05 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
2011-01-18 9:17 ` Bastien
2011-01-18 12:05 ` Julius Gamanyi [this message]
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='AANLkTi=C+zC7kPHiOz-AL9RQXhweaU+JLeir8k2afo+4@mail.gmail.com' \
--to=julius.gb@gmail.com \
--cc=bastien.guerry@wikimedia.fr \
--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).