From: abonnements <abonnements@thierry-pelle.eu>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Using sessions.
Date: Mon, 01 Dec 2014 17:48:35 +0100 [thread overview]
Message-ID: <547C9BE3.6090707@thierry-pelle.eu> (raw)
In-Reply-To: <87a937wfx5.fsf@bzg.ath.cx>
Le 01/12/2014 16:25, Bastien a écrit :
> abonnements <abonnements@thierry-pelle.eu> writes:
>
>> I wonder if it is worth including this usage in the manual?
> Can you specify the suggestion by sending a patch?
>
> Thanks!
>
Hi, sorry if this is the second time I send it but the first time failed
(for my MUA).
I hope this work, it's the first time I dare...
diff --git a/doc/org.texi b/doc/org.texi
index d508c06..c229187 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -15563,13 +15563,18 @@ execution.
@cindex @code{:session}, src header argument
The @code{:session} header argument starts a session for an interpreted
-language where state is preserved.
+language where state is preserved. By default, a session is not started.
-By default, a session is not started.
-
-A string passed to the @code{:session} header argument will give the session
-a name. This makes it possible to run concurrent sessions for each
-interpreted language.
+@itemize @bullet
+@item @code{none}
+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}.
+@end itemize
@node noweb
@subsubsection @code{:noweb}
next prev parent reply other threads:[~2014-12-01 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 6:47 Using sessions abonnements
2014-12-01 15:25 ` Bastien
2014-12-01 16:48 ` abonnements [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-26 10:03 abonnements
2014-10-26 14:19 ` Andreas Leha
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=547C9BE3.6090707@thierry-pelle.eu \
--to=abonnements@thierry-pelle.eu \
--cc=bzg@gnu.org \
--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
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).