Disable the “>” operator in Rstudio linux terminalssh-agent and screenBash shell: how to reconcile...

Contest math problem about crossing out numbers in the table

cron not executing python3

What creature do these Alchemical Humonculus actions target?

Why is "points exist" not an axiom in geometry?

Disable the ">" operator in Rstudio linux terminal

Why zero tolerance on nudity in space?

Jumping Numbers

What is the purpose of easy combat scenarios that don't need resource expenditure?

We are very unlucky in my court

Quenching swords in dragon blood; why?

Can a hotel cancel a confirmed reservation?

Is a debit card dangerous in my situation?

Book where aliens are selecting humans for food consumption

Caruana vs Carlsen game 10 (WCC) why not 18...Nxb6?

Why does lambda auto& parameter choose const overload?

A starship is travelling at 0.9c and collides with a small rock. Will it leave a clean hole through, or will more happen?

Do authors have to be politically correct in article-writing?

Why is working on the same position for more than 15 years not a red flag?

Why Normality assumption in linear regression

Why did other German political parties disband so fast when Hitler was appointed chancellor?

Can an insurance company drop you after receiving a bill and refusing to pay?

Program that converts a number to a letter of the alphabet

What is the most triangles you can make from a capital "H" and 3 straight lines?

Why exactly do action photographers need high fps burst cameras?



Disable the “>” operator in Rstudio linux terminal


ssh-agent and screenBash shell: how to reconcile portable configuration files and GUI terminal start-up types (login or interactive)?Disable mouse reporting in a terminal session after tmux exits unexpectedlycd <nonexistent_directory> in bash causes cd to different directory?Any chance to change word selection separator characters in RStudio?Windows launch second RStudio?command nohup tail with redirection in shell script not invoked properly under a particular situationSingle SSH History for multiple sessions?Hiding pane above script editor in RstudioRStudio: What are the available options in RStudio to format code chunks in an R Markdown document?













1















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 disable ">" in these sessions, but I am not sure how to do this.










share|improve this question









New contributor




user36302 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 4





    > is not a command, it's a redirection operator.

    – Arkadiusz Drabczyk
    4 hours ago






  • 2





    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
    4 hours ago











  • ok that explains why it can't be aliased, but do you have a suggestion how to address my question?

    – user36302
    4 hours ago






  • 1





    Bash appears to offer a restricted mode: stackoverflow.com/questions/50989369/…

    – music2myear
    4 hours ago


















1















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 disable ">" in these sessions, but I am not sure how to do this.










share|improve this question









New contributor




user36302 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 4





    > is not a command, it's a redirection operator.

    – Arkadiusz Drabczyk
    4 hours ago






  • 2





    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
    4 hours ago











  • ok that explains why it can't be aliased, but do you have a suggestion how to address my question?

    – user36302
    4 hours ago






  • 1





    Bash appears to offer a restricted mode: stackoverflow.com/questions/50989369/…

    – music2myear
    4 hours ago
















1












1








1








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 disable ">" in these sessions, but I am not sure how to do this.










share|improve this question









New contributor




user36302 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












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 disable ">" in these sessions, but I am not sure how to do this.







linux bash ssh terminal rstudio






share|improve this question









New contributor




user36302 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




user36302 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 2 hours ago







user36302













New contributor




user36302 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 4 hours ago









user36302user36302

62




62




New contributor




user36302 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





user36302 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






user36302 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 4





    > is not a command, it's a redirection operator.

    – Arkadiusz Drabczyk
    4 hours ago






  • 2





    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
    4 hours ago











  • ok that explains why it can't be aliased, but do you have a suggestion how to address my question?

    – user36302
    4 hours ago






  • 1





    Bash appears to offer a restricted mode: stackoverflow.com/questions/50989369/…

    – music2myear
    4 hours ago
















  • 4





    > is not a command, it's a redirection operator.

    – Arkadiusz Drabczyk
    4 hours ago






  • 2





    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
    4 hours ago











  • ok that explains why it can't be aliased, but do you have a suggestion how to address my question?

    – user36302
    4 hours ago






  • 1





    Bash appears to offer a restricted mode: stackoverflow.com/questions/50989369/…

    – music2myear
    4 hours ago










4




4





> is not a command, it's a redirection operator.

– Arkadiusz Drabczyk
4 hours ago





> is not a command, it's a redirection operator.

– Arkadiusz Drabczyk
4 hours ago




2




2





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
4 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
4 hours ago













ok that explains why it can't be aliased, but do you have a suggestion how to address my question?

– user36302
4 hours ago





ok that explains why it can't be aliased, but do you have a suggestion how to address my question?

– user36302
4 hours ago




1




1





Bash appears to offer a restricted mode: stackoverflow.com/questions/50989369/…

– music2myear
4 hours ago







Bash appears to offer a restricted mode: stackoverflow.com/questions/50989369/…

– music2myear
4 hours ago












1 Answer
1






active

oldest

votes


















9














> 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 The Set Builtin). The ‘>|’ redirection operator may be used to override noclobber.



https://www.gnu.org/software/bash/manual/bashref.html#The-Set-Builtin







share|improve this answer























    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.










    draft saved

    draft discarded


















    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









    9














    > 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 The Set Builtin). The ‘>|’ redirection operator may be used to override noclobber.



    https://www.gnu.org/software/bash/manual/bashref.html#The-Set-Builtin







    share|improve this answer




























      9














      > 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 The Set Builtin). The ‘>|’ redirection operator may be used to override noclobber.



      https://www.gnu.org/software/bash/manual/bashref.html#The-Set-Builtin







      share|improve this answer


























        9












        9








        9







        > 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 The Set Builtin). The ‘>|’ redirection operator may be used to override noclobber.



        https://www.gnu.org/software/bash/manual/bashref.html#The-Set-Builtin







        share|improve this answer













        > 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 The Set Builtin). The ‘>|’ redirection operator may be used to override noclobber.



        https://www.gnu.org/software/bash/manual/bashref.html#The-Set-Builtin








        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 3 hours ago









        phuclvphuclv

        9,53363990




        9,53363990






















            user36302 is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            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.




            draft saved


            draft discarded














            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





















































            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







            Popular posts from this blog

            Benedict Cumberbatch Contingut Inicis Debut professional Premis Filmografia bàsica Premis i...

            Monticle de plataforma Contingut Est de Nord Amèrica Interpretacions Altres cultures Vegeu...

            Escacs Janus Enllaços externs Menú de navegacióEscacs JanusJanusschachBrainKing.comChessV