From: Sebastian Rose <sebastian_rose@gmx.de>
To: emacs-orgmode@gnu.org
Subject: Re: Org-Mode Presentation Videos
Date: Sun, 19 Oct 2008 23:39:45 +0200 [thread overview]
Message-ID: <48FBA921.8040100@gmx.de> (raw)
In-Reply-To: <20081019184544.GN1080@thinkpad.adamsinfoserv.com>
Russell Adams wrote:
> On Sun, Oct 19, 2008 at 02:02:07PM -0400, srandby@gmail.com wrote:
>> Sebastian Rose wrote:
>> First, I don't know emacs lisp. I've been planning to learn it, but
>> finding the time is difficult and I'm not a professional programmer.
>
> Don't need to know lisp. ;]
Right, my lisp is a desaster. But there are so many snippets for emacs'
custtomization around (in the org-manual, on this list, in emacs docs),
that I manage to fiddle something together.
And, it does not hurt to ask ;-)
>> Second, the customizations I use for LaTeX vary widely between files. My
>> understanding of your code, please correct me if I'm wrong, is that if I
>> have multiple header files for different types of documents, then I must
>> change my .emacs each time I want to change headers. This doesn't seem
>> to be very convenient to me. I suppose it is possible to write some code
>> to take care of multiple header files, but what if one has a brand new
>> header file?
>
> There is a new feature where you can use template lines for the latex
> header instead of customizing .emacs or loading a local variable.
>
> #+LATEX_HEADER my header here
> #+LATEX_HEADER my second row here
>
> I think this is new in git, you may have to have the latest.
Russel is always one step ahead :-D
But still, I prefer the elisp setup, since it's as Manish said:
> I have found that I write only a certain "types" of latex documents,
> professional reports and personal resume for example. And each type
> tends to have same preamble. Even between latex documents much of the
> preamble is also similar.
I use one LaTeX-header for all, mostly documentation for customers.
That's how LaTeX is supposed to be used, right? Define one header file
with logos, page headers and footers, link colors etc., and that's it.
next prev parent reply other threads:[~2008-10-19 21:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 19:13 Org-Mode Presentation Videos Russell Adams
2008-10-17 9:32 ` Rick Moynihan
2008-10-17 19:30 ` srandby
2008-10-17 19:55 ` Russell Adams
2008-10-18 15:06 ` srandby
2008-10-18 19:16 ` Sebastian Rose
2008-10-19 18:02 ` srandby
2008-10-19 18:44 ` Manish
2008-10-19 18:45 ` Russell Adams
2008-10-19 21:39 ` Sebastian Rose [this message]
2008-10-20 0:03 ` Russell Adams
2008-10-20 1:11 ` Sebastian Rose
2008-10-17 20:07 ` Leo
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=48FBA921.8040100@gmx.de \
--to=sebastian_rose@gmx.de \
--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).