Different file opened by openin (was: between 2017 and 2018)
Short version:
It seems that some trivial behavior of file opening (openin) changed between TeX Live 2017 and 2018 differs between environment. I did not see any notice about that, but why?
Consider the following code:
openin1 read1 to X closein1 showX
Normally openin should be followed by a file, but here that is omitted. TeX/e-TeX/e-(u)pTeX/XeTeX/LuaTeX of Overleaf (TL2017) and Japanese TeX on Web (TL2016; only e-pTeX available) showed par, but my local installation (TL2018) and Cloud LaTeX (TL2017) shows nothing (empty).
Similar difference with e-TeX:
openin1 readline1 toXshowXreadline1 toXshowXreadline1 toXshowXclosein1 bye
e-TeX of Overleaf returned only ^^M and stopped, but that of my local installation shows:
> X=macro:
->%%^^M.
<*> openin1 readline1 toXshowX
readline1 toXshowXreadline1 toXsho...
?
> X=macro:
->%% This is file `.tex',^^M.
<*> ...readline1 toXshowXreadline1 toXshowX
readline1 toXshowXclo...
?
> X=macro:
->%% generated with the docstrip utility.^^M.
<*> ...readline1 toXshowXreadline1 toXshowX
closein1 bye
?
No pages of output.
The followings are my guess from these behavior:
- terminal was read in Overleaf, Japanese TeX on Web
tools/.texis being read in my local installation, Cloud LaTeX
I don't think this is a problem; just for curiosity.
tex-core filesystem-access primitives
asked 1 hour ago
Hironobu YAMASHITA
46736
|
show 4 more comments
Short version:
It seems that some trivial behavior of file opening (openin) changed between TeX Live 2017 and 2018 differs between environment. I did not see any notice about that, but why?
Consider the following code:
openin1 read1 to X closein1 showX
Normally openin should be followed by a file, but here that is omitted. TeX/e-TeX/e-(u)pTeX/XeTeX/LuaTeX of Overleaf (TL2017) and Japanese TeX on Web (TL2016; only e-pTeX available) showed par, but my local installation (TL2018) and Cloud LaTeX (TL2017) shows nothing (empty).
Similar difference with e-TeX:
openin1 readline1 toXshowXreadline1 toXshowXreadline1 toXshowXclosein1 bye
e-TeX of Overleaf returned only ^^M and stopped, but that of my local installation shows:
> X=macro:
->%%^^M.
<*> openin1 readline1 toXshowX
readline1 toXshowXreadline1 toXsho...
?
> X=macro:
->%% This is file `.tex',^^M.
<*> ...readline1 toXshowXreadline1 toXshowX
readline1 toXshowXclo...
?
> X=macro:
->%% generated with the docstrip utility.^^M.
<*> ...readline1 toXshowXreadline1 toXshowX
closein1 bye
?
No pages of output.
The followings are my guess from these behavior:
- terminal was read in Overleaf, Japanese TeX on Web
tools/.texis being read in my local installation, Cloud LaTeX
I don't think this is a problem; just for curiosity.
tex-core filesystem-access primitives
asked 1 hour ago
Hironobu YAMASHITA
46736
1
I can't reproduce the issue.
– egreg
1 hour ago
Hmm, I tested on both Linux and Mac.
– Hironobu YAMASHITA
1 hour ago
@egreg Which behavior you get?
– Hironobu YAMASHITA
1 hour ago
1
I can't reproduce difference with etex with TL2016, 2017 (MacPorts binaries), and TL2018 (self-compiled binaries). They all behave as in your question.
– jfbu
1 hour ago
@HironobuYAMASHITA I always get->.afterX=macro:(that is, empty).
– egreg
1 hour ago
|
show 4 more comments
Short version:
It seems that some trivial behavior of file opening (openin) changed between TeX Live 2017 and 2018 differs between environment. I did not see any notice about that, but why?
Consider the following code:
openin1 read1 to X closein1 showX
Normally openin should be followed by a file, but here that is omitted. TeX/e-TeX/e-(u)pTeX/XeTeX/LuaTeX of Overleaf (TL2017) and Japanese TeX on Web (TL2016; only e-pTeX available) showed par, but my local installation (TL2018) and Cloud LaTeX (TL2017) shows nothing (empty).
Similar difference with e-TeX:
openin1 readline1 toXshowXreadline1 toXshowXreadline1 toXshowXclosein1 bye
e-TeX of Overleaf returned only ^^M and stopped, but that of my local installation shows:
> X=macro:
->%%^^M.
<*> openin1 readline1 toXshowX
readline1 toXshowXreadline1 toXsho...
?
> X=macro:
->%% This is file `.tex',^^M.
<*> ...readline1 toXshowXreadline1 toXshowX
readline1 toXshowXclo...
?
> X=macro:
->%% generated with the docstrip utility.^^M.
<*> ...readline1 toXshowXreadline1 toXshowX
closein1 bye
?
No pages of output.
The followings are my guess from these behavior:
- terminal was read in Overleaf, Japanese TeX on Web
tools/.texis being read in my local installation, Cloud LaTeX
I don't think this is a problem; just for curiosity.
tex-core filesystem-access primitives
asked 1 hour ago
Hironobu YAMASHITA
46736
Short version:
It seems that some trivial behavior of file opening (openin) changed between TeX Live 2017 and 2018 differs between environment. I did not see any notice about that, but why?
Consider the following code:
openin1 read1 to X closein1 showX
Normally openin should be followed by a file, but here that is omitted. TeX/e-TeX/e-(u)pTeX/XeTeX/LuaTeX of Overleaf (TL2017) and Japanese TeX on Web (TL2016; only e-pTeX available) showed par, but my local installation (TL2018) and Cloud LaTeX (TL2017) shows nothing (empty).
Similar difference with e-TeX:
openin1 readline1 toXshowXreadline1 toXshowXreadline1 toXshowXclosein1 bye
e-TeX of Overleaf returned only ^^M and stopped, but that of my local installation shows:
> X=macro:
->%%^^M.
<*> openin1 readline1 toXshowX
readline1 toXshowXreadline1 toXsho...
?
> X=macro:
->%% This is file `.tex',^^M.
<*> ...readline1 toXshowXreadline1 toXshowX
readline1 toXshowXclo...
?
> X=macro:
->%% generated with the docstrip utility.^^M.
<*> ...readline1 toXshowXreadline1 toXshowX
closein1 bye
?
No pages of output.
The followings are my guess from these behavior:
- terminal was read in Overleaf, Japanese TeX on Web
tools/.texis being read in my local installation, Cloud LaTeX
I don't think this is a problem; just for curiosity.
tex-core filesystem-access primitives
tex-core filesystem-access primitives
asked 1 hour ago
Hironobu YAMASHITA
46736
asked 1 hour ago
Hironobu YAMASHITA
46736
edited 23 mins ago
asked 1 hour ago
Hironobu YAMASHITA
46736
asked 1 hour ago
Hironobu YAMASHITA
46736
asked 1 hour ago
Hironobu YAMASHITA
46736
46736
1
I can't reproduce the issue.
– egreg
1 hour ago
Hmm, I tested on both Linux and Mac.
– Hironobu YAMASHITA
1 hour ago
@egreg Which behavior you get?
– Hironobu YAMASHITA
1 hour ago
1
I can't reproduce difference with etex with TL2016, 2017 (MacPorts binaries), and TL2018 (self-compiled binaries). They all behave as in your question.
– jfbu
1 hour ago
@HironobuYAMASHITA I always get->.afterX=macro:(that is, empty).
– egreg
1 hour ago
|
show 4 more comments
1
I can't reproduce the issue.
– egreg
1 hour ago
Hmm, I tested on both Linux and Mac.
– Hironobu YAMASHITA
1 hour ago
@egreg Which behavior you get?
– Hironobu YAMASHITA
1 hour ago
1
I can't reproduce difference with etex with TL2016, 2017 (MacPorts binaries), and TL2018 (self-compiled binaries). They all behave as in your question.
– jfbu
1 hour ago
@HironobuYAMASHITA I always get->.afterX=macro:(that is, empty).
– egreg
1 hour ago
1
1
I can't reproduce the issue.
– egreg
1 hour ago
I can't reproduce the issue.
– egreg
1 hour ago
Hmm, I tested on both Linux and Mac.
– Hironobu YAMASHITA
1 hour ago
Hmm, I tested on both Linux and Mac.
– Hironobu YAMASHITA
1 hour ago
@egreg Which behavior you get?
– Hironobu YAMASHITA
1 hour ago
@egreg Which behavior you get?
– Hironobu YAMASHITA
1 hour ago
1
1
I can't reproduce difference with etex with TL2016, 2017 (MacPorts binaries), and TL2018 (self-compiled binaries). They all behave as in your question.
– jfbu
1 hour ago
I can't reproduce difference with etex with TL2016, 2017 (MacPorts binaries), and TL2018 (self-compiled binaries). They all behave as in your question.
– jfbu
1 hour ago
@HironobuYAMASHITA I always get
->. after X=macro: (that is, empty).– egreg
1 hour ago
@HironobuYAMASHITA I always get
->. after X=macro: (that is, empty).– egreg
1 hour ago
|
show 4 more comments
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
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%2ftex.stackexchange.com%2fquestions%2f467666%2fdifferent-file-opened-by-openin-was-between-2017-and-2018%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to TeX - LaTeX 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.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
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%2ftex.stackexchange.com%2fquestions%2f467666%2fdifferent-file-opened-by-openin-was-between-2017-and-2018%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
1
I can't reproduce the issue.
– egreg
1 hour ago
Hmm, I tested on both Linux and Mac.
– Hironobu YAMASHITA
1 hour ago
@egreg Which behavior you get?
– Hironobu YAMASHITA
1 hour ago
1
I can't reproduce difference with etex with TL2016, 2017 (MacPorts binaries), and TL2018 (self-compiled binaries). They all behave as in your question.
– jfbu
1 hour ago
@HironobuYAMASHITA I always get
->.afterX=macro:(that is, empty).– egreg
1 hour ago