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

From: Aaron Ecay <aaronecay@gmail.com>
To: abonnements@thierry-pelle.eu, emacs-orgmode@gnu.org
Subject: Re: [PATCH] Proposal for «session»  documentation
Date: Sun, 21 Dec 2014 22:27:20 -0500	[thread overview]
Message-ID: <8761d42wkn.fsf@gmail.com> (raw)
In-Reply-To: <86ioh58h0d.fsf@Evon.thierry-pelle.eu>

Hi Thierry,

Juts a two comments and one question.

2014ko abenudak 21an, Thierry Pellé-ek idatzi zuen:
> 
> Hi,
>   I added description for empty names and used the suggestion of Aaron.
> 
> Hope it's not too frenchy ;-)
> 
> 
> diff --git a/doc/org.texi b/doc/org.texi
> index 3612bba..72ad0d9 100644
> --- a/doc/org.texi
> +++ b/doc/org.texi
> @@ -15559,8 +15559,8 @@ execution.
>  @subsubsection @code{:session}
>  @cindex @code{:session}, src header argument
>  
> -The @code{:session} header argument starts a session for an interpreted
> -language where state is preserved.  By default, a session is not started.
> +The @code{:session} header argument starts a (possibly named) session for an interpreted
> +language where state is preserved.  All code blocks sharing the same name are exectuted by the same interpreter process.  By default, a session is not started.
>  
>  @itemize @bullet
>  @item @code{none}
> @@ -15568,9 +15568,10 @@ The default.  Each block is evaluated in its own session.  The session is
>  not preserved after the evaluation.
>  @item @code{other}
>  Any other string passed to the @code{:session} header argument will give the
> -session a name.  All blocks with the same session name share the same
> -session.  Using different session name enables concurrent sessions (even for
> -the same interpreted language).  E.g., @code{:session mysession}.
> +session a name.  If the given name is empty, the session is named as the

“according to” instead of “as”

> +language used in the block.  All blocks with the same session name share the
> +same session.  Using different session name enables concurrent sessions (even
> +for the same interpreted language).  E.g., @code{:session mysession}.

I would move the “e.g.” directly after the sentence which ends “give the
session a name.”

Can you send a patch generated with “git format-patch”?  This way you
can write and include a commit message.  The procedure is described
here: <http://orgmode.org/worg/org-contribute.html#unnumbered-4>.

Thanks,

-- 
Aaron Ecay

next prev parent reply	other threads:[~2014-12-22  3:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-21  9:54 [PATCH] Proposal for «session» documentation Thierry Pellé
2014-12-22  3:27 ` Aaron Ecay [this message]
     [not found]   ` <5497D44F.9040105@thierry-pelle.eu>
     [not found]     ` <CAFcZrT3mbz2Ny6Ge-axJ5UKzN_3qGYJippywGSxLgEUk=6T4Xw@mail.gmail.com>
     [not found]       ` <5497EB3A.2050906@thierry-pelle.eu>
2015-01-17  3:48         ` Aaron Ecay
2015-01-17  7:20           ` abonnements
2015-01-17  9:39             ` Achim Gratz
2014-12-22 10:50 ` Rasmus

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=8761d42wkn.fsf@gmail.com \
    --to=aaronecay@gmail.com \
    --cc=abonnements@thierry-pelle.eu \
    --cc=emacs-orgmode@gnu.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

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