emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bastien <bzg@altern.org>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org
Subject: Closing #+results: with #+end declaration?
Date: Sat, 26 Feb 2011 10:56:21 +0100	[thread overview]
Message-ID: <87hbbqepgz.fsf@altern.org> (raw)
In-Reply-To: 87zkpjfwew.fsf@gmail.com

Hi Eric,

"Eric Schulte" <schulte.eric@gmail.com> writes:

> #+begin_src sh :results list
>   echo "eric schulte"
>   echo "dan davison"
>   echo "seb vauban"
> #+end_src
>
> #+results:
> - ("eric" "schulte")
> - ("dan" "davison")
> - ("seb" "vauban")

reading this, I wonder if we should consider use this instead:

#+results:
- ("eric" "schulte")
- ("dan" "davison")
- ("seb" "vauban")
#+end

or better:

#+begin_results
- ("eric" "schulte")
- ("dan" "davison")
- ("seb" "vauban")
#+end_results

Looks more consistent with the rest of the #+begin* statements.

More generally, I've sometimes wondered why we need to use 

#+begin_*
#+end_*

instead of just

#+begin_*
#+end

Unless we allow nested #+begin blocks (and AFAIK we don't), there 
is no real need for being specific about what #+end ends.

What do you think?

-- 
 Bastien

next prev parent reply	other threads:[~2011-02-26 16:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04 16:00 [babel] How to kill two birds with one stone? Sébastien Vauban
2011-02-04 17:43 ` Dan Davison
2011-02-04 22:23   ` Sébastien Vauban
2011-02-06 16:51   ` Sébastien Vauban
2011-02-20  8:57     ` Eric Schulte
2011-02-25 14:27       ` Sébastien Vauban
2011-02-25 22:44         ` Nick Dokos
2011-02-25 22:55           ` Nick Dokos
2011-02-28 13:59           ` Sébastien Vauban
2011-02-26  0:24         ` Eric Schulte
2011-02-26  9:56           ` Bastien [this message]
2011-02-27 20:00             ` Closing #+results: with #+end declaration? Eric Schulte
2011-02-28 13:54               ` Sébastien Vauban
2011-03-03 11:11               ` Bastien
2011-02-28 15:16       ` [babel] How to kill two birds with one stone? 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=87hbbqepgz.fsf@altern.org \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.com \
    --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

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).