Dtjytyk

How to format long polynomial?

Approximately how much travel time was saved by the opening of the Suez Canal in 1869?

Can a vampire attack twice with their claws using Multiattack?

Arrow those variables!

Are the number of citations and number of published articles the most important criteria for a tenure promotion?

Did Shadowfax go to Valinor?

infared filters v nd

What does "Puller Prush Person" mean?

Codimension of non-flat locus

Is it unprofessional to ask if a job posting on GlassDoor is real?

Do I have a twin with permutated remainders?

Doing something right before you need it - expression for this?

Perform and show arithmetic with LuaLaTeX

Cross compiling for RPi - error while loading shared libraries

meaning of に in 本当に?

Was any UN Security Council vote triple-vetoed?

Today is the Center

RSA: Danger of using p to create q

Paid for article while in US on F-1 visa?

How can I prevent hyper evolved versions of regular creatures from wiping out their cousins?

Are astronomers waiting to see something in an image from a gravitational lens that they've already seen in an adjacent image?

Can a Cauchy sequence converge for one metric while not converging for another?

Why is consensus so controversial in Britain?

Maximum likelihood parameters deviate from posterior distributions

Strange behavior of Out[]

How do I extract the contents of a selected cell as plain text?How to make a parallel auto-generated .m package from Initialization cells?Making flash cards with MathematicaDifference between double quotesHow is CellContext->CellGroup supposed to work?Automatic shading of all InitializationCell->True cells in older versions“Find currently evaluating cell” does not seem to work correctlyExporting notebooks inserts unwanted $CellContext. Workaround?Stop notebook from auto-scrolling upon printingDocked Cell Slider that controls magnification of Output Cells only

7

$begingroup$

Let's create two notebooks external.nb and primary.nb. Then call the external.nb notebook from the primary.nb and investigate values of Out[ ]. The context of the external notebook is not important, however for the demonstration of the strange behavior it should contain number of cells. My external.nb notebook contains 4 cells:

a=1; 

---

b=1

---

c=1

---

d

The primary notebook contains the single cell which calls the external notebook from the primary. If we put both notebooks in the same directory, the cell is

NotebookEvaluate @ FileNameJoin[

  { NotebookDirectory[EvaluationNotebook[]], "external.nb"}

]

Open the primary.nb and evaluate the cell which calls the evaluation of the external.nb.

The output yields

Out[1] = d

So it returns output of the last cell of the called notebook.

Now refer to input %4 of primary.nb. I would expect an empty output, since at the moment there is no %4 out in the primary notebook. However the result is the same d.

Asking

?? Out[]

we see the primary.nb knows all Out[] values of the external.nb notebook. Bug or feature?

front-end kernel

share|improve this question

edited Mar 19 at 11:27

Kuba♦

107k12211533

asked Mar 19 at 11:22

user18792user18792

1,785915

$endgroup$

• 
  
  
  

  
  

  
  
  
  
  
  

  
  $begingroup$
  The kernel state (including In/Out values) is not local to notebooks. This is expected.
  $endgroup$
  – Szabolcs
  Mar 19 at 12:05
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $begingroup$
  That is clear, however why then not to continue the enumeration from the last Out[ ] value the kernel knows in the new notebook? I find this confusing.
  $endgroup$
  – user18792
  Mar 19 at 12:17
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $begingroup$
  Right, now I see what you mean. primary.nb keeps counting up from 1, yet higher input line values are already set in Out thanks to external.nb. It is indeed strange.
  $endgroup$
  – Szabolcs
  Mar 19 at 12:22
  

  
  
  
  

add a comment | 

7

$begingroup$

Let's create two notebooks external.nb and primary.nb. Then call the external.nb notebook from the primary.nb and investigate values of Out[ ]. The context of the external notebook is not important, however for the demonstration of the strange behavior it should contain number of cells. My external.nb notebook contains 4 cells:

a=1; 

---

b=1

---

c=1

---

d

The primary notebook contains the single cell which calls the external notebook from the primary. If we put both notebooks in the same directory, the cell is

NotebookEvaluate @ FileNameJoin[

  { NotebookDirectory[EvaluationNotebook[]], "external.nb"}

]

Open the primary.nb and evaluate the cell which calls the evaluation of the external.nb.

The output yields

Out[1] = d

So it returns output of the last cell of the called notebook.

Now refer to input %4 of primary.nb. I would expect an empty output, since at the moment there is no %4 out in the primary notebook. However the result is the same d.

Asking

?? Out[]

we see the primary.nb knows all Out[] values of the external.nb notebook. Bug or feature?

front-end kernel

share|improve this question

edited Mar 19 at 11:27

Kuba♦

107k12211533

asked Mar 19 at 11:22

user18792user18792

1,785915

$endgroup$

• 
  
  
  

  
  

  
  
  
  
  
  

  
  $begingroup$
  The kernel state (including In/Out values) is not local to notebooks. This is expected.
  $endgroup$
  – Szabolcs
  Mar 19 at 12:05
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $begingroup$
  That is clear, however why then not to continue the enumeration from the last Out[ ] value the kernel knows in the new notebook? I find this confusing.
  $endgroup$
  – user18792
  Mar 19 at 12:17
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $begingroup$
  Right, now I see what you mean. primary.nb keeps counting up from 1, yet higher input line values are already set in Out thanks to external.nb. It is indeed strange.
  $endgroup$
  – Szabolcs
  Mar 19 at 12:22
  

  
  
  
  

add a comment | 

$begingroup$

Let's create two notebooks external.nb and primary.nb. Then call the external.nb notebook from the primary.nb and investigate values of Out[ ]. The context of the external notebook is not important, however for the demonstration of the strange behavior it should contain number of cells. My external.nb notebook contains 4 cells:

a=1; 

---

b=1

---

c=1

---

d

The primary notebook contains the single cell which calls the external notebook from the primary. If we put both notebooks in the same directory, the cell is

NotebookEvaluate @ FileNameJoin[

  { NotebookDirectory[EvaluationNotebook[]], "external.nb"}

]

Open the primary.nb and evaluate the cell which calls the evaluation of the external.nb.

The output yields

Out[1] = d

So it returns output of the last cell of the called notebook.

Now refer to input %4 of primary.nb. I would expect an empty output, since at the moment there is no %4 out in the primary notebook. However the result is the same d.

Asking

?? Out[]

we see the primary.nb knows all Out[] values of the external.nb notebook. Bug or feature?

front-end kernel

share|improve this question

edited Mar 19 at 11:27

Kuba♦

107k12211533

asked Mar 19 at 11:22

user18792user18792

1,785915

$endgroup$

a=1; 

b=1

c=1

d

NotebookEvaluate @ FileNameJoin[

  { NotebookDirectory[EvaluationNotebook[]], "external.nb"}

]

Out[1] = d

?? Out[]

share|improve this question

edited Mar 19 at 11:27

Kuba♦

107k12211533

asked Mar 19 at 11:22

user18792user18792

1,785915

share|improve this question

edited Mar 19 at 11:27

Kuba♦

107k12211533

asked Mar 19 at 11:22

user18792user18792

1,785915

edited Mar 19 at 11:27

Kuba♦

107k12211533

edited Mar 19 at 11:27

Kuba♦

107k12211533

asked Mar 19 at 11:22

user18792user18792

1,785915

asked Mar 19 at 11:22

user18792user18792

1,785915

1 Answer
1

active

oldest

votes

7

$begingroup$

I am guessing that this has to do with the following note in the NotebookEvaluate documentation:

The cells of the notebook are evaluated in a dialog subsession.

Here is an example session demonstrating similar behaviour:

See Dialog if you are not familiar with it.

Within the dialog, $Line keeps getting incremented as usual, and Out values are set. But once the dialog finishes, $Line is reset to its original value.

This is documented:

Dialog automatically localizes the values of $Line, $MessageList, and $Epilog.

Side note: A dialog is something you would normally encounter not when explicitly entering it, but when interrupting evaluation or when debugging (say, you set the debugger to break on a message/assert). Try e.g. Do[Pause[1], {i, 30}], then interrupt using Alt-, (Option-Command-. on Mac). Now you can evaluate i to check its value, or examine the kernel state in other ways. Exit the dialog using Return[]. It is natural that one would not want these evaluations to influence $Line once the dialog has finished.

share|improve this answer

answered Mar 19 at 12:29

SzabolcsSzabolcs

163k14447944

$endgroup$

• 
  
  
  

  
  

  
  
  
  
  
  

  
  $begingroup$
  Since the behavior is documented I conclude this is the intended design feature. I use NotebookEvaluate for package development, because it is much more convenient way to add new definitions and navigate in the many cell notebook than in plain .m file. I think I will try to add Clear[Out] as the last cell in the external.nb.
  $endgroup$
  – user18792
  Mar 20 at 7:29
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $begingroup$
  @user18792 You can edit an .m file as if it were a notebook. You can add section cells and text cells. You can close and open section cells. Try it.
  $endgroup$
  – Szabolcs
  Mar 20 at 8:47
  
  
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ifUsing("editor", function () {
return StackExchange.using("mathjaxEditing", function () {
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["$", "$"], ["\\(","\\)"]]);
});
});
}, "mathjax-editing");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "387"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmathematica.stackexchange.com%2fquestions%2f193547%2fstrange-behavior-of-out%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

7

$begingroup$

I am guessing that this has to do with the following note in the NotebookEvaluate documentation:

The cells of the notebook are evaluated in a dialog subsession.

Here is an example session demonstrating similar behaviour:

See Dialog if you are not familiar with it.

Within the dialog, $Line keeps getting incremented as usual, and Out values are set. But once the dialog finishes, $Line is reset to its original value.

This is documented:

Dialog automatically localizes the values of $Line, $MessageList, and $Epilog.

Side note: A dialog is something you would normally encounter not when explicitly entering it, but when interrupting evaluation or when debugging (say, you set the debugger to break on a message/assert). Try e.g. Do[Pause[1], {i, 30}], then interrupt using Alt-, (Option-Command-. on Mac). Now you can evaluate i to check its value, or examine the kernel state in other ways. Exit the dialog using Return[]. It is natural that one would not want these evaluations to influence $Line once the dialog has finished.

share|improve this answer

answered Mar 19 at 12:29

SzabolcsSzabolcs

163k14447944

$endgroup$

• 
  
  
  

  
  

  
  
  
  
  
  

  
  $begingroup$
  Since the behavior is documented I conclude this is the intended design feature. I use NotebookEvaluate for package development, because it is much more convenient way to add new definitions and navigate in the many cell notebook than in plain .m file. I think I will try to add Clear[Out] as the last cell in the external.nb.
  $endgroup$
  – user18792
  Mar 20 at 7:29
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $begingroup$
  @user18792 You can edit an .m file as if it were a notebook. You can add section cells and text cells. You can close and open section cells. Try it.
  $endgroup$
  – Szabolcs
  Mar 20 at 8:47
  
  
  

  
  
  
  

add a comment | 

7

$begingroup$

I am guessing that this has to do with the following note in the NotebookEvaluate documentation:

The cells of the notebook are evaluated in a dialog subsession.

Here is an example session demonstrating similar behaviour:

See Dialog if you are not familiar with it.

Within the dialog, $Line keeps getting incremented as usual, and Out values are set. But once the dialog finishes, $Line is reset to its original value.

This is documented:

Dialog automatically localizes the values of $Line, $MessageList, and $Epilog.

Side note: A dialog is something you would normally encounter not when explicitly entering it, but when interrupting evaluation or when debugging (say, you set the debugger to break on a message/assert). Try e.g. Do[Pause[1], {i, 30}], then interrupt using Alt-, (Option-Command-. on Mac). Now you can evaluate i to check its value, or examine the kernel state in other ways. Exit the dialog using Return[]. It is natural that one would not want these evaluations to influence $Line once the dialog has finished.

share|improve this answer

answered Mar 19 at 12:29

SzabolcsSzabolcs

163k14447944

$endgroup$

• 
  
  
  

  
  

  
  
  
  
  
  

  
  $begingroup$
  Since the behavior is documented I conclude this is the intended design feature. I use NotebookEvaluate for package development, because it is much more convenient way to add new definitions and navigate in the many cell notebook than in plain .m file. I think I will try to add Clear[Out] as the last cell in the external.nb.
  $endgroup$
  – user18792
  Mar 20 at 7:29
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $begingroup$
  @user18792 You can edit an .m file as if it were a notebook. You can add section cells and text cells. You can close and open section cells. Try it.
  $endgroup$
  – Szabolcs
  Mar 20 at 8:47
  
  
  

  
  
  
  

add a comment | 

$begingroup$

I am guessing that this has to do with the following note in the NotebookEvaluate documentation:

The cells of the notebook are evaluated in a dialog subsession.

Here is an example session demonstrating similar behaviour:

See Dialog if you are not familiar with it.

Within the dialog, $Line keeps getting incremented as usual, and Out values are set. But once the dialog finishes, $Line is reset to its original value.

This is documented:

Dialog automatically localizes the values of $Line, $MessageList, and $Epilog.

Side note: A dialog is something you would normally encounter not when explicitly entering it, but when interrupting evaluation or when debugging (say, you set the debugger to break on a message/assert). Try e.g. Do[Pause[1], {i, 30}], then interrupt using Alt-, (Option-Command-. on Mac). Now you can evaluate i to check its value, or examine the kernel state in other ways. Exit the dialog using Return[]. It is natural that one would not want these evaluations to influence $Line once the dialog has finished.

share|improve this answer

answered Mar 19 at 12:29

SzabolcsSzabolcs

163k14447944

$endgroup$

share|improve this answer

answered Mar 19 at 12:29

SzabolcsSzabolcs

163k14447944

answered Mar 19 at 12:29

SzabolcsSzabolcs

163k14447944

answered Mar 19 at 12:29

SzabolcsSzabolcs

163k14447944