Disable the “>” operator in Rstudio linux terminal
For an interactive session via SSH on a Linux cluster in Rstudio, it is very easy to accidentally execute the keyboard shortcut for "run in terminal" when commands are highlighted in Rstudio console. This results in behavior such as
> library
or
Var1>Var2
being executed in terminal, which creates a library
or Var2
file in the remote working directory if the terminal is logged in at the bash prompt.
In a worst case scenario this would result in overwriting files in the remote working directory.
I would like to disable ">" in these sessions, but I am not sure how to do this.
linux bash ssh terminal rstudio
New contributor
add a comment |
For an interactive session via SSH on a Linux cluster in Rstudio, it is very easy to accidentally execute the keyboard shortcut for "run in terminal" when commands are highlighted in Rstudio console. This results in behavior such as
> library
or
Var1>Var2
being executed in terminal, which creates a library
or Var2
file in the remote working directory if the terminal is logged in at the bash prompt.
In a worst case scenario this would result in overwriting files in the remote working directory.
I would like to disable ">" in these sessions, but I am not sure how to do this.
linux bash ssh terminal rstudio
New contributor
5
>
is not a command, it's a redirection operator.
– Arkadiusz Drabczyk
12 hours ago
3
Redirection characters are fundamental to Linux shells and can't be changed. You should look at whether you can change the Rstudio prompt to something less drastic if accidentally copied. If you can't, you'll just need to take more care.
– AFH
12 hours ago
ok that explains why it can't be aliased, but do you have a suggestion how to address my question?
– user36302
12 hours ago
2
Bash appears to offer a restricted mode: stackoverflow.com/questions/50989369/…
– music2myear
12 hours ago
add a comment |
For an interactive session via SSH on a Linux cluster in Rstudio, it is very easy to accidentally execute the keyboard shortcut for "run in terminal" when commands are highlighted in Rstudio console. This results in behavior such as
> library
or
Var1>Var2
being executed in terminal, which creates a library
or Var2
file in the remote working directory if the terminal is logged in at the bash prompt.
In a worst case scenario this would result in overwriting files in the remote working directory.
I would like to disable ">" in these sessions, but I am not sure how to do this.
linux bash ssh terminal rstudio
New contributor
For an interactive session via SSH on a Linux cluster in Rstudio, it is very easy to accidentally execute the keyboard shortcut for "run in terminal" when commands are highlighted in Rstudio console. This results in behavior such as
> library
or
Var1>Var2
being executed in terminal, which creates a library
or Var2
file in the remote working directory if the terminal is logged in at the bash prompt.
In a worst case scenario this would result in overwriting files in the remote working directory.
I would like to disable ">" in these sessions, but I am not sure how to do this.
linux bash ssh terminal rstudio
linux bash ssh terminal rstudio
New contributor
New contributor
edited 4 hours ago
phuclv
9,60363991
9,60363991
New contributor
asked 12 hours ago
user36302user36302
212
212
New contributor
New contributor
5
>
is not a command, it's a redirection operator.
– Arkadiusz Drabczyk
12 hours ago
3
Redirection characters are fundamental to Linux shells and can't be changed. You should look at whether you can change the Rstudio prompt to something less drastic if accidentally copied. If you can't, you'll just need to take more care.
– AFH
12 hours ago
ok that explains why it can't be aliased, but do you have a suggestion how to address my question?
– user36302
12 hours ago
2
Bash appears to offer a restricted mode: stackoverflow.com/questions/50989369/…
– music2myear
12 hours ago
add a comment |
5
>
is not a command, it's a redirection operator.
– Arkadiusz Drabczyk
12 hours ago
3
Redirection characters are fundamental to Linux shells and can't be changed. You should look at whether you can change the Rstudio prompt to something less drastic if accidentally copied. If you can't, you'll just need to take more care.
– AFH
12 hours ago
ok that explains why it can't be aliased, but do you have a suggestion how to address my question?
– user36302
12 hours ago
2
Bash appears to offer a restricted mode: stackoverflow.com/questions/50989369/…
– music2myear
12 hours ago
5
5
>
is not a command, it's a redirection operator.– Arkadiusz Drabczyk
12 hours ago
>
is not a command, it's a redirection operator.– Arkadiusz Drabczyk
12 hours ago
3
3
Redirection characters are fundamental to Linux shells and can't be changed. You should look at whether you can change the Rstudio prompt to something less drastic if accidentally copied. If you can't, you'll just need to take more care.
– AFH
12 hours ago
Redirection characters are fundamental to Linux shells and can't be changed. You should look at whether you can change the Rstudio prompt to something less drastic if accidentally copied. If you can't, you'll just need to take more care.
– AFH
12 hours ago
ok that explains why it can't be aliased, but do you have a suggestion how to address my question?
– user36302
12 hours ago
ok that explains why it can't be aliased, but do you have a suggestion how to address my question?
– user36302
12 hours ago
2
2
Bash appears to offer a restricted mode: stackoverflow.com/questions/50989369/…
– music2myear
12 hours ago
Bash appears to offer a restricted mode: stackoverflow.com/questions/50989369/…
– music2myear
12 hours ago
add a comment |
1 Answer
1
active
oldest
votes
>
is not a command but an operator, so you can't alias it. But you can disable overwriting files with the noclobber
option. Just run set -C
or set -o noclobber
(or add them to your ~/.bashrc)
The
noclobber
option is available to avoid overwriting existing files with output redirection (see TheSet
Builtin). The ‘>|’ redirection operator may be used to override noclobber.
https://www.gnu.org/software/bash/manual/bashref.html#The-Set-Builtin
This still wont prevent the creation of new files
– D. Ben Knoble
5 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});
}
});
user36302 is a new contributor. Be nice, and check out our Code of Conduct.
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%2fsuperuser.com%2fquestions%2f1410511%2fdisable-the-operator-in-rstudio-linux-terminal%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
>
is not a command but an operator, so you can't alias it. But you can disable overwriting files with the noclobber
option. Just run set -C
or set -o noclobber
(or add them to your ~/.bashrc)
The
noclobber
option is available to avoid overwriting existing files with output redirection (see TheSet
Builtin). The ‘>|’ redirection operator may be used to override noclobber.
https://www.gnu.org/software/bash/manual/bashref.html#The-Set-Builtin
This still wont prevent the creation of new files
– D. Ben Knoble
5 hours ago
add a comment |
>
is not a command but an operator, so you can't alias it. But you can disable overwriting files with the noclobber
option. Just run set -C
or set -o noclobber
(or add them to your ~/.bashrc)
The
noclobber
option is available to avoid overwriting existing files with output redirection (see TheSet
Builtin). The ‘>|’ redirection operator may be used to override noclobber.
https://www.gnu.org/software/bash/manual/bashref.html#The-Set-Builtin
This still wont prevent the creation of new files
– D. Ben Knoble
5 hours ago
add a comment |
>
is not a command but an operator, so you can't alias it. But you can disable overwriting files with the noclobber
option. Just run set -C
or set -o noclobber
(or add them to your ~/.bashrc)
The
noclobber
option is available to avoid overwriting existing files with output redirection (see TheSet
Builtin). The ‘>|’ redirection operator may be used to override noclobber.
https://www.gnu.org/software/bash/manual/bashref.html#The-Set-Builtin
>
is not a command but an operator, so you can't alias it. But you can disable overwriting files with the noclobber
option. Just run set -C
or set -o noclobber
(or add them to your ~/.bashrc)
The
noclobber
option is available to avoid overwriting existing files with output redirection (see TheSet
Builtin). The ‘>|’ redirection operator may be used to override noclobber.
https://www.gnu.org/software/bash/manual/bashref.html#The-Set-Builtin
answered 12 hours ago
phuclvphuclv
9,60363991
9,60363991
This still wont prevent the creation of new files
– D. Ben Knoble
5 hours ago
add a comment |
This still wont prevent the creation of new files
– D. Ben Knoble
5 hours ago
This still wont prevent the creation of new files
– D. Ben Knoble
5 hours ago
This still wont prevent the creation of new files
– D. Ben Knoble
5 hours ago
add a comment |
user36302 is a new contributor. Be nice, and check out our Code of Conduct.
user36302 is a new contributor. Be nice, and check out our Code of Conduct.
user36302 is a new contributor. Be nice, and check out our Code of Conduct.
user36302 is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1410511%2fdisable-the-operator-in-rstudio-linux-terminal%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
5
>
is not a command, it's a redirection operator.– Arkadiusz Drabczyk
12 hours ago
3
Redirection characters are fundamental to Linux shells and can't be changed. You should look at whether you can change the Rstudio prompt to something less drastic if accidentally copied. If you can't, you'll just need to take more care.
– AFH
12 hours ago
ok that explains why it can't be aliased, but do you have a suggestion how to address my question?
– user36302
12 hours ago
2
Bash appears to offer a restricted mode: stackoverflow.com/questions/50989369/…
– music2myear
12 hours ago