Hello,
> Sébastien Vauban writes:
> I meant, for me, there are only 2 useful options regarding a "block
> environment" such as BLOCKQUOTE and VERSE:
> - either, nothing is "interpreted"; that is, line breaks are
> preserved, and lists are preserved as well (outputted as they are
> written in
Hi Nicolas,
Nicolas Goaziou wrote:
>> Sébastien Vauban writes:
>
>> Though, I don't understand cases where we would like to preserve the
>> "verbatimness" of the linebreaks, but not of the lists, which is the
>> case, currently, for VERSE. Is there any useful use case for that?
>>
>> For me, b
Hi Eric,
(will answer to the other posts later, need to go and rest)
"Eric Schulte" wrote:
> Sébastien Vauban writes:
>> Tested it (yesterday) for HTML. Per-fect! Thanks a lot... It's of great use.
>
> great, thanks for testing
Confirmed.
>> Tried to test it (now) for LaTeX. Can't, for the sa
Hello,
> Sébastien Vauban writes:
> Though, I don't understand cases where we would like to preserve the
> "verbatimness" of the linebreaks, but not of the lists, which is the
> case, currently, for VERSE. Is there any useful use case for that?
> For me, both should be supported together, wh
Hi Seb,
Sébastien Vauban writes:
[...]
>
> Tested it (yesterday) for HTML. Per-fect! Thanks a lot... It's of great use.
>
great, thanks for testing
>
> Tried to test it (now) for LaTeX. Can't, for the same reason as
> described in:
>
>[[http://mid.gmane.org/80eiadw0dh.fsf%40missioncritica
Hi Eric,
"Eric Schulte" wrote:
> "Eric Schulte" writes:
>> This would be useful for custom export of the proposed future babel
>> results block (which I promise I'll implement soon).
>
> An experimental patch implementing wrapping of results using a new
> "wrap" :results header argument is attach
Hi Nicolas,
Nicolas Goaziou wrote:
>> Sébastien Vauban writes:
>
>> I'd expect to see all the above passage from the email to be
>> uninterpreted. It is not acting that way.
>
> According to the manual, VERSE block only preserves line breaks and
> leading white spaces. Otherwise it is _normal_
Hi Dan,
Dan Davison wrote:
> Sébastien Vauban
> writes:
>> Dan Davison wrote:
>>> In addition to the Org example, would you mind supplying a concise,
>>> explicit statement of what the putative bug is? With just the Org example
>>> on its own, the bug is implicit and I at least feel that I'm havi
Hello,
> Sébastien Vauban writes:
> I'd expect to see all the above passage from the email to be
> uninterpreted. It is not acting that way.
According to the manual, VERSE block only preserves line breaks and
leading white spaces. Otherwise it is _normal_ formatting. Though,
this raises an i
Hi Seb,
What I was trying to say is that with bug reports it is helpful if the
first one or two sentences of the email are a precise and brief
statement of what is going wrong. Then the reader can decide if she
wants to continue to the more detailed and discursive material.
Dan
Sébastien Vauban
Hi Seb,
In addition to the Org example, would you mind supplying a concise,
explicit statement of what the putative bug is? With just the Org
example on its own, the bug is implicit and I at least feel that I'm
having to work hard to get there!
Dan
p.s. However, your emails did motivate the fo
Hi Eric,
"Eric Schulte" wrote:
> "Eric Schulte" writes:
>
>> This would be useful for custom export of the proposed future babel
>> results block (which I promise I'll implement soon).
>
> An experimental patch implementing wrapping of results using a new
> "wrap" :results header argument is atta
Hi Christian,
Christian Moe wrote:
> Perhaps I misunderstood what you're after. As I now understand it, you want
> line breaks preserved and you don't want anything interpreted, you want
> verbatim text. Why doesn't EXAMPLE meet your needs?
Because there are clearly 3 key "concepts" to be able to
Hi Eric,
"Eric Schulte" wrote:
> Sébastien Vauban writes:
>> *Same for PDF*: the lists in the VERSE environment are interpreted.
>> So are the CODE inlined words (delimited by =equal= signs).
>>
>> - Bug, or
>> - on purpose?
>
> I believe that this is on purpose,
I'd like to have an "official" a
Hi,
Perhaps I misunderstood what you're after. As I now understand it, you
want line breaks preserved and you don't want anything interpreted,
you want verbatim text. Why doesn't EXAMPLE meet your needs?
Yours,
Christian
On 11/19/10 9:12 PM, Sébastien Vauban wrote:
Hi Christian,
Christian
"Eric Schulte" writes:
> This would be useful for custom export of the proposed future babel
> results block (which I promise I'll implement soon).
An experimental patch implementing wrapping of results using a new
"wrap" :results header argument is attached. Here is an example of its
usage.
*
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--
Hi Seb,
Sébastien Vauban writes:
>
> *Same for PDF*: the lists in the VERSE environment are interpreted:
>
...
>
> So are the CODE inlined words (delimited by =equal= signs).
>
> - Bug, or
> - on purpose?
>
I believe that this is on purpose, otherwise I don't see why verse would
be any differen
Aloha Séb,
On Nov 19, 2010, at 12:02 PM, Sébastien Vauban wrote:
Hi Thomas,
"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---
\beg
Hi Thomas,
"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:\\
>
Aloha Sébastien,
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 a
Hi all,
Sébastien Vauban wrote:
> Christian Moe wrote:
>>> Along this (still open -- at least, I hope so) discussion, I have a request
>>> for a new literal block.
>>>
>>> Currently, when looking at http://orgmode.org/manual/Literal-examples.html,
>>> we
>>> see we only have two "environments" th
Hi Christian,
Christian Moe wrote:
>> Along this (still open -- at least, I hope so) discussion, I have a request
>> for a new literal block.
>>
>> Currently, when looking at http://orgmode.org/manual/Literal-examples.html,
>> we
>> see we only have two "environments" that keep line breaks as the
23 matches
Mail list logo
