emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Indraneel Majumdar <indraneel@indraneel.info>
To: Scot Becker <scot.becker@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Header levels and section numbering > 3, in LaTeX export
Date: Fri, 08 Oct 2010 15:54:42 +0530	[thread overview]
Message-ID: <4CAEF16A.3050508@indraneel.info> (raw)
In-Reply-To: <AANLkTinb=TcnEpe3J=j20BXb=vDHT46t-C5=-7HSW5Xq@mail.gmail.com>


>> I couldn't get easylist to understand the
>> \star symbol that orgmode uses. Do you know how to do that?
> No.  You might have seen the footnote in the easylist documentation
> (on p. 2) which says:
>
> "You might not be happy with the symbols and maybe you'd like to use
> another one, or simply have your favorite symbol
> as default to avoid remembering such a cumbersome name as 'pilcrow'.
> Here's a simple hack that does the job: select the
> entire code of the package, and replace all occurrences of Ÿ (<<-- the
> pilcrow) with your symbol. Make sure you won't use it in the list for
> other purposes, though."
>
> I've not tried this, however.  It would be nice if there were a dead
> easy way to get easylist and org-mode to work well together, since the
> two are very natural partners.  Let me know if you can make this work.
>
I couldn't get either \star nor \ast to work so I'm just using \sharp 
now, and am simply replacing # (at beginning of the line) with a hook. 
I'm not sure which is the best hook to use though. I don't want to alter 
my orgmode buffer and also want the hook to run on orgmode syntax. So 
far, I've failed at this.
org-export-first-hook runs in my orgmode buffer and alters the contents.
org-export-latex-after-blockquotes-hook runs after latex export has 
already happened (ie \section etc have already been converted)
Maybe there's a hook in the middle somewhere, but I couldn't find any 
documentation on it.
>> And also to skip
>> the first 3 stars in a level4 heading (if I want to retain latex's default
>> top 3 levels)?
> I've never actually gone all the way to making a document
> easy-to-publish with Easylist.  I've just manually converted
> org-mode's stars to a character Easylist can understand, then manually
> wrapped the whole thing in a LaTeX preamble.  The ideal would be to
> automate the process, perhaps by using org-babel and putting your
> easylist sections in special code blocks. But I've not taken the time
> to figure all that out.
I do not even know what babel is, although I've heard it in a ton of 
different contexts. Considering what the word "babel" means, I'm not 
even sure if that is strange or not!
> Failing that, I bet you could do a halfway hack with minimal amount of
> manual work.  For example (if I understand you correctly), you could
> make an org document like this:
>
> * Regular org heading
> ** Subheading
> ** Here's a third-level heading
> STARTLIST
> **** My first thesis, which is longer and wordier than it probably should be.
> ***** Of course it's nothing compared to the length of its supporting arguments
> *****  Both of them
> **** Here is my second thesis, as convincing as the first
> ENDLIST
>
> Org-mode will let you do all of that, just fine.  Then either
> manually, or with a temporary latex export hook, do something like
> this:
>
> replace STARTLIST with \begin{easylist} and ENDLIST with \end{easylist}
> replace '**** ' with '&  ' and '***** ' with'&&  ' and ****** ' with'&&&  ', etc.
>
>
> If you do it in an export hook, I think you'd want to do it in one
> that runs before everything else.  That way org-mode will leave
> everthing in your easylist environment alone.  What that will do to
> quotation marks and /emphasis/ I don't know.
>
This is exactly what I want to do, but which export hook to use? 
Something that will not modify my original buffer and also understand 
regexp that I can base on what was originally in my buffer. So instead 
of searching for \paragraph, I can search for "**** ", but I want to 
keep "**** " in my original org buffer.

Indraneel
> This should leave you with an easylist which starts at level '1', in a
> document which uses org's header levels 1-3 in the normal latex way.
> Is that what you want?
>
> Make sure in the preamble, you have \usepackage[ampersand]{easylist}
>
> Let me know if you need help figuring any of this out in detail.
> That's just a rough sketch.
>
> Cheers,
>
> Scot
>
> _______________________________________________
> 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
>

      reply	other threads:[~2010-10-08 10:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <k@limist.com>
2010-10-06  3:36 ` Header levels and section numbering > 3, in LaTeX export Kai
2010-10-06  4:22   ` Indraneel Majumdar
2010-10-06  5:38   ` Nick Dokos
2010-10-06 21:45     ` Scot Becker
2010-10-07  1:06       ` Indraneel Majumdar
2010-10-07  9:55         ` Scot Becker
2010-10-08 10:24           ` Indraneel Majumdar [this message]

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=4CAEF16A.3050508@indraneel.info \
    --to=indraneel@indraneel.info \
    --cc=emacs-orgmode@gnu.org \
    --cc=scot.becker@gmail.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).