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 13:11:22 -0400 [thread overview]
Message-ID: <87havdifd1.fsf@gmx.com> (raw)
In-Reply-To: <808vgpqpy6.fsf@somewhere.org> (Sebastien Vauban's message of "Fri, 18 May 2012 20:55:29 +0200")
"Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:
> Hi Nicolas and Eric,
>
> Eric Schulte wrote:
>> "Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:
>>> 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---
>>
>> 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.
>
> With your fix, the above gets correctly exported. Thanks a lot to Nicolas for
> finding out the problem, and to you for the fix.
>
> However, if I change my list to something like this:
>
> 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
>
> 1. 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
>
> 1. Restart Emacs.
>
> #+begin_src emacs-lisp
> (restart)
> #+end_src
>
> The export (see HTML), while being semantically correct in the sense that code
> blocks do belong to the items, seems wrong wrt the indentation, something like
> this:
>
> 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
>
> 1. 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
>
> 1. Restart Emacs.
>
> #+begin_src emacs-lisp
> (restart)
> #+end_src
>
> A bit like if the indentation was "doubled" each time. What do you think of
> that?
>
Hi Seb,
This indentation is an HTML/CSS issue, as far as I can tell Org-mode is
generating the correct HTML.
>
> Should I not use `org-src-preserve-indentation', maybe?[1]
>
The `org-src-preserve-indentation' variable only effects the indentation
of code *inside* of code blocks, it shouldn't have any effect on this
issue.
>
> Best regards,
> Seb
>
> [1] BTW, GitHub seems to use that setting, as they show the same problem as I
> had initially, when exporting README.org to HTML.
Github uses a ruby library named "org-ruby" to export, it is an entirely
separate export implementation.
Best,
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2012-05-18 19:11 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
2012-05-18 18:55 ` Sebastien Vauban
2012-05-18 17:11 ` Eric Schulte [this message]
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=87havdifd1.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).