Re: Using sessions.

Re: Using sessions.

[abonnements]

[-- Attachment #1: Type: text/plain, Size: 601 bytes --]

Thank you.
I wonder if it is worth including this usage in the manual?


---------------------------------------
Hi Thierry,

abonnements<abonnements@thierry-pelle.eu>  writes:

> Hi,
>      I would like to know if it is possible to desactivate a previously
> "open session".
> Example :
> * Test
> :PROPERTIES:
> :HEAGER-ARGS: :session SESS-TEST
> :END:
>
> <....> some code in session mode
>
> #+begin_src python
> <...> some code for which I dont what to use the session.
> #+end_src
>
> Is there something like ":session NONE" or ":session DISABLE"?
>
There is:  ":session none"

Best,
Andreas




[-- Attachment #2: Type: text/html, Size: 1140 bytes --]

Re: Using sessions.

[Bastien]

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!

-- 
 Bastien

Re: Using sessions.

[abonnements]

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}

Using sessions.

[abonnements]

Hi,
    I would like to know if it is possible to desactivate a previously 
"open session".
Example :
* Test
:PROPERTIES:
:HEAGER-ARGS: :session SESS-TEST
:END:

<....> some code in session mode

#+begin_src python
<...> some code for which I dont what to use the session.
#+end_src

Is there something like ":session NONE" or ":session DISABLE"?

Thanks.
Thierry

Re: Using sessions.

[Andreas Leha]

Hi Thierry,

abonnements <abonnements@thierry-pelle.eu> writes:
> Hi,
>     I would like to know if it is possible to desactivate a previously 
> "open session".
> Example :
> * Test
> :PROPERTIES:
> :HEAGER-ARGS: :session SESS-TEST
> :END:
>
> <....> some code in session mode
>
> #+begin_src python
> <...> some code for which I dont what to use the session.
> #+end_src
>
> Is there something like ":session NONE" or ":session DISABLE"?
>

There is:  ":session none"

Best,
Andreas