Strange behavior of Out[]
$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
edited yesterday
Kuba♦
107k12210530
asked yesterday
user18792user18792
1,785915
$endgroup$
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
edited yesterday
Kuba♦
107k12210530
asked yesterday
user18792user18792
1,785915
$endgroup$
$begingroup$
The kernel state (including In/Out values) is not local to notebooks. This is expected.
$endgroup$
– Szabolcs
yesterday
$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
yesterday
$begingroup$
Right, now I see what you mean.primary.nbkeeps counting up from 1, yet higher input line values are already set inOutthanks toexternal.nb. It is indeed strange.
$endgroup$
– Szabolcs
yesterday
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
edited yesterday
Kuba♦
107k12210530
asked yesterday
user18792user18792
1,785915
$endgroup$
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
front-end kernel
edited yesterday
Kuba♦
107k12210530
asked yesterday
user18792user18792
1,785915
edited yesterday
Kuba♦
107k12210530
asked yesterday
user18792user18792
1,785915
edited yesterday
Kuba♦
107k12210530
edited yesterday
Kuba♦
107k12210530
edited yesterday
Kuba♦
107k12210530
107k12210530
asked yesterday
user18792user18792
1,785915
asked yesterday
user18792user18792
1,785915
asked yesterday
user18792user18792
1,785915
1,785915
$begingroup$
The kernel state (including In/Out values) is not local to notebooks. This is expected.
$endgroup$
– Szabolcs
yesterday
$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
yesterday
$begingroup$
Right, now I see what you mean.primary.nbkeeps counting up from 1, yet higher input line values are already set inOutthanks toexternal.nb. It is indeed strange.
$endgroup$
– Szabolcs
yesterday
add a comment |
$begingroup$
The kernel state (including In/Out values) is not local to notebooks. This is expected.
$endgroup$
– Szabolcs
yesterday
$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
yesterday
$begingroup$
Right, now I see what you mean.primary.nbkeeps counting up from 1, yet higher input line values are already set inOutthanks toexternal.nb. It is indeed strange.
$endgroup$
– Szabolcs
yesterday
$begingroup$
The kernel state (including In/Out values) is not local to notebooks. This is expected.
$endgroup$
– Szabolcs
yesterday
$begingroup$
The kernel state (including In/Out values) is not local to notebooks. This is expected.
$endgroup$
– Szabolcs
yesterday
$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
yesterday
$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
yesterday
$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
yesterday
$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
yesterday
add a comment |
1 Answer
1
active
oldest
votes
$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.
answered yesterday
SzabolcsSzabolcs
162k14443941
$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
16 hours ago
$begingroup$
@user18792 You can edit an.mfile 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
15 hours ago
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
});
}
});
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
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
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
$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.
answered yesterday
SzabolcsSzabolcs
162k14443941
$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
16 hours ago
$begingroup$
@user18792 You can edit an.mfile 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
15 hours ago
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.
answered yesterday
SzabolcsSzabolcs
162k14443941
$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
16 hours ago
$begingroup$
@user18792 You can edit an.mfile 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
15 hours ago
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.
answered yesterday
SzabolcsSzabolcs
162k14443941
$endgroup$
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.
answered yesterday
SzabolcsSzabolcs
162k14443941
answered yesterday
SzabolcsSzabolcs
162k14443941
answered yesterday
SzabolcsSzabolcs
162k14443941
answered yesterday
SzabolcsSzabolcs
162k14443941
162k14443941
$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
16 hours ago
$begingroup$
@user18792 You can edit an.mfile 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
15 hours ago
add a comment |
$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
16 hours ago
$begingroup$
@user18792 You can edit an.mfile 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
15 hours ago
$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
16 hours ago
$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
16 hours ago
$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
15 hours ago
$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
15 hours ago
add a comment |
Thanks for contributing an answer to Mathematica Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
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
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
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
$begingroup$
The kernel state (including In/Out values) is not local to notebooks. This is expected.
$endgroup$
– Szabolcs
yesterday
$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
yesterday
$begingroup$
Right, now I see what you mean.
primary.nbkeeps counting up from 1, yet higher input line values are already set inOutthanks toexternal.nb. It is indeed strange.$endgroup$
– Szabolcs
yesterday