From: Dan Davison <dandavison7@gmail.com>
To: "Sébastien Vauban"
<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@lo.gmane.org>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: [Babel] Need for an extra literal block construct
Date: Sun, 21 Nov 2010 10:01:24 +0000 [thread overview]
Message-ID: <871v6fj8qz.fsf@gmail.com> (raw)
In-Reply-To: <80ipzrzmts.fsf@missioncriticalit.com> ("Sébastien Vauban"'s message of "Sat, 20 Nov 2010 22:50:39 +0100")
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 <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
writes:
> Hi Dan,
>
> 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 having to work hard to get
>> there!
>
> Hope this helps!
>
> #+TITLE: ecm-verse-2.txt
> #+DATE: 2010-11-20
> #+LANGUAGE: en_US
>
> #+LaTeX_CLASS: mcarticle
> #+LaTeX_CLASS_OPTIONS: [final]
>
> * Context
>
> There are clearly 3 key "concepts" to be able to distinguish in nice HTML
> output:
>
> - Code fragments :: text files that use the specific numbers of spaces and
> characters to line things up.
>
> - Sample output :: Output from programs, scripts or commands.
>
> - Text giving instructions :: Typically used for quoting passages of an email
> message.
>
> * Examples
>
> ** Code fragment
>
> #+begin_src emacs-lisp
> (update this-var)
> (echo "OK")
> #+end_src
>
> ** Sample output
>
> The results of code execution is currently (or /was/ -- I need to test the
> patch of Eric) translated into HTML as EXAMPLE.
>
> #+begin_src sh :results output :exports both
> ls *.org
> #+end_src
>
> #+results:
> | Agenda-Sorting-Strategy.org |
> | Clock-Report.org |
> | org-beamer-fpu-rules.org |
> | org-hist.org |
>
> ** Text giving instructions
>
> EXAMPLE begin taken, if I want another "verbatim" environment, the only left
> to me, in HTML, is VERSE.
>
> #+begin_verse
> 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
> #+end_verse
>
>
> From [[http://mid.gmane.org/87mxp5q6uf.fsf%40gmail.com][Email from Dan Davison: Re: {Babel} Need for an extra ]]
>
> *I'd expect to see all the above passage from the email to be uninterpreted*. It
> is not acting that way.
>
> See attachment for what I'm heading to.
>
>
>> p.s. However, your emails did motivate the following trivial function a
>> few months ago which I now use every day for various purposes.
>>
>> (defun dan/switch-to-org-scratch ()
>> "Switch to a temp Org buffer.
>> If the region is active, insert it."
>> (interactive)
>> (let ((contents
>> (and (region-active-p)
>> (buffer-substring (region-beginning)
>> (region-end)))))
>> (find-file "/tmp/org-scratch.org")
>> (if contents (insert contents))))
>
> Thanks for sharing this... Always interesting to see what others do, what does
> help them in their workflows...
>
> Best regards,
> Seb
next prev parent reply other threads:[~2010-11-21 10:02 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
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 [this message]
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=871v6fj8qz.fsf@gmail.com \
--to=dandavison7@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@lo.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).