[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Using sessions.
From: |
abonnements |
Subject: |
Re: [O] Using sessions. |
Date: |
Mon, 01 Dec 2014 17:48:35 +0100 |
User-agent: |
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
Le 01/12/2014 16:25, Bastien a écrit :
abonnements <address@hidden> 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.
address@hidden @bullet
address@hidden @code{none}
+The default. Each block is evaluated in its own session. The session is
+not preserved after the evaluation.
address@hidden @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}.
address@hidden itemize
@node noweb
@subsubsection @code{:noweb}