From: Eric Schulte <eric.schulte@gmx.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Code blocks in lists?
Date: Fri, 18 May 2012 09:08:39 -0400 [thread overview]
Message-ID: <87k409k560.fsf@gmx.com> (raw)
In-Reply-To: <80obplmu1l.fsf@somewhere.org> (Sebastien Vauban's message of "Fri, 18 May 2012 16:40:38 +0200")
"Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:
> Hi Nicolas,
>
> Nicolas Goaziou wrote:
>> "Sebastien Vauban" writes:
>>> As demonstrated by the following ECM, it seems that I can't put code blocks
>>> inside lists.
>>>
>>> I guess this is the same root cause as the problem I tried to described at
>>> http://lists.gnu.org/archive/html/emacs-orgmode/2012-02/msg00247.html.
>>>
>>> Here, the fact that it is an enumerated list makes the problem stand
>>> out.
>>
>> I still cannot reproduce it.
>>
>> What happens if you eval:
>>
>> (let ((org-current-export-file (current-buffer)))
>> (org-export-blocks-preprocess))
>>
>> in your buffer?
>
> * Before command
>
> --8<---------------cut here---------------start------------->8---
> 1. Download and install color-theme.
>
> #+begin_src emacs-lisp
> (add-to-list 'load-path "/path/to/color-theme-6.6.0")
> (require 'color-theme)
> #+end_src
>
> 2. Download and install color-theme-leuven.
>
> #+begin_src emacs-lisp
> (add-to-list 'load-path "/path/to/color-theme-leuven")
> (require 'color-theme-leuven)
> #+end_src
>
> 3. Restart Emacs.
> --8<---------------cut here---------------end--------------->8---
>
> * Command to execute
>
> --8<---------------cut here---------------start------------->8---
> (let ((org-current-export-file (current-buffer)))
> (org-export-blocks-preprocess))
> --8<---------------cut here---------------end--------------->8---
>
> * After command
>
> --8<---------------cut here---------------start------------->8---
> 1. Download and install color-theme.
>
> #+BEGIN_SRC emacs-lisp
> (add-to-list 'load-path "/path/to/color-theme-6.6.0")
> (require 'color-theme)
> #+END_SRC
>
> 2. Download and install color-theme-leuven.
>
> #+BEGIN_SRC emacs-lisp
> (add-to-list 'load-path "/path/to/color-theme-leuven")
> (require 'color-theme-leuven)
> #+END_SRC
>
> 3. Restart Emacs.
> --8<---------------cut here---------------end--------------->8---
>
> * Summary of the changes
>
> The code blocks "meta data":
> - is indented in column 0
> - becomes uppercased
> - gets a trailing space added
>
> * Note
>
> If I go at the end of (or just below) the text "3. Restart Emacs", and press
> C-RET, I get:
>
> --8<---------------cut here---------------start------------->8---
> 3. Restart Emacs.
>
> 4.
> --8<---------------cut here---------------end--------------->8---
>
> in the "Before command" section, while I get:
>
> --8<---------------cut here---------------start------------->8---
> 1. Restart Emacs.
> 2.
> --8<---------------cut here---------------end--------------->8---
>
> in the "After command" section.
>
> Hence, they do not share the same view on identifying the current list.
>
> Best regards,
> Seb
Hi Seb,
Sorry I missed the bit about `org-src-preserve-indentation', indeed
there was a bug in the block indentation during export. I've just
pushed up a fix, please let me know if you continue to have problems.
Thanks,
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2012-05-18 15:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 8:39 Code blocks in lists? Sebastien Vauban
2012-05-18 9:02 ` Nicolas Goaziou
[not found] ` <87obpl3lre.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-05-18 11:50 ` **: " Sebastien Vauban
2012-05-18 11:50 ` Sebastien Vauban
[not found] ` <1337342641.WXHGMQZGWMUF@spammotel.com>
2012-05-18 13:44 ` Nicolas Goaziou
2012-05-18 12:09 ` Eric Schulte
2012-05-18 14:40 ` Sebastien Vauban
2012-05-18 13:08 ` Eric Schulte [this message]
2012-05-18 18:55 ` Sebastien Vauban
2012-05-18 17:11 ` Eric Schulte
2012-05-18 20:38 ` Sebastien Vauban
2012-05-19 22:48 ` Eric Schulte
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=87k409k560.fsf@gmx.com \
--to=eric.schulte@gmx.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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).