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











up vote
9
down vote

favorite
1












When I enter single quote ' in terminal it goes to some other mode, and commands don't execute. What is this mode and when do we use it?



root@sai:~# '
> ls
> '
ls
: command not found
root@sai:~#









share|improve this question




















  • 27




    and why are you running as root?
    – Zanna
    Mar 8 '17 at 7:15






  • 12




    Your terminal is in the same mode as before - your shell is in a different mode (waiting for the completion of a string with another ')
    – ohno
    Mar 8 '17 at 13:30















up vote
9
down vote

favorite
1












When I enter single quote ' in terminal it goes to some other mode, and commands don't execute. What is this mode and when do we use it?



root@sai:~# '
> ls
> '
ls
: command not found
root@sai:~#









share|improve this question




















  • 27




    and why are you running as root?
    – Zanna
    Mar 8 '17 at 7:15






  • 12




    Your terminal is in the same mode as before - your shell is in a different mode (waiting for the completion of a string with another ')
    – ohno
    Mar 8 '17 at 13:30













up vote
9
down vote

favorite
1









up vote
9
down vote

favorite
1






1





When I enter single quote ' in terminal it goes to some other mode, and commands don't execute. What is this mode and when do we use it?



root@sai:~# '
> ls
> '
ls
: command not found
root@sai:~#









share|improve this question















When I enter single quote ' in terminal it goes to some other mode, and commands don't execute. What is this mode and when do we use it?



root@sai:~# '
> ls
> '
ls
: command not found
root@sai:~#






command-line bash






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 9 '17 at 1:40









muru

135k19289490




135k19289490










asked Mar 8 '17 at 7:03









manikanta

872213




872213








  • 27




    and why are you running as root?
    – Zanna
    Mar 8 '17 at 7:15






  • 12




    Your terminal is in the same mode as before - your shell is in a different mode (waiting for the completion of a string with another ')
    – ohno
    Mar 8 '17 at 13:30














  • 27




    and why are you running as root?
    – Zanna
    Mar 8 '17 at 7:15






  • 12




    Your terminal is in the same mode as before - your shell is in a different mode (waiting for the completion of a string with another ')
    – ohno
    Mar 8 '17 at 13:30








27




27




and why are you running as root?
– Zanna
Mar 8 '17 at 7:15




and why are you running as root?
– Zanna
Mar 8 '17 at 7:15




12




12




Your terminal is in the same mode as before - your shell is in a different mode (waiting for the completion of a string with another ')
– ohno
Mar 8 '17 at 13:30




Your terminal is in the same mode as before - your shell is in a different mode (waiting for the completion of a string with another ')
– ohno
Mar 8 '17 at 13:30










2 Answers
2






active

oldest

votes

















up vote
23
down vote



accepted










Effectively, the shell asks for a complete command/expression, and for that reason is displaying the PS2 prompt string.



From man bash:




PROMPTING



When executing interactively, bash displays the
primary prompt PS1 when it is ready to read a
command, and the secondary prompt PS2 when it
needs more input to complete a command.




And a little before that:




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



Thus, as you may guess from reading the documentation, shells have multiple prompts with different purposes. The PS1 prompt is your root@sai:~# string, which shows up normally when you enter commands. > is the PS2 prompt. There's others, too: PS3 for select command block and PS4 for debugging with set -x command. In this case we're more interested in PS2.



There are many ways in which shell may show the PS2 prompt (and where completing a command on a new line might be necessary). The same prompt is used when you perform here-doc redirection (where a command is considered complete when you see the terminating string, in this example, EOF):



$ cat <<EOF
> line one
> line two
> EOF
line one
line two


Very often continuation of a lengthy command can be done by adding and immediate(!) newline, which will cause the same prompt to appear:



$ echo Hello
> World
HelloWorld

$ echo 'Hello
> World'
Hello
World


When pipes, logic operators, or special keywords appear on command-line before newline, the command also is considered incomplete until all final statements are entered:



$ echo Hello World | 
> wc -l
1

$ echo Hello World &&
> echo "!"
Hello World
!

$ for i in $(seq 1 3); do
> echo "$i"
> done
1
2
3

$ if [ -f /etc/passwd ]
> then
> echo "YES"
> fi
YES


In your particular case, a single quote implies literal interpretation of what is between the single quotes. Thus, as Zanna pointed out, you are entering a command that consists of newline+ls+newline. Such an executable filename cannot be found (and typically command filenames should consist of only alphanumeric characters, plus underscores, dashes, and dots). Although it is indeed possible to have filenames that contain special characters in them, it is always avoided.



NOTE: such behavior as shown in your example is specific to Bourne-like shells, including bash, dash (on Ubuntu it is symlinked to /bin/sh), ksh, and mksh. csh and its derivatives do not behave in such way:



$ tcsh                                                    
eagle:~> '
Unmatched '.
eagle:~> csh
% '
Unmatched '.
%


However, in interactive mode, csh will still raise ? as prompt2 when more input is required:



$ csh
% foreach n ( 1 2 3 )
? echo $n
? end
1
2
3


See also:




  • In which situations are PS2, PS3, PS4 used as the prompt?

  • What's the difference between <<, <<< and < < in bash?

  • What does > mean in the terminal!

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

  • What is the effect of a lone backtick at the end of a command line?






share|improve this answer























  • The link What's the difference between <<, <<< and < < in bash? is offline/wrong.
    – Tico
    Mar 8 '17 at 16:49










  • @Tico Thanks fixed. The answer was written with internet speed of milli-turtles per second, which resulted only in partially copied link. Fixed now
    – Sergiy Kolodyazhnyy
    Mar 8 '17 at 16:51






  • 2




    Meanwhile, zsh is kind enough to actually tell you what it is waiting for, which is occasionally useful if you thought your command was valid but forgot to escape something.
    – Kevin
    Mar 9 '17 at 8:02


















up vote
28
down vote













The shell is just waiting for the closing quote. When you enter it, it will do exactly what it usually does, and attempt to execute the command entered.



Quotes cause the shell not to interpret special characters, meaning that expansions are not performed. Single quotes suppress all interpretation of special characters completely. Normally a newline separates commands, but here you have included the newlines as part of the command by quoting them.



Since there is no such command as <newline>ls<newline>, it is not found.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    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',
    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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f890782%2fwhat-mode-does-the-terminal-go-into-when-i-type-a-single-quote%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    23
    down vote



    accepted










    Effectively, the shell asks for a complete command/expression, and for that reason is displaying the PS2 prompt string.



    From man bash:




    PROMPTING



    When executing interactively, bash displays the
    primary prompt PS1 when it is ready to read a
    command, and the secondary prompt PS2 when it
    needs more input to complete a command.




    And a little before that:




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



    Thus, as you may guess from reading the documentation, shells have multiple prompts with different purposes. The PS1 prompt is your root@sai:~# string, which shows up normally when you enter commands. > is the PS2 prompt. There's others, too: PS3 for select command block and PS4 for debugging with set -x command. In this case we're more interested in PS2.



    There are many ways in which shell may show the PS2 prompt (and where completing a command on a new line might be necessary). The same prompt is used when you perform here-doc redirection (where a command is considered complete when you see the terminating string, in this example, EOF):



    $ cat <<EOF
    > line one
    > line two
    > EOF
    line one
    line two


    Very often continuation of a lengthy command can be done by adding and immediate(!) newline, which will cause the same prompt to appear:



    $ echo Hello
    > World
    HelloWorld

    $ echo 'Hello
    > World'
    Hello
    World


    When pipes, logic operators, or special keywords appear on command-line before newline, the command also is considered incomplete until all final statements are entered:



    $ echo Hello World | 
    > wc -l
    1

    $ echo Hello World &&
    > echo "!"
    Hello World
    !

    $ for i in $(seq 1 3); do
    > echo "$i"
    > done
    1
    2
    3

    $ if [ -f /etc/passwd ]
    > then
    > echo "YES"
    > fi
    YES


    In your particular case, a single quote implies literal interpretation of what is between the single quotes. Thus, as Zanna pointed out, you are entering a command that consists of newline+ls+newline. Such an executable filename cannot be found (and typically command filenames should consist of only alphanumeric characters, plus underscores, dashes, and dots). Although it is indeed possible to have filenames that contain special characters in them, it is always avoided.



    NOTE: such behavior as shown in your example is specific to Bourne-like shells, including bash, dash (on Ubuntu it is symlinked to /bin/sh), ksh, and mksh. csh and its derivatives do not behave in such way:



    $ tcsh                                                    
    eagle:~> '
    Unmatched '.
    eagle:~> csh
    % '
    Unmatched '.
    %


    However, in interactive mode, csh will still raise ? as prompt2 when more input is required:



    $ csh
    % foreach n ( 1 2 3 )
    ? echo $n
    ? end
    1
    2
    3


    See also:




    • In which situations are PS2, PS3, PS4 used as the prompt?

    • What's the difference between <<, <<< and < < in bash?

    • What does > mean in the terminal!

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

    • What is the effect of a lone backtick at the end of a command line?






    share|improve this answer























    • The link What's the difference between <<, <<< and < < in bash? is offline/wrong.
      – Tico
      Mar 8 '17 at 16:49










    • @Tico Thanks fixed. The answer was written with internet speed of milli-turtles per second, which resulted only in partially copied link. Fixed now
      – Sergiy Kolodyazhnyy
      Mar 8 '17 at 16:51






    • 2




      Meanwhile, zsh is kind enough to actually tell you what it is waiting for, which is occasionally useful if you thought your command was valid but forgot to escape something.
      – Kevin
      Mar 9 '17 at 8:02















    up vote
    23
    down vote



    accepted










    Effectively, the shell asks for a complete command/expression, and for that reason is displaying the PS2 prompt string.



    From man bash:




    PROMPTING



    When executing interactively, bash displays the
    primary prompt PS1 when it is ready to read a
    command, and the secondary prompt PS2 when it
    needs more input to complete a command.




    And a little before that:




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



    Thus, as you may guess from reading the documentation, shells have multiple prompts with different purposes. The PS1 prompt is your root@sai:~# string, which shows up normally when you enter commands. > is the PS2 prompt. There's others, too: PS3 for select command block and PS4 for debugging with set -x command. In this case we're more interested in PS2.



    There are many ways in which shell may show the PS2 prompt (and where completing a command on a new line might be necessary). The same prompt is used when you perform here-doc redirection (where a command is considered complete when you see the terminating string, in this example, EOF):



    $ cat <<EOF
    > line one
    > line two
    > EOF
    line one
    line two


    Very often continuation of a lengthy command can be done by adding and immediate(!) newline, which will cause the same prompt to appear:



    $ echo Hello
    > World
    HelloWorld

    $ echo 'Hello
    > World'
    Hello
    World


    When pipes, logic operators, or special keywords appear on command-line before newline, the command also is considered incomplete until all final statements are entered:



    $ echo Hello World | 
    > wc -l
    1

    $ echo Hello World &&
    > echo "!"
    Hello World
    !

    $ for i in $(seq 1 3); do
    > echo "$i"
    > done
    1
    2
    3

    $ if [ -f /etc/passwd ]
    > then
    > echo "YES"
    > fi
    YES


    In your particular case, a single quote implies literal interpretation of what is between the single quotes. Thus, as Zanna pointed out, you are entering a command that consists of newline+ls+newline. Such an executable filename cannot be found (and typically command filenames should consist of only alphanumeric characters, plus underscores, dashes, and dots). Although it is indeed possible to have filenames that contain special characters in them, it is always avoided.



    NOTE: such behavior as shown in your example is specific to Bourne-like shells, including bash, dash (on Ubuntu it is symlinked to /bin/sh), ksh, and mksh. csh and its derivatives do not behave in such way:



    $ tcsh                                                    
    eagle:~> '
    Unmatched '.
    eagle:~> csh
    % '
    Unmatched '.
    %


    However, in interactive mode, csh will still raise ? as prompt2 when more input is required:



    $ csh
    % foreach n ( 1 2 3 )
    ? echo $n
    ? end
    1
    2
    3


    See also:




    • In which situations are PS2, PS3, PS4 used as the prompt?

    • What's the difference between <<, <<< and < < in bash?

    • What does > mean in the terminal!

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

    • What is the effect of a lone backtick at the end of a command line?






    share|improve this answer























    • The link What's the difference between <<, <<< and < < in bash? is offline/wrong.
      – Tico
      Mar 8 '17 at 16:49










    • @Tico Thanks fixed. The answer was written with internet speed of milli-turtles per second, which resulted only in partially copied link. Fixed now
      – Sergiy Kolodyazhnyy
      Mar 8 '17 at 16:51






    • 2




      Meanwhile, zsh is kind enough to actually tell you what it is waiting for, which is occasionally useful if you thought your command was valid but forgot to escape something.
      – Kevin
      Mar 9 '17 at 8:02













    up vote
    23
    down vote



    accepted







    up vote
    23
    down vote



    accepted






    Effectively, the shell asks for a complete command/expression, and for that reason is displaying the PS2 prompt string.



    From man bash:




    PROMPTING



    When executing interactively, bash displays the
    primary prompt PS1 when it is ready to read a
    command, and the secondary prompt PS2 when it
    needs more input to complete a command.




    And a little before that:




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



    Thus, as you may guess from reading the documentation, shells have multiple prompts with different purposes. The PS1 prompt is your root@sai:~# string, which shows up normally when you enter commands. > is the PS2 prompt. There's others, too: PS3 for select command block and PS4 for debugging with set -x command. In this case we're more interested in PS2.



    There are many ways in which shell may show the PS2 prompt (and where completing a command on a new line might be necessary). The same prompt is used when you perform here-doc redirection (where a command is considered complete when you see the terminating string, in this example, EOF):



    $ cat <<EOF
    > line one
    > line two
    > EOF
    line one
    line two


    Very often continuation of a lengthy command can be done by adding and immediate(!) newline, which will cause the same prompt to appear:



    $ echo Hello
    > World
    HelloWorld

    $ echo 'Hello
    > World'
    Hello
    World


    When pipes, logic operators, or special keywords appear on command-line before newline, the command also is considered incomplete until all final statements are entered:



    $ echo Hello World | 
    > wc -l
    1

    $ echo Hello World &&
    > echo "!"
    Hello World
    !

    $ for i in $(seq 1 3); do
    > echo "$i"
    > done
    1
    2
    3

    $ if [ -f /etc/passwd ]
    > then
    > echo "YES"
    > fi
    YES


    In your particular case, a single quote implies literal interpretation of what is between the single quotes. Thus, as Zanna pointed out, you are entering a command that consists of newline+ls+newline. Such an executable filename cannot be found (and typically command filenames should consist of only alphanumeric characters, plus underscores, dashes, and dots). Although it is indeed possible to have filenames that contain special characters in them, it is always avoided.



    NOTE: such behavior as shown in your example is specific to Bourne-like shells, including bash, dash (on Ubuntu it is symlinked to /bin/sh), ksh, and mksh. csh and its derivatives do not behave in such way:



    $ tcsh                                                    
    eagle:~> '
    Unmatched '.
    eagle:~> csh
    % '
    Unmatched '.
    %


    However, in interactive mode, csh will still raise ? as prompt2 when more input is required:



    $ csh
    % foreach n ( 1 2 3 )
    ? echo $n
    ? end
    1
    2
    3


    See also:




    • In which situations are PS2, PS3, PS4 used as the prompt?

    • What's the difference between <<, <<< and < < in bash?

    • What does > mean in the terminal!

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

    • What is the effect of a lone backtick at the end of a command line?






    share|improve this answer














    Effectively, the shell asks for a complete command/expression, and for that reason is displaying the PS2 prompt string.



    From man bash:




    PROMPTING



    When executing interactively, bash displays the
    primary prompt PS1 when it is ready to read a
    command, and the secondary prompt PS2 when it
    needs more input to complete a command.




    And a little before that:




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



    Thus, as you may guess from reading the documentation, shells have multiple prompts with different purposes. The PS1 prompt is your root@sai:~# string, which shows up normally when you enter commands. > is the PS2 prompt. There's others, too: PS3 for select command block and PS4 for debugging with set -x command. In this case we're more interested in PS2.



    There are many ways in which shell may show the PS2 prompt (and where completing a command on a new line might be necessary). The same prompt is used when you perform here-doc redirection (where a command is considered complete when you see the terminating string, in this example, EOF):



    $ cat <<EOF
    > line one
    > line two
    > EOF
    line one
    line two


    Very often continuation of a lengthy command can be done by adding and immediate(!) newline, which will cause the same prompt to appear:



    $ echo Hello
    > World
    HelloWorld

    $ echo 'Hello
    > World'
    Hello
    World


    When pipes, logic operators, or special keywords appear on command-line before newline, the command also is considered incomplete until all final statements are entered:



    $ echo Hello World | 
    > wc -l
    1

    $ echo Hello World &&
    > echo "!"
    Hello World
    !

    $ for i in $(seq 1 3); do
    > echo "$i"
    > done
    1
    2
    3

    $ if [ -f /etc/passwd ]
    > then
    > echo "YES"
    > fi
    YES


    In your particular case, a single quote implies literal interpretation of what is between the single quotes. Thus, as Zanna pointed out, you are entering a command that consists of newline+ls+newline. Such an executable filename cannot be found (and typically command filenames should consist of only alphanumeric characters, plus underscores, dashes, and dots). Although it is indeed possible to have filenames that contain special characters in them, it is always avoided.



    NOTE: such behavior as shown in your example is specific to Bourne-like shells, including bash, dash (on Ubuntu it is symlinked to /bin/sh), ksh, and mksh. csh and its derivatives do not behave in such way:



    $ tcsh                                                    
    eagle:~> '
    Unmatched '.
    eagle:~> csh
    % '
    Unmatched '.
    %


    However, in interactive mode, csh will still raise ? as prompt2 when more input is required:



    $ csh
    % foreach n ( 1 2 3 )
    ? echo $n
    ? end
    1
    2
    3


    See also:




    • In which situations are PS2, PS3, PS4 used as the prompt?

    • What's the difference between <<, <<< and < < in bash?

    • What does > mean in the terminal!

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

    • What is the effect of a lone backtick at the end of a command line?







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Nov 30 at 0:21









    wjandrea

    8,06142258




    8,06142258










    answered Mar 8 '17 at 7:40









    Sergiy Kolodyazhnyy

    68.9k9143303




    68.9k9143303












    • The link What's the difference between <<, <<< and < < in bash? is offline/wrong.
      – Tico
      Mar 8 '17 at 16:49










    • @Tico Thanks fixed. The answer was written with internet speed of milli-turtles per second, which resulted only in partially copied link. Fixed now
      – Sergiy Kolodyazhnyy
      Mar 8 '17 at 16:51






    • 2




      Meanwhile, zsh is kind enough to actually tell you what it is waiting for, which is occasionally useful if you thought your command was valid but forgot to escape something.
      – Kevin
      Mar 9 '17 at 8:02


















    • The link What's the difference between <<, <<< and < < in bash? is offline/wrong.
      – Tico
      Mar 8 '17 at 16:49










    • @Tico Thanks fixed. The answer was written with internet speed of milli-turtles per second, which resulted only in partially copied link. Fixed now
      – Sergiy Kolodyazhnyy
      Mar 8 '17 at 16:51






    • 2




      Meanwhile, zsh is kind enough to actually tell you what it is waiting for, which is occasionally useful if you thought your command was valid but forgot to escape something.
      – Kevin
      Mar 9 '17 at 8:02
















    The link What's the difference between <<, <<< and < < in bash? is offline/wrong.
    – Tico
    Mar 8 '17 at 16:49




    The link What's the difference between <<, <<< and < < in bash? is offline/wrong.
    – Tico
    Mar 8 '17 at 16:49












    @Tico Thanks fixed. The answer was written with internet speed of milli-turtles per second, which resulted only in partially copied link. Fixed now
    – Sergiy Kolodyazhnyy
    Mar 8 '17 at 16:51




    @Tico Thanks fixed. The answer was written with internet speed of milli-turtles per second, which resulted only in partially copied link. Fixed now
    – Sergiy Kolodyazhnyy
    Mar 8 '17 at 16:51




    2




    2




    Meanwhile, zsh is kind enough to actually tell you what it is waiting for, which is occasionally useful if you thought your command was valid but forgot to escape something.
    – Kevin
    Mar 9 '17 at 8:02




    Meanwhile, zsh is kind enough to actually tell you what it is waiting for, which is occasionally useful if you thought your command was valid but forgot to escape something.
    – Kevin
    Mar 9 '17 at 8:02












    up vote
    28
    down vote













    The shell is just waiting for the closing quote. When you enter it, it will do exactly what it usually does, and attempt to execute the command entered.



    Quotes cause the shell not to interpret special characters, meaning that expansions are not performed. Single quotes suppress all interpretation of special characters completely. Normally a newline separates commands, but here you have included the newlines as part of the command by quoting them.



    Since there is no such command as <newline>ls<newline>, it is not found.






    share|improve this answer



























      up vote
      28
      down vote













      The shell is just waiting for the closing quote. When you enter it, it will do exactly what it usually does, and attempt to execute the command entered.



      Quotes cause the shell not to interpret special characters, meaning that expansions are not performed. Single quotes suppress all interpretation of special characters completely. Normally a newline separates commands, but here you have included the newlines as part of the command by quoting them.



      Since there is no such command as <newline>ls<newline>, it is not found.






      share|improve this answer

























        up vote
        28
        down vote










        up vote
        28
        down vote









        The shell is just waiting for the closing quote. When you enter it, it will do exactly what it usually does, and attempt to execute the command entered.



        Quotes cause the shell not to interpret special characters, meaning that expansions are not performed. Single quotes suppress all interpretation of special characters completely. Normally a newline separates commands, but here you have included the newlines as part of the command by quoting them.



        Since there is no such command as <newline>ls<newline>, it is not found.






        share|improve this answer














        The shell is just waiting for the closing quote. When you enter it, it will do exactly what it usually does, and attempt to execute the command entered.



        Quotes cause the shell not to interpret special characters, meaning that expansions are not performed. Single quotes suppress all interpretation of special characters completely. Normally a newline separates commands, but here you have included the newlines as part of the command by quoting them.



        Since there is no such command as <newline>ls<newline>, it is not found.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Mar 8 '17 at 8:08

























        answered Mar 8 '17 at 7:12









        Zanna

        49.3k13127236




        49.3k13127236






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • 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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2faskubuntu.com%2fquestions%2f890782%2fwhat-mode-does-the-terminal-go-into-when-i-type-a-single-quote%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

            Ellipse (mathématiques)

            Quarter-circle Tiles

            Mont Emei