From: Aankhen <aankhen@gmail.com>
To: Stinky Wizzleteet <wizzleteet@hotmail.com>,
Org mailing list <emacs-orgmode@gnu.org>
Subject: Re: editing "org-export-latex-default-packages-alist" has no effect
Date: Sun, 24 Apr 2011 01:28:19 +0530 [thread overview]
Message-ID: <BANLkTi=+U1-8tTdBSQKYzrQk5oZ7GD0Kyw@mail.gmail.com> (raw)
In-Reply-To: <cuoei4s3k1n.fsf@mauc.nl>
On Sat, Apr 23, 2011 at 23:51, Stinky Wizzleteet <wizzleteet@hotmail.com> wrote:
> Stinky Wizzleteet <wizzleteet@hotmail.com> writes:
>
>> Aankhen <aankhen@gmail.com> writes:
> -snip-
>>>> However, fontenc and textcomp are still in the org-generated tex file.
>>>> bug, or feature ?
>>>
>>> That line you pasted contains both packages. Maybe you forgot to set
>>> it after customising it or some such thing?
>>
>> I figured that "textcomp" "nil" meant that textcomp was turned off..
>> I'll try to erase the entry alltogether.
>
> Yes, I have confirmed now that I need to erase these items from the list
> in order for them to not show up in the header.
> The customize-variable system toggled the entries from "t" to "nil",
> which apparently was not enough.
> I think this is a bug.
From the docstring:
,----[ C-h v org-export-latex-default-packages-alist RET ]
| Each cell is of the format ( "options" "package" snippet-flag).
| If SNIPPET-FLAG is t, the package also needs to be included when
| compiling LaTeX snippets into images for inclusion into HTML.
`----
If you look at the Customize interface, where you toggled it, the
label is ‘Snippet’. The ‘INS’ and ‘DEL’ buttons are for manipulating
the list.
> But now, for me, it works.
>
> thx.
Glad I could help.
Aankhen
next prev parent reply other threads:[~2011-04-23 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 7:24 editing "org-export-latex-default-packages-alist" has no effect Stinky Wizzleteet
2011-04-23 14:24 ` Aankhen
2011-04-23 18:10 ` Stinky Wizzleteet
2011-04-23 18:21 ` Stinky Wizzleteet
2011-04-23 19:58 ` Aankhen [this message]
2011-04-23 19:54 ` Carsten Dominik
2011-04-23 21:34 ` Stinky Wizzleteet
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='BANLkTi=+U1-8tTdBSQKYzrQk5oZ7GD0Kyw@mail.gmail.com' \
--to=aankhen@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wizzleteet@hotmail.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).