Mixing
ZSH thinks unterminated quote if preceded by exclamation mark (!)
I have zsh 5.3 (through oh-my-zsh), if I run echo --message="foo!", I get unterminated quote prompt on the next line:
$ echo --message="foo!"
dquote>
This doesn' happen in bash.
When I drop the ! character from the argument, it works fine:
$ echo --message="foo"
--message=foo
What’s happening here?
I should also note that if I answer the unterminated quote prompt with " and hit return, I get this output, which totally drops the !:
$ echo --message="foo!"
dquote> "
--message=foo
zsh
asked Jan 29 at 2:45
Ahmet Alp BalkanAhmet Alp Balkan
1769
add a comment |
I have zsh 5.3 (through oh-my-zsh), if I run echo --message="foo!", I get unterminated quote prompt on the next line:
$ echo --message="foo!"
dquote>
This doesn' happen in bash.
When I drop the ! character from the argument, it works fine:
$ echo --message="foo"
--message=foo
What’s happening here?
I should also note that if I answer the unterminated quote prompt with " and hit return, I get this output, which totally drops the !:
$ echo --message="foo!"
dquote> "
--message=foo
zsh
asked Jan 29 at 2:45
Ahmet Alp BalkanAhmet Alp Balkan
1769
add a comment |
I have zsh 5.3 (through oh-my-zsh), if I run echo --message="foo!", I get unterminated quote prompt on the next line:
$ echo --message="foo!"
dquote>
This doesn' happen in bash.
When I drop the ! character from the argument, it works fine:
$ echo --message="foo"
--message=foo
What’s happening here?
I should also note that if I answer the unterminated quote prompt with " and hit return, I get this output, which totally drops the !:
$ echo --message="foo!"
dquote> "
--message=foo
zsh
asked Jan 29 at 2:45
Ahmet Alp BalkanAhmet Alp Balkan
1769
I have zsh 5.3 (through oh-my-zsh), if I run echo --message="foo!", I get unterminated quote prompt on the next line:
$ echo --message="foo!"
dquote>
This doesn' happen in bash.
When I drop the ! character from the argument, it works fine:
$ echo --message="foo"
--message=foo
What’s happening here?
I should also note that if I answer the unterminated quote prompt with " and hit return, I get this output, which totally drops the !:
$ echo --message="foo!"
dquote> "
--message=foo
zsh
zsh
asked Jan 29 at 2:45
Ahmet Alp BalkanAhmet Alp Balkan
1769
asked Jan 29 at 2:45
Ahmet Alp BalkanAhmet Alp Balkan
1769
asked Jan 29 at 2:45
Ahmet Alp BalkanAhmet Alp Balkan
1769
asked Jan 29 at 2:45
Ahmet Alp BalkanAhmet Alp Balkan
1769
asked Jan 29 at 2:45
Ahmet Alp BalkanAhmet Alp Balkan
1769
1769
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
That's the history expansion at work.
This is what the zshexpn(1) manpage says about it:
If the shell encounters the character sequence
!"in the input, the
history mechanism is temporarily disabled until the current list (see
zshmisc(1)) is fully parsed. The!"is removed from the input, and
any subsequent!characters have no special significance.
answered Jan 29 at 2:58
mosvymosvy
8,8621833
1
So as either escape"foo!"or use single quotes'foo!'. Or even"foo!"!",!" "foo!", etc..
– Sparhawk
Jan 29 at 3:03
1
What is it expanding? The manpage makes it sound like!"is a special token that disables "the history mechanism", which I assume means it prevents the current line from appearing in the previous command list/history buffer? Wouldn't that be more like 'history compression (or perhaps, excision)'?
– aroth
Jan 29 at 10:12
"history expansion" is the official name of this!feature -- you call it "csh bangs" if you like. And!"does no more than told in that paragraph; in particular, it does not prevent the current line from being pushed in the history -- why should it?
– mosvy
Jan 29 at 12:29
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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%2funix.stackexchange.com%2fquestions%2f497328%2fzsh-thinks-unterminated-quote-if-preceded-by-exclamation-mark%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
That's the history expansion at work.
This is what the zshexpn(1) manpage says about it:
If the shell encounters the character sequence
!"in the input, the
history mechanism is temporarily disabled until the current list (see
zshmisc(1)) is fully parsed. The!"is removed from the input, and
any subsequent!characters have no special significance.
answered Jan 29 at 2:58
mosvymosvy
8,8621833
1
So as either escape"foo!"or use single quotes'foo!'. Or even"foo!"!",!" "foo!", etc..
– Sparhawk
Jan 29 at 3:03
1
What is it expanding? The manpage makes it sound like!"is a special token that disables "the history mechanism", which I assume means it prevents the current line from appearing in the previous command list/history buffer? Wouldn't that be more like 'history compression (or perhaps, excision)'?
– aroth
Jan 29 at 10:12
"history expansion" is the official name of this!feature -- you call it "csh bangs" if you like. And!"does no more than told in that paragraph; in particular, it does not prevent the current line from being pushed in the history -- why should it?
– mosvy
Jan 29 at 12:29
add a comment |
That's the history expansion at work.
This is what the zshexpn(1) manpage says about it:
If the shell encounters the character sequence
!"in the input, the
history mechanism is temporarily disabled until the current list (see
zshmisc(1)) is fully parsed. The!"is removed from the input, and
any subsequent!characters have no special significance.
answered Jan 29 at 2:58
mosvymosvy
8,8621833
1
So as either escape"foo!"or use single quotes'foo!'. Or even"foo!"!",!" "foo!", etc..
– Sparhawk
Jan 29 at 3:03
1
What is it expanding? The manpage makes it sound like!"is a special token that disables "the history mechanism", which I assume means it prevents the current line from appearing in the previous command list/history buffer? Wouldn't that be more like 'history compression (or perhaps, excision)'?
– aroth
Jan 29 at 10:12
"history expansion" is the official name of this!feature -- you call it "csh bangs" if you like. And!"does no more than told in that paragraph; in particular, it does not prevent the current line from being pushed in the history -- why should it?
– mosvy
Jan 29 at 12:29
add a comment |
That's the history expansion at work.
This is what the zshexpn(1) manpage says about it:
If the shell encounters the character sequence
!"in the input, the
history mechanism is temporarily disabled until the current list (see
zshmisc(1)) is fully parsed. The!"is removed from the input, and
any subsequent!characters have no special significance.
answered Jan 29 at 2:58
mosvymosvy
8,8621833
That's the history expansion at work.
This is what the zshexpn(1) manpage says about it:
If the shell encounters the character sequence
!"in the input, the
history mechanism is temporarily disabled until the current list (see
zshmisc(1)) is fully parsed. The!"is removed from the input, and
any subsequent!characters have no special significance.
answered Jan 29 at 2:58
mosvymosvy
8,8621833
answered Jan 29 at 2:58
mosvymosvy
8,8621833
answered Jan 29 at 2:58
mosvymosvy
8,8621833
answered Jan 29 at 2:58
mosvymosvy
8,8621833
8,8621833
1
So as either escape"foo!"or use single quotes'foo!'. Or even"foo!"!",!" "foo!", etc..
– Sparhawk
Jan 29 at 3:03
1
What is it expanding? The manpage makes it sound like!"is a special token that disables "the history mechanism", which I assume means it prevents the current line from appearing in the previous command list/history buffer? Wouldn't that be more like 'history compression (or perhaps, excision)'?
– aroth
Jan 29 at 10:12
"history expansion" is the official name of this!feature -- you call it "csh bangs" if you like. And!"does no more than told in that paragraph; in particular, it does not prevent the current line from being pushed in the history -- why should it?
– mosvy
Jan 29 at 12:29
add a comment |
1
So as either escape"foo!"or use single quotes'foo!'. Or even"foo!"!",!" "foo!", etc..
– Sparhawk
Jan 29 at 3:03
1
What is it expanding? The manpage makes it sound like!"is a special token that disables "the history mechanism", which I assume means it prevents the current line from appearing in the previous command list/history buffer? Wouldn't that be more like 'history compression (or perhaps, excision)'?
– aroth
Jan 29 at 10:12
"history expansion" is the official name of this!feature -- you call it "csh bangs" if you like. And!"does no more than told in that paragraph; in particular, it does not prevent the current line from being pushed in the history -- why should it?
– mosvy
Jan 29 at 12:29
1
1
So as either escape
"foo!" or use single quotes 'foo!'. Or even "foo!"!", !" "foo!", etc..– Sparhawk
Jan 29 at 3:03
So as either escape
"foo!" or use single quotes 'foo!'. Or even "foo!"!", !" "foo!", etc..– Sparhawk
Jan 29 at 3:03
1
1
What is it expanding? The manpage makes it sound like
!" is a special token that disables "the history mechanism", which I assume means it prevents the current line from appearing in the previous command list/history buffer? Wouldn't that be more like 'history compression (or perhaps, excision)'?– aroth
Jan 29 at 10:12
What is it expanding? The manpage makes it sound like
!" is a special token that disables "the history mechanism", which I assume means it prevents the current line from appearing in the previous command list/history buffer? Wouldn't that be more like 'history compression (or perhaps, excision)'?– aroth
Jan 29 at 10:12
"history expansion" is the official name of this
! feature -- you call it "csh bangs" if you like. And !" does no more than told in that paragraph; in particular, it does not prevent the current line from being pushed in the history -- why should it?– mosvy
Jan 29 at 12:29
"history expansion" is the official name of this
! feature -- you call it "csh bangs" if you like. And !" does no more than told in that paragraph; in particular, it does not prevent the current line from being pushed in the history -- why should it?– mosvy
Jan 29 at 12:29
add a comment |
Thanks for contributing an answer to Unix & Linux 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.
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%2funix.stackexchange.com%2fquestions%2f497328%2fzsh-thinks-unterminated-quote-if-preceded-by-exclamation-mark%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
