From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Rick Frankel <rick@rickster.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug formatting source code in new latex exporter
Date: Mon, 25 Mar 2013 22:09:37 +0100 [thread overview]
Message-ID: <87obe7xk32.fsf@gmail.com> (raw)
In-Reply-To: <m2r4j4wf56.wl%rick@rickster.com> (Rick Frankel's message of "Sun, 24 Mar 2013 19:29:25 -0400")
Hello,
Rick Frankel <rick@rickster.com> writes:
>> > The cross reference approach seems clever, but maybe a simpler
>> > approach would simply be to add an ATTR_LaTeX(:longlisting) and leave
>> > it up to the user.
>>
>> That's the most reasonable option, indeed.
>>
>> The following patch implements :long-listing attribute for src-blocks.
>>
>> What do you think?
>
> Works for me.
Good. I wonder if :long wouldn't be better. Since the attribute only
applies to src-blocks, the "listing" is redundant.
> BTW, a couple of other small things:
>
> 1. I think `elisp' should be added to the default
> `org-latex-minted-langs'.
There is no "elisp" language in Babel, is it? I think it's "emacs-lisp".
> 2. Unrelated, but I spent some time trying to get relative file
> links working. At least in Acrobat Reader on windows, the only
> way file links work is with no protocol at all
> (\url{path/to/file}).
Do you mean the "file:" part should be dropped for files with a relative
path?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-03-25 21:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 21:11 Bug formatting source code in new latex exporter Rick Frankel
2013-03-21 19:26 ` Nicolas Goaziou
2013-03-22 0:50 ` Rick Frankel
2013-03-23 21:51 ` Nicolas Goaziou
2013-03-24 23:29 ` Rick Frankel
2013-03-25 21:09 ` Nicolas Goaziou [this message]
2013-03-26 12:28 ` Rick Frankel
2013-03-27 14:17 ` Nicolas Goaziou
2013-03-27 22:10 ` Rick Frankel
2013-03-27 22:29 ` Nicolas Goaziou
-- strict thread matches above, loose matches on Subject: below --
2013-03-19 20:59 Rick Frankel
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=87obe7xk32.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rick@rickster.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).