From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [Babel] Need for an extra literal block construct
Date: Sat, 20 Nov 2010 00:00:53 +0100 [thread overview]
Message-ID: <807hg83om2.fsf@missioncriticalit.com> (raw)
In-Reply-To: 449AB0AE-C332-442E-9498-7B1CFBF603A5@tsdye.com
Hi Thomas,
"Thomas S. Dye" wrote:
> On Nov 19, 2010, at 12:02 PM, Sébastien Vauban wrote:
>> "Thomas S. Dye" wrote:
>>> On Nov 19, 2010, at 10:26 AM, Sébastien Vauban wrote:
>>>> *Same for PDF*: the lists in the VERSE environment are interpreted:
>>>>
>>>> --8<---------------cut here---------------start------------->8---
>>>> \begin{verse}
>>>>>> Does it work?\\
>>>>> \\
>>>>> Yes, if you:\\
>>>>> - update \url{this-var}\\
>>>>> - restart\\
>>>> \vspace*{1em}
>>>> OK. Confirmed, but you need to:\\
>>>> \begin{enumerate}
>>>> \item delete the \url{cache}.\\
>>>> \item redo it.\\
>>>> \end{enumerate}
>>>>
>>>> \vspace*{1em}
>>>> Thanks to:\\
>>>> \begin{itemize}
>>>> \item you\\
>>>> \item me\\
>>>> \end{itemize}
>>>>
>>>> \end{verse}
>>>> --8<---------------cut here---------------end--------------->8---
>>>
>>> Just a side comment on the LaTeX output of your example: it is usually not
>>> a good idea to put markup like \vspace in the .tex file. Commands like
>>> \vspace work there, but they defeat the document design of the style or
>>> class file. In the ideal case, commands like \vspace are confined to style
>>> and class files and do not appear in tex files.
>>>
>>> Perhaps the \vspace could be eliminated on the way to squashing your bug?
>>
>> Just to be sure we talk of the same thing, the \vspace is not introduced by
>> me. It's something automatically inserted in the TeX during the VERSE
>> conversion.
>>
>> I think it's clear to you, but let's state it clearly...
>
> Yes, that's what I meant. Apologies for any ambiguity.
No worry! It's simply because I misunderstood it when reading it the first
time. Maybe because I read too quickly, because English is not my mother
tongue, or because it's already late for me. Or a bit of all 3 reasons...
Thanks, clearly, for attaching importance to this post!... and for passing
extra information...
Best regards,
Seb
--
Sébastien Vauban
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-11-19 23:00 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 15:16 [babel] Environment around exported results Sébastien Vauban
2010-09-20 4:46 ` Eric Schulte
2010-09-20 19:10 ` Sébastien Vauban
2010-09-21 7:44 ` Sébastien Vauban
2010-09-21 13:14 ` Eric Schulte
2010-09-24 9:28 ` Sébastien Vauban
2010-09-24 21:01 ` Rainer M Krug
2010-09-27 8:16 ` Sébastien Vauban
2010-11-19 13:27 ` [Babel] Need for an extra literal block construct Sébastien Vauban
2010-11-19 15:17 ` Christian Moe
2010-11-19 20:12 ` Sébastien Vauban
2010-11-19 20:26 ` Sébastien Vauban
2010-11-19 20:38 ` Thomas S. Dye
2010-11-19 22:02 ` Sébastien Vauban
2010-11-19 22:20 ` Thomas S. Dye
2010-11-19 23:00 ` Sébastien Vauban [this message]
2010-11-19 22:24 ` Eric Schulte
2010-11-19 23:07 ` Eric Schulte
2010-11-20 7:20 ` Sébastien Vauban
2010-11-22 21:46 ` Sébastien Vauban
2010-11-23 0:42 ` Eric Schulte
2010-11-23 23:15 ` Sébastien Vauban
2010-11-19 23:13 ` Sébastien Vauban
2010-11-19 22:36 ` Dan Davison
2010-11-20 21:50 ` Sébastien Vauban
2010-11-21 10:01 ` Dan Davison
2010-11-22 20:22 ` Sébastien Vauban
2010-11-21 13:41 ` Nicolas Goaziou
2010-11-22 20:30 ` Sébastien Vauban
2010-11-23 19:27 ` Nicolas Goaziou
2010-11-23 23:22 ` Sébastien Vauban
2010-11-24 10:14 ` Nicolas Goaziou
2010-11-19 23:10 ` Christian Moe
2010-11-19 23:23 ` Sébastien Vauban
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=807hg83om2.fsf@missioncriticalit.com \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.