Mixing
' in command prompt
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
Occasionally when I type : to quit or write my file the prompt already contains the characters :'<,'> without me typing anything. It causes an error if I type w or q. I cannot replicate this problem. It happens at the oddest times and I have not been able to determine what is causing it.
It took me forever to figure out that my accidentally typing q: instead of :q was causing me to have trouble quitting. Now that I know about that little quirk, I'm trying to figure out what causes this other behavior. I can't find anything on it, though I've seen it somewhere in someone's colon command.
Is this an expected behavior? What could be causing it?
command-line
asked 29 mins ago
malan
1294
add a comment |Â
up vote
1
down vote
favorite
Occasionally when I type : to quit or write my file the prompt already contains the characters :'<,'> without me typing anything. It causes an error if I type w or q. I cannot replicate this problem. It happens at the oddest times and I have not been able to determine what is causing it.
It took me forever to figure out that my accidentally typing q: instead of :q was causing me to have trouble quitting. Now that I know about that little quirk, I'm trying to figure out what causes this other behavior. I can't find anything on it, though I've seen it somewhere in someone's colon command.
Is this an expected behavior? What could be causing it?
command-line
asked 29 mins ago
malan
1294
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Occasionally when I type : to quit or write my file the prompt already contains the characters :'<,'> without me typing anything. It causes an error if I type w or q. I cannot replicate this problem. It happens at the oddest times and I have not been able to determine what is causing it.
It took me forever to figure out that my accidentally typing q: instead of :q was causing me to have trouble quitting. Now that I know about that little quirk, I'm trying to figure out what causes this other behavior. I can't find anything on it, though I've seen it somewhere in someone's colon command.
Is this an expected behavior? What could be causing it?
command-line
asked 29 mins ago
malan
1294
Occasionally when I type : to quit or write my file the prompt already contains the characters :'<,'> without me typing anything. It causes an error if I type w or q. I cannot replicate this problem. It happens at the oddest times and I have not been able to determine what is causing it.
It took me forever to figure out that my accidentally typing q: instead of :q was causing me to have trouble quitting. Now that I know about that little quirk, I'm trying to figure out what causes this other behavior. I can't find anything on it, though I've seen it somewhere in someone's colon command.
Is this an expected behavior? What could be causing it?
command-line
command-line
asked 29 mins ago
malan
1294
asked 29 mins ago
malan
1294
edited 18 mins ago
asked 29 mins ago
malan
1294
asked 29 mins ago
malan
1294
asked 29 mins ago
malan
1294
1294
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
3
down vote
accepted
Seeing '<,'> in the command line when you press : indicates that you currently have a range selected (e. g. with v, V, or Ctrl-v), and vim is helpfully prefixing the markers for 'beginning of selection' through 'end of selection' in order to apply those limitations to the scope of the command you are presumably about to enter.
Since you can't "quit" only a certain part of a file, that is why you get an Invalid address when you try to :'<,'>q.
If you do want to run a command not suchly limited, you can press Ctrl-U to erase everything to the left of the cursor before entering q, or simply use the ZZ alias.
answered 23 mins ago
DopeGhoti
1462
New contributor
DopeGhoti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
Seeing '<,'> in the command line when you press : indicates that you currently have a range selected (e. g. with v, V, or Ctrl-v), and vim is helpfully prefixing the markers for 'beginning of selection' through 'end of selection' in order to apply those limitations to the scope of the command you are presumably about to enter.
Since you can't "quit" only a certain part of a file, that is why you get an Invalid address when you try to :'<,'>q.
If you do want to run a command not suchly limited, you can press Ctrl-U to erase everything to the left of the cursor before entering q, or simply use the ZZ alias.
answered 23 mins ago
DopeGhoti
1462
New contributor
DopeGhoti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
3
down vote
accepted
Seeing '<,'> in the command line when you press : indicates that you currently have a range selected (e. g. with v, V, or Ctrl-v), and vim is helpfully prefixing the markers for 'beginning of selection' through 'end of selection' in order to apply those limitations to the scope of the command you are presumably about to enter.
Since you can't "quit" only a certain part of a file, that is why you get an Invalid address when you try to :'<,'>q.
If you do want to run a command not suchly limited, you can press Ctrl-U to erase everything to the left of the cursor before entering q, or simply use the ZZ alias.
answered 23 mins ago
DopeGhoti
1462
New contributor
DopeGhoti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
3
down vote
accepted
up vote
3
down vote
accepted
Seeing '<,'> in the command line when you press : indicates that you currently have a range selected (e. g. with v, V, or Ctrl-v), and vim is helpfully prefixing the markers for 'beginning of selection' through 'end of selection' in order to apply those limitations to the scope of the command you are presumably about to enter.
Since you can't "quit" only a certain part of a file, that is why you get an Invalid address when you try to :'<,'>q.
If you do want to run a command not suchly limited, you can press Ctrl-U to erase everything to the left of the cursor before entering q, or simply use the ZZ alias.
answered 23 mins ago
DopeGhoti
1462
New contributor
DopeGhoti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Seeing '<,'> in the command line when you press : indicates that you currently have a range selected (e. g. with v, V, or Ctrl-v), and vim is helpfully prefixing the markers for 'beginning of selection' through 'end of selection' in order to apply those limitations to the scope of the command you are presumably about to enter.
Since you can't "quit" only a certain part of a file, that is why you get an Invalid address when you try to :'<,'>q.
If you do want to run a command not suchly limited, you can press Ctrl-U to erase everything to the left of the cursor before entering q, or simply use the ZZ alias.
answered 23 mins ago
DopeGhoti
1462
New contributor
DopeGhoti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 23 mins ago
DopeGhoti
1462
New contributor
DopeGhoti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 23 mins ago
DopeGhoti
1462
answered 23 mins ago
DopeGhoti
1462
1462
New contributor
DopeGhoti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
DopeGhoti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
DopeGhoti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
add a comment |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fvi.stackexchange.com%2fquestions%2f17563%2fin-command-prompt%23new-answer', 'question_page');
);
Post as a guest
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
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
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
