emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Fri, 19 Nov 2010 21:12:04 +0100	[thread overview]
Message-ID: <8039qx3wff.fsf@missioncriticalit.com> (raw)
In-Reply-To: 4CE694F1.2050409@christianmoe.com

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 they are in the
>> Org buffer, that is SRC and EXAMPLE, both mapped in HTML to PRE.
>
> There's VERSE, too.

#+TITLE:     Is VERSE a real PRE environment?
#+DATE:      2010-11-19
#+LANGUAGE:  en_US

If VERSE was really handled "verbatim" (for lists, etc.), then, yes,
definitively, I don't need a new "environment" for emails. Was forgetting
about that one, thanks for the reminder!

Though, if the following is not a bug, but a deliberative choice, then no,
it's not what I'm looking for...

* Source block

** Source

#+begin_src emacs-lisp
(update this-var)
(echo "OK")
#+end_src

** Results

#+begin_example
<pre class="src src-emacs-lisp">(update this-var)
(echo <span class="org-string">"OK"</span>)
</pre>
#+end_example

* Example

** Source

#+begin_example
>> Does it work?
>
> Yes, if you:
> - update =this-var=
> - restart

OK. Confirmed, but you need to:
1. delete the =cache=.
2. redo it.

Thanks to:
- you
- me
#+end_example

** Results

#+begin_example
<pre class="example">&gt;&gt; Does it work?
&gt;
&gt; Yes, if you:
&gt; - update =this-var=
&gt; - restart

OK. Confirmed, but you need to:
1. delete the =cache=.
2. redo it.

Thanks to:
- you
- me
</pre>
#+end_example

* Verse

** Source

#+begin_verse
>> Does it work?
>
> Yes, if you:
> - update =this-var=
> - restart

OK. Confirmed, but you need to:
1. delete the =cache=.
2. redo it.

Thanks to:
- you
- me
#+end_verse

** Results

#+begin_example
<p class="verse">
&gt;&gt; Does it work?<br/>
&gt;<br/>
&gt; Yes, if you:<br/>

&gt; - update <code>this-var</code><br/>
&gt; - restart<br/>
<br/>
OK. Confirmed, but you need to:<br/>
</p><ol>
<li>
delete the <code>cache</code>.<br/>
</li>

<li>
redo it.<br/>
<br/>
Thanks to:<br/>
</li>
<li>
you<br/>
</li>
<li>
me<br/>
</p>
#+end_example

** Right thing or wrong thing?

The verse "mail" is badly translated into HTML:

1. lists are not copied "verbatim" in the PRE
2. they're even wrong: mix of OL and UL, because there is no ending /OL...

While the second is clearly a bug, what about the first point?

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

  reply	other threads:[~2010-11-19 20:12 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 [this message]
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
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

  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=8039qx3wff.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 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).