Bigger operator (>) shows up when I enter arguments in terminal [duplicate]












2
















This question already has an answer here:




  • What mode does the terminal go into when I type a single quote?

    2 answers



  • Unable to enter new commands in terminal — stuck with “>”

    1 answer




I found that it happens because it splits entered arguments. But I am creating a program that encrypts string and it encrypted "test" as |m{|. But when I switch to decryption mode that thing happens. Any solution ?










share|improve this question















marked as duplicate by glenn jackman, Thomas, Eric Carvalho, Sergiy Kolodyazhnyy command-line
Users with the  command-line badge can single-handedly close command-line questions as duplicates and reopen them as needed.

StackExchange.ready(function() {
if (StackExchange.options.isMobile) return;

$('.dupe-hammer-message-hover:not(.hover-bound)').each(function() {
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');

$hover.hover(
function() {
$hover.showInfoMessage('', {
messageElement: $msg.clone().show(),
transient: false,
position: { my: 'bottom left', at: 'top center', offsetTop: -7 },
dismissable: false,
relativeToBody: true
});
},
function() {
StackExchange.helpers.removeMessages();
}
);
});
});
Jan 16 at 21:08


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.























    2
















    This question already has an answer here:




    • What mode does the terminal go into when I type a single quote?

      2 answers



    • Unable to enter new commands in terminal — stuck with “>”

      1 answer




    I found that it happens because it splits entered arguments. But I am creating a program that encrypts string and it encrypted "test" as |m{|. But when I switch to decryption mode that thing happens. Any solution ?










    share|improve this question















    marked as duplicate by glenn jackman, Thomas, Eric Carvalho, Sergiy Kolodyazhnyy command-line
    Users with the  command-line badge can single-handedly close command-line questions as duplicates and reopen them as needed.

    StackExchange.ready(function() {
    if (StackExchange.options.isMobile) return;

    $('.dupe-hammer-message-hover:not(.hover-bound)').each(function() {
    var $hover = $(this).addClass('hover-bound'),
    $msg = $hover.siblings('.dupe-hammer-message');

    $hover.hover(
    function() {
    $hover.showInfoMessage('', {
    messageElement: $msg.clone().show(),
    transient: false,
    position: { my: 'bottom left', at: 'top center', offsetTop: -7 },
    dismissable: false,
    relativeToBody: true
    });
    },
    function() {
    StackExchange.helpers.removeMessages();
    }
    );
    });
    });
    Jan 16 at 21:08


    This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.





















      2












      2








      2









      This question already has an answer here:




      • What mode does the terminal go into when I type a single quote?

        2 answers



      • Unable to enter new commands in terminal — stuck with “>”

        1 answer




      I found that it happens because it splits entered arguments. But I am creating a program that encrypts string and it encrypted "test" as |m{|. But when I switch to decryption mode that thing happens. Any solution ?










      share|improve this question

















      This question already has an answer here:




      • What mode does the terminal go into when I type a single quote?

        2 answers



      • Unable to enter new commands in terminal — stuck with “>”

        1 answer




      I found that it happens because it splits entered arguments. But I am creating a program that encrypts string and it encrypted "test" as |m{|. But when I switch to decryption mode that thing happens. Any solution ?





      This question already has an answer here:




      • What mode does the terminal go into when I type a single quote?

        2 answers



      • Unable to enter new commands in terminal — stuck with “>”

        1 answer








      command-line






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 16 at 21:29









      wjandrea

      9,06542262




      9,06542262










      asked Jan 16 at 16:02









      Stel TeamStel Team

      214




      214




      marked as duplicate by glenn jackman, Thomas, Eric Carvalho, Sergiy Kolodyazhnyy command-line
      Users with the  command-line badge can single-handedly close command-line questions as duplicates and reopen them as needed.

      StackExchange.ready(function() {
      if (StackExchange.options.isMobile) return;

      $('.dupe-hammer-message-hover:not(.hover-bound)').each(function() {
      var $hover = $(this).addClass('hover-bound'),
      $msg = $hover.siblings('.dupe-hammer-message');

      $hover.hover(
      function() {
      $hover.showInfoMessage('', {
      messageElement: $msg.clone().show(),
      transient: false,
      position: { my: 'bottom left', at: 'top center', offsetTop: -7 },
      dismissable: false,
      relativeToBody: true
      });
      },
      function() {
      StackExchange.helpers.removeMessages();
      }
      );
      });
      });
      Jan 16 at 21:08


      This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.









      marked as duplicate by glenn jackman, Thomas, Eric Carvalho, Sergiy Kolodyazhnyy command-line
      Users with the  command-line badge can single-handedly close command-line questions as duplicates and reopen them as needed.

      StackExchange.ready(function() {
      if (StackExchange.options.isMobile) return;

      $('.dupe-hammer-message-hover:not(.hover-bound)').each(function() {
      var $hover = $(this).addClass('hover-bound'),
      $msg = $hover.siblings('.dupe-hammer-message');

      $hover.hover(
      function() {
      $hover.showInfoMessage('', {
      messageElement: $msg.clone().show(),
      transient: false,
      position: { my: 'bottom left', at: 'top center', offsetTop: -7 },
      dismissable: false,
      relativeToBody: true
      });
      },
      function() {
      StackExchange.helpers.removeMessages();
      }
      );
      });
      });
      Jan 16 at 21:08


      This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
























          1 Answer
          1






          active

          oldest

          votes


















          5














          The > comes from bash's $PS2 variable. man bash says:



          PS2    The value of this parameter is expanded as with PS1 and used as the secondary prompt string.  The default is ``> ''.


          I often see > when I have an unmatched quote (") or apostrophe ('), or some other input that bash views as incomplete.






          share|improve this answer
























          • Is there any way to input "|m{|" (without quotes) into terminal ?

            – Stel Team
            Jan 16 at 16:10






          • 1





            @StelTeam I believe terminal is waiting for you to enter }. What's wrong if it is enter within double quotes? I think it is just a filename. Isn't it?

            – Kulfy
            Jan 16 at 16:44













          • @Kulfy The string |m{| is the encrypted version of "test". so the program must take |m{| as an argument in order to decrypt it as "test"

            – Stel Team
            Jan 16 at 16:46






          • 3





            ... if you enter "|m{|" '|m{|' in the shell as an argument to your program, your program will not see the quotes (they will simply prevent the shell from trying to interpret the sequence)

            – steeldriver
            Jan 16 at 16:51











          • @StelTeam Without quotes | will be treated as pipe symbol and { as start of compound command, therefore the shell will treat it as part of its syntax and consider the line you entered incomplete. That's what > signifies.

            – Sergiy Kolodyazhnyy
            Jan 16 at 21:07


















          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          5














          The > comes from bash's $PS2 variable. man bash says:



          PS2    The value of this parameter is expanded as with PS1 and used as the secondary prompt string.  The default is ``> ''.


          I often see > when I have an unmatched quote (") or apostrophe ('), or some other input that bash views as incomplete.






          share|improve this answer
























          • Is there any way to input "|m{|" (without quotes) into terminal ?

            – Stel Team
            Jan 16 at 16:10






          • 1





            @StelTeam I believe terminal is waiting for you to enter }. What's wrong if it is enter within double quotes? I think it is just a filename. Isn't it?

            – Kulfy
            Jan 16 at 16:44













          • @Kulfy The string |m{| is the encrypted version of "test". so the program must take |m{| as an argument in order to decrypt it as "test"

            – Stel Team
            Jan 16 at 16:46






          • 3





            ... if you enter "|m{|" '|m{|' in the shell as an argument to your program, your program will not see the quotes (they will simply prevent the shell from trying to interpret the sequence)

            – steeldriver
            Jan 16 at 16:51











          • @StelTeam Without quotes | will be treated as pipe symbol and { as start of compound command, therefore the shell will treat it as part of its syntax and consider the line you entered incomplete. That's what > signifies.

            – Sergiy Kolodyazhnyy
            Jan 16 at 21:07
















          5














          The > comes from bash's $PS2 variable. man bash says:



          PS2    The value of this parameter is expanded as with PS1 and used as the secondary prompt string.  The default is ``> ''.


          I often see > when I have an unmatched quote (") or apostrophe ('), or some other input that bash views as incomplete.






          share|improve this answer
























          • Is there any way to input "|m{|" (without quotes) into terminal ?

            – Stel Team
            Jan 16 at 16:10






          • 1





            @StelTeam I believe terminal is waiting for you to enter }. What's wrong if it is enter within double quotes? I think it is just a filename. Isn't it?

            – Kulfy
            Jan 16 at 16:44













          • @Kulfy The string |m{| is the encrypted version of "test". so the program must take |m{| as an argument in order to decrypt it as "test"

            – Stel Team
            Jan 16 at 16:46






          • 3





            ... if you enter "|m{|" '|m{|' in the shell as an argument to your program, your program will not see the quotes (they will simply prevent the shell from trying to interpret the sequence)

            – steeldriver
            Jan 16 at 16:51











          • @StelTeam Without quotes | will be treated as pipe symbol and { as start of compound command, therefore the shell will treat it as part of its syntax and consider the line you entered incomplete. That's what > signifies.

            – Sergiy Kolodyazhnyy
            Jan 16 at 21:07














          5












          5








          5







          The > comes from bash's $PS2 variable. man bash says:



          PS2    The value of this parameter is expanded as with PS1 and used as the secondary prompt string.  The default is ``> ''.


          I often see > when I have an unmatched quote (") or apostrophe ('), or some other input that bash views as incomplete.






          share|improve this answer













          The > comes from bash's $PS2 variable. man bash says:



          PS2    The value of this parameter is expanded as with PS1 and used as the secondary prompt string.  The default is ``> ''.


          I often see > when I have an unmatched quote (") or apostrophe ('), or some other input that bash views as incomplete.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 16 at 16:08









          waltinatorwaltinator

          22.4k74169




          22.4k74169













          • Is there any way to input "|m{|" (without quotes) into terminal ?

            – Stel Team
            Jan 16 at 16:10






          • 1





            @StelTeam I believe terminal is waiting for you to enter }. What's wrong if it is enter within double quotes? I think it is just a filename. Isn't it?

            – Kulfy
            Jan 16 at 16:44













          • @Kulfy The string |m{| is the encrypted version of "test". so the program must take |m{| as an argument in order to decrypt it as "test"

            – Stel Team
            Jan 16 at 16:46






          • 3





            ... if you enter "|m{|" '|m{|' in the shell as an argument to your program, your program will not see the quotes (they will simply prevent the shell from trying to interpret the sequence)

            – steeldriver
            Jan 16 at 16:51











          • @StelTeam Without quotes | will be treated as pipe symbol and { as start of compound command, therefore the shell will treat it as part of its syntax and consider the line you entered incomplete. That's what > signifies.

            – Sergiy Kolodyazhnyy
            Jan 16 at 21:07



















          • Is there any way to input "|m{|" (without quotes) into terminal ?

            – Stel Team
            Jan 16 at 16:10






          • 1





            @StelTeam I believe terminal is waiting for you to enter }. What's wrong if it is enter within double quotes? I think it is just a filename. Isn't it?

            – Kulfy
            Jan 16 at 16:44













          • @Kulfy The string |m{| is the encrypted version of "test". so the program must take |m{| as an argument in order to decrypt it as "test"

            – Stel Team
            Jan 16 at 16:46






          • 3





            ... if you enter "|m{|" '|m{|' in the shell as an argument to your program, your program will not see the quotes (they will simply prevent the shell from trying to interpret the sequence)

            – steeldriver
            Jan 16 at 16:51











          • @StelTeam Without quotes | will be treated as pipe symbol and { as start of compound command, therefore the shell will treat it as part of its syntax and consider the line you entered incomplete. That's what > signifies.

            – Sergiy Kolodyazhnyy
            Jan 16 at 21:07

















          Is there any way to input "|m{|" (without quotes) into terminal ?

          – Stel Team
          Jan 16 at 16:10





          Is there any way to input "|m{|" (without quotes) into terminal ?

          – Stel Team
          Jan 16 at 16:10




          1




          1





          @StelTeam I believe terminal is waiting for you to enter }. What's wrong if it is enter within double quotes? I think it is just a filename. Isn't it?

          – Kulfy
          Jan 16 at 16:44







          @StelTeam I believe terminal is waiting for you to enter }. What's wrong if it is enter within double quotes? I think it is just a filename. Isn't it?

          – Kulfy
          Jan 16 at 16:44















          @Kulfy The string |m{| is the encrypted version of "test". so the program must take |m{| as an argument in order to decrypt it as "test"

          – Stel Team
          Jan 16 at 16:46





          @Kulfy The string |m{| is the encrypted version of "test". so the program must take |m{| as an argument in order to decrypt it as "test"

          – Stel Team
          Jan 16 at 16:46




          3




          3





          ... if you enter "|m{|" '|m{|' in the shell as an argument to your program, your program will not see the quotes (they will simply prevent the shell from trying to interpret the sequence)

          – steeldriver
          Jan 16 at 16:51





          ... if you enter "|m{|" '|m{|' in the shell as an argument to your program, your program will not see the quotes (they will simply prevent the shell from trying to interpret the sequence)

          – steeldriver
          Jan 16 at 16:51













          @StelTeam Without quotes | will be treated as pipe symbol and { as start of compound command, therefore the shell will treat it as part of its syntax and consider the line you entered incomplete. That's what > signifies.

          – Sergiy Kolodyazhnyy
          Jan 16 at 21:07





          @StelTeam Without quotes | will be treated as pipe symbol and { as start of compound command, therefore the shell will treat it as part of its syntax and consider the line you entered incomplete. That's what > signifies.

          – Sergiy Kolodyazhnyy
          Jan 16 at 21:07



          Popular posts from this blog

          Human spaceflight

          Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

          張江高科駅