How to avoid printing a newline when seq completes?












6















To create a column header, looking like:



1234567890123456789


I (am trying to) use seq and echo:



seq -s '' 1 9 ; echo -n 0; seq -s '' 1 9


However, seq outputs a newline after each run. How can I avoid that?










share|improve this question

























  • would you care to elaborate why you can't just echo 1234567890123456789? and why you need just 19 columns? and why the echo -n 0; seq -s '' 1 9 instead of seq -s '' 0 9?

    – pizdelect
    Jan 5 at 18:42











  • @pizdelect: Q1 & 2: I'm looking for an expandable method that might be put in a scripts; Q3: Because I don't want a leading 0.

    – GreenMatt
    Jan 9 at 19:39











  • Q1 & Q2. what do you want to expand it to? I explained in my answer how to make a header as wide as the terminal, without writing the numbers byte by byte. And that's easy to adapt to eg. a header like abcdeabcde.... Q3. the two commands from my comment are equivalent.

    – pizdelect
    Jan 9 at 20:10













  • If any of the answers solved your problem, please accept it by clicking the checkmark next to it. Thank you!

    – Jeff Schaller
    Jan 13 at 15:15
















6















To create a column header, looking like:



1234567890123456789


I (am trying to) use seq and echo:



seq -s '' 1 9 ; echo -n 0; seq -s '' 1 9


However, seq outputs a newline after each run. How can I avoid that?










share|improve this question

























  • would you care to elaborate why you can't just echo 1234567890123456789? and why you need just 19 columns? and why the echo -n 0; seq -s '' 1 9 instead of seq -s '' 0 9?

    – pizdelect
    Jan 5 at 18:42











  • @pizdelect: Q1 & 2: I'm looking for an expandable method that might be put in a scripts; Q3: Because I don't want a leading 0.

    – GreenMatt
    Jan 9 at 19:39











  • Q1 & Q2. what do you want to expand it to? I explained in my answer how to make a header as wide as the terminal, without writing the numbers byte by byte. And that's easy to adapt to eg. a header like abcdeabcde.... Q3. the two commands from my comment are equivalent.

    – pizdelect
    Jan 9 at 20:10













  • If any of the answers solved your problem, please accept it by clicking the checkmark next to it. Thank you!

    – Jeff Schaller
    Jan 13 at 15:15














6












6








6








To create a column header, looking like:



1234567890123456789


I (am trying to) use seq and echo:



seq -s '' 1 9 ; echo -n 0; seq -s '' 1 9


However, seq outputs a newline after each run. How can I avoid that?










share|improve this question
















To create a column header, looking like:



1234567890123456789


I (am trying to) use seq and echo:



seq -s '' 1 9 ; echo -n 0; seq -s '' 1 9


However, seq outputs a newline after each run. How can I avoid that?







gnu seq






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 4 at 2:44









poige

4,1851646




4,1851646










asked Jan 3 at 19:54









GreenMattGreenMatt

23428




23428













  • would you care to elaborate why you can't just echo 1234567890123456789? and why you need just 19 columns? and why the echo -n 0; seq -s '' 1 9 instead of seq -s '' 0 9?

    – pizdelect
    Jan 5 at 18:42











  • @pizdelect: Q1 & 2: I'm looking for an expandable method that might be put in a scripts; Q3: Because I don't want a leading 0.

    – GreenMatt
    Jan 9 at 19:39











  • Q1 & Q2. what do you want to expand it to? I explained in my answer how to make a header as wide as the terminal, without writing the numbers byte by byte. And that's easy to adapt to eg. a header like abcdeabcde.... Q3. the two commands from my comment are equivalent.

    – pizdelect
    Jan 9 at 20:10













  • If any of the answers solved your problem, please accept it by clicking the checkmark next to it. Thank you!

    – Jeff Schaller
    Jan 13 at 15:15



















  • would you care to elaborate why you can't just echo 1234567890123456789? and why you need just 19 columns? and why the echo -n 0; seq -s '' 1 9 instead of seq -s '' 0 9?

    – pizdelect
    Jan 5 at 18:42











  • @pizdelect: Q1 & 2: I'm looking for an expandable method that might be put in a scripts; Q3: Because I don't want a leading 0.

    – GreenMatt
    Jan 9 at 19:39











  • Q1 & Q2. what do you want to expand it to? I explained in my answer how to make a header as wide as the terminal, without writing the numbers byte by byte. And that's easy to adapt to eg. a header like abcdeabcde.... Q3. the two commands from my comment are equivalent.

    – pizdelect
    Jan 9 at 20:10













  • If any of the answers solved your problem, please accept it by clicking the checkmark next to it. Thank you!

    – Jeff Schaller
    Jan 13 at 15:15

















would you care to elaborate why you can't just echo 1234567890123456789? and why you need just 19 columns? and why the echo -n 0; seq -s '' 1 9 instead of seq -s '' 0 9?

– pizdelect
Jan 5 at 18:42





would you care to elaborate why you can't just echo 1234567890123456789? and why you need just 19 columns? and why the echo -n 0; seq -s '' 1 9 instead of seq -s '' 0 9?

– pizdelect
Jan 5 at 18:42













@pizdelect: Q1 & 2: I'm looking for an expandable method that might be put in a scripts; Q3: Because I don't want a leading 0.

– GreenMatt
Jan 9 at 19:39





@pizdelect: Q1 & 2: I'm looking for an expandable method that might be put in a scripts; Q3: Because I don't want a leading 0.

– GreenMatt
Jan 9 at 19:39













Q1 & Q2. what do you want to expand it to? I explained in my answer how to make a header as wide as the terminal, without writing the numbers byte by byte. And that's easy to adapt to eg. a header like abcdeabcde.... Q3. the two commands from my comment are equivalent.

– pizdelect
Jan 9 at 20:10







Q1 & Q2. what do you want to expand it to? I explained in my answer how to make a header as wide as the terminal, without writing the numbers byte by byte. And that's easy to adapt to eg. a header like abcdeabcde.... Q3. the two commands from my comment are equivalent.

– pizdelect
Jan 9 at 20:10















If any of the answers solved your problem, please accept it by clicking the checkmark next to it. Thank you!

– Jeff Schaller
Jan 13 at 15:15





If any of the answers solved your problem, please accept it by clicking the checkmark next to it. Thank you!

– Jeff Schaller
Jan 13 at 15:15










7 Answers
7






active

oldest

votes


















10














Assuming you just want to print 1234567890123456789, you can do it with:



$ printf "%s" $(seq 1 9) $(seq 0 9)
1234567890123456789$


That won't have a trailing newline at all though, so maybe you prefer:



$ printf "%s" $(seq 1 9) $(seq 0 9) $'n'
1234567890123456789
$


A few simpler choices if you don't need to use seq:



$ perl -le 'print 1..9,0,1..9'
1234567890123456789
$ printf "%s" {1..9} {0..9} $'n'
1234567890123456789


Since you mentioned portability, I recommend you use the perl approach, or if you are likely to encounter systems without perl, and yet need the same command to run in shells including bash, sh, dash, tcsh etc, try Kamil's approach.






share|improve this answer





















  • 1





    @GreenMatt ah, that depends. For extreme portability, you may as well just use the perl one which is shell-agnostic. The printf "%s" $(seq 1 9) $(seq 0 9) will work in any POSIX shell, including sh and dash, but the printf "%s" $(seq 1 9) $(seq 0 9) $'n' will fail in dash. Note that it does work in sh (or at least in bash running as sh, so in POSIX mode), I assume you're running Ubuntu or a simmilar system whose sh is actually dash. tcsh is a strange one and not even trying to be POSIX so don't expect any of the shell-based approaches to work there.

    – terdon
    Jan 3 at 20:21








  • 3





    @GreenMatt of course, if you need portability, you should also avoid using echo.

    – terdon
    Jan 3 at 20:25






  • 2





    @GreenMatt lol. Say what you like about Perl, you just can't beat it for text manipulation and it is extremely portable.

    – terdon
    Jan 3 at 21:19






  • 1





    @Larry, not with that printf structure you can't, the format string gets repeated for each argument, but we only want one newline.

    – ilkkachu
    Jan 3 at 22:22






  • 1





    @Larry, mm, the command you posted as a comment prints one digit per line. But I'm starting to think you should post that as an answer of your own if you want to refine or discuss it further.

    – ilkkachu
    Jan 3 at 22:35



















6














You can remove newlines from any stream with tr -d 'n'. In your case



(seq -s '' 1 9 ; echo -n 0; seq -s '' 1 9) | tr -d 'n'


While other answers may concentrate on modifying your original approach, this is the way that should just remove newline characters regardless of what is before |.






share|improve this answer



















  • 1





    Nice. This also has the benefit of being portable to most (all?) shells. I think the OP wants the final newline, so another option might be ( seq -s '' 1 9 ; echo -n 0 ; seq -s '' 1 9 ) | tr -d 'n' ; printf "n".

    – terdon
    Jan 3 at 20:34











  • Ah yes, I never think of tr.

    – GreenMatt
    Jan 3 at 20:38











  • +1. Also, worth saying that BSD version of seq does treat -s '' more fully than GNU's — no newline is printed even when it exits (they q-n wouldn't arise at all there)

    – poige
    Jan 4 at 2:43













  • My take on this: unix.stackexchange.com/a/492380/6622

    – poige
    Jan 4 at 4:09



















4














I assume you don't want just that particular string, but strings of incrementing digits with variable lengths. For that, it may be useful to be able to change the width by changing one number, instead of having to build it from multiple calls to seq.



In Bash, you could use something like this (for a 19-long sequence):



for ((i=1; i <= 19; i++)); do printf "%d" "$(( i % 10 ))"; done; echo


This should work in a standard shell (and works in at least dash and busybox, anyway):



i=1; while [ "$i" -le 19 ]; do printf "%d" "$(( i % 10 ))"; i=$((i+1)); done; echo





share|improve this answer


























  • +1: The latter approach looks like everything it needs should be guaranteed to be available in any POSIX-y shell to me.

    – Charles Duffy
    Jan 3 at 22:01



















4














Consider also:



printf '%d' $(seq -w 1 1 99 | cut -c2)


We generate the numbers 01..99, zero-padded (-w), then strip off the tens-place. Those ones-place numbers are then sent to printf to be printed individually.



To get your desired output, use 19 instead:



$ printf '%d' $(seq -w 1 1 19 | cut -c2)
1234567890123456789





share|improve this answer

































    1














    To remove the trailing newline, just use a command execution:



     $ echo "test$(seq -s '' 9)no-newline"
    test12345679no-newline


    Or capture it in a variable:



     $ var=$(seq -s '' 9); echo "${var}0${var}"
    1234567890123456789


    Or also:



     $ printf '%s' {{0..9},0,{0..9}}; echo
    1234567890123456789





    share|improve this answer

































      0














      I wonder why you don't just:



      echo 1234567890123456789


      And what's the point of printing just 19 columns instead of 20?



      If you want it repeated (by default: for the whole width of the terminal)



      chdr(){ c=${1:-$COLUMNS}; while [ "$c" -gt 0 ]; do printf '%.*s' "$c" 1234567890; c=$((c-10)); done; echo; }
      chdr 17
      12345678901234567
      chdr
      12345678901234567890123456789012345678901234567890123456789012345678901234567890


      Of course, that won't work in csh (huh).



      FYI: seq isn't portable (there's jot on *BSD, but it's quite different).






      share|improve this answer

































        0














        When using tr to get rid of trailing new-line it's worth realising that it deletes all occurrences of the characters given in its -d option. Thus you can get it a bit more slim:



        (seq 1 9; echo 0; seq 1 9) | tr -d 'n'


        — even echo doesn't need to have -n anymore.



        And for completeness sake: BSD's version of seq when -s '' specified doesn't produce new-line on its exit.






        share|improve this answer
























          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          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: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          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%2funix.stackexchange.com%2fquestions%2f492315%2fhow-to-avoid-printing-a-newline-when-seq-completes%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          7 Answers
          7






          active

          oldest

          votes








          7 Answers
          7






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          10














          Assuming you just want to print 1234567890123456789, you can do it with:



          $ printf "%s" $(seq 1 9) $(seq 0 9)
          1234567890123456789$


          That won't have a trailing newline at all though, so maybe you prefer:



          $ printf "%s" $(seq 1 9) $(seq 0 9) $'n'
          1234567890123456789
          $


          A few simpler choices if you don't need to use seq:



          $ perl -le 'print 1..9,0,1..9'
          1234567890123456789
          $ printf "%s" {1..9} {0..9} $'n'
          1234567890123456789


          Since you mentioned portability, I recommend you use the perl approach, or if you are likely to encounter systems without perl, and yet need the same command to run in shells including bash, sh, dash, tcsh etc, try Kamil's approach.






          share|improve this answer





















          • 1





            @GreenMatt ah, that depends. For extreme portability, you may as well just use the perl one which is shell-agnostic. The printf "%s" $(seq 1 9) $(seq 0 9) will work in any POSIX shell, including sh and dash, but the printf "%s" $(seq 1 9) $(seq 0 9) $'n' will fail in dash. Note that it does work in sh (or at least in bash running as sh, so in POSIX mode), I assume you're running Ubuntu or a simmilar system whose sh is actually dash. tcsh is a strange one and not even trying to be POSIX so don't expect any of the shell-based approaches to work there.

            – terdon
            Jan 3 at 20:21








          • 3





            @GreenMatt of course, if you need portability, you should also avoid using echo.

            – terdon
            Jan 3 at 20:25






          • 2





            @GreenMatt lol. Say what you like about Perl, you just can't beat it for text manipulation and it is extremely portable.

            – terdon
            Jan 3 at 21:19






          • 1





            @Larry, not with that printf structure you can't, the format string gets repeated for each argument, but we only want one newline.

            – ilkkachu
            Jan 3 at 22:22






          • 1





            @Larry, mm, the command you posted as a comment prints one digit per line. But I'm starting to think you should post that as an answer of your own if you want to refine or discuss it further.

            – ilkkachu
            Jan 3 at 22:35
















          10














          Assuming you just want to print 1234567890123456789, you can do it with:



          $ printf "%s" $(seq 1 9) $(seq 0 9)
          1234567890123456789$


          That won't have a trailing newline at all though, so maybe you prefer:



          $ printf "%s" $(seq 1 9) $(seq 0 9) $'n'
          1234567890123456789
          $


          A few simpler choices if you don't need to use seq:



          $ perl -le 'print 1..9,0,1..9'
          1234567890123456789
          $ printf "%s" {1..9} {0..9} $'n'
          1234567890123456789


          Since you mentioned portability, I recommend you use the perl approach, or if you are likely to encounter systems without perl, and yet need the same command to run in shells including bash, sh, dash, tcsh etc, try Kamil's approach.






          share|improve this answer





















          • 1





            @GreenMatt ah, that depends. For extreme portability, you may as well just use the perl one which is shell-agnostic. The printf "%s" $(seq 1 9) $(seq 0 9) will work in any POSIX shell, including sh and dash, but the printf "%s" $(seq 1 9) $(seq 0 9) $'n' will fail in dash. Note that it does work in sh (or at least in bash running as sh, so in POSIX mode), I assume you're running Ubuntu or a simmilar system whose sh is actually dash. tcsh is a strange one and not even trying to be POSIX so don't expect any of the shell-based approaches to work there.

            – terdon
            Jan 3 at 20:21








          • 3





            @GreenMatt of course, if you need portability, you should also avoid using echo.

            – terdon
            Jan 3 at 20:25






          • 2





            @GreenMatt lol. Say what you like about Perl, you just can't beat it for text manipulation and it is extremely portable.

            – terdon
            Jan 3 at 21:19






          • 1





            @Larry, not with that printf structure you can't, the format string gets repeated for each argument, but we only want one newline.

            – ilkkachu
            Jan 3 at 22:22






          • 1





            @Larry, mm, the command you posted as a comment prints one digit per line. But I'm starting to think you should post that as an answer of your own if you want to refine or discuss it further.

            – ilkkachu
            Jan 3 at 22:35














          10












          10








          10







          Assuming you just want to print 1234567890123456789, you can do it with:



          $ printf "%s" $(seq 1 9) $(seq 0 9)
          1234567890123456789$


          That won't have a trailing newline at all though, so maybe you prefer:



          $ printf "%s" $(seq 1 9) $(seq 0 9) $'n'
          1234567890123456789
          $


          A few simpler choices if you don't need to use seq:



          $ perl -le 'print 1..9,0,1..9'
          1234567890123456789
          $ printf "%s" {1..9} {0..9} $'n'
          1234567890123456789


          Since you mentioned portability, I recommend you use the perl approach, or if you are likely to encounter systems without perl, and yet need the same command to run in shells including bash, sh, dash, tcsh etc, try Kamil's approach.






          share|improve this answer















          Assuming you just want to print 1234567890123456789, you can do it with:



          $ printf "%s" $(seq 1 9) $(seq 0 9)
          1234567890123456789$


          That won't have a trailing newline at all though, so maybe you prefer:



          $ printf "%s" $(seq 1 9) $(seq 0 9) $'n'
          1234567890123456789
          $


          A few simpler choices if you don't need to use seq:



          $ perl -le 'print 1..9,0,1..9'
          1234567890123456789
          $ printf "%s" {1..9} {0..9} $'n'
          1234567890123456789


          Since you mentioned portability, I recommend you use the perl approach, or if you are likely to encounter systems without perl, and yet need the same command to run in shells including bash, sh, dash, tcsh etc, try Kamil's approach.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jan 3 at 20:34

























          answered Jan 3 at 20:00









          terdonterdon

          133k33267446




          133k33267446








          • 1





            @GreenMatt ah, that depends. For extreme portability, you may as well just use the perl one which is shell-agnostic. The printf "%s" $(seq 1 9) $(seq 0 9) will work in any POSIX shell, including sh and dash, but the printf "%s" $(seq 1 9) $(seq 0 9) $'n' will fail in dash. Note that it does work in sh (or at least in bash running as sh, so in POSIX mode), I assume you're running Ubuntu or a simmilar system whose sh is actually dash. tcsh is a strange one and not even trying to be POSIX so don't expect any of the shell-based approaches to work there.

            – terdon
            Jan 3 at 20:21








          • 3





            @GreenMatt of course, if you need portability, you should also avoid using echo.

            – terdon
            Jan 3 at 20:25






          • 2





            @GreenMatt lol. Say what you like about Perl, you just can't beat it for text manipulation and it is extremely portable.

            – terdon
            Jan 3 at 21:19






          • 1





            @Larry, not with that printf structure you can't, the format string gets repeated for each argument, but we only want one newline.

            – ilkkachu
            Jan 3 at 22:22






          • 1





            @Larry, mm, the command you posted as a comment prints one digit per line. But I'm starting to think you should post that as an answer of your own if you want to refine or discuss it further.

            – ilkkachu
            Jan 3 at 22:35














          • 1





            @GreenMatt ah, that depends. For extreme portability, you may as well just use the perl one which is shell-agnostic. The printf "%s" $(seq 1 9) $(seq 0 9) will work in any POSIX shell, including sh and dash, but the printf "%s" $(seq 1 9) $(seq 0 9) $'n' will fail in dash. Note that it does work in sh (or at least in bash running as sh, so in POSIX mode), I assume you're running Ubuntu or a simmilar system whose sh is actually dash. tcsh is a strange one and not even trying to be POSIX so don't expect any of the shell-based approaches to work there.

            – terdon
            Jan 3 at 20:21








          • 3





            @GreenMatt of course, if you need portability, you should also avoid using echo.

            – terdon
            Jan 3 at 20:25






          • 2





            @GreenMatt lol. Say what you like about Perl, you just can't beat it for text manipulation and it is extremely portable.

            – terdon
            Jan 3 at 21:19






          • 1





            @Larry, not with that printf structure you can't, the format string gets repeated for each argument, but we only want one newline.

            – ilkkachu
            Jan 3 at 22:22






          • 1





            @Larry, mm, the command you posted as a comment prints one digit per line. But I'm starting to think you should post that as an answer of your own if you want to refine or discuss it further.

            – ilkkachu
            Jan 3 at 22:35








          1




          1





          @GreenMatt ah, that depends. For extreme portability, you may as well just use the perl one which is shell-agnostic. The printf "%s" $(seq 1 9) $(seq 0 9) will work in any POSIX shell, including sh and dash, but the printf "%s" $(seq 1 9) $(seq 0 9) $'n' will fail in dash. Note that it does work in sh (or at least in bash running as sh, so in POSIX mode), I assume you're running Ubuntu or a simmilar system whose sh is actually dash. tcsh is a strange one and not even trying to be POSIX so don't expect any of the shell-based approaches to work there.

          – terdon
          Jan 3 at 20:21







          @GreenMatt ah, that depends. For extreme portability, you may as well just use the perl one which is shell-agnostic. The printf "%s" $(seq 1 9) $(seq 0 9) will work in any POSIX shell, including sh and dash, but the printf "%s" $(seq 1 9) $(seq 0 9) $'n' will fail in dash. Note that it does work in sh (or at least in bash running as sh, so in POSIX mode), I assume you're running Ubuntu or a simmilar system whose sh is actually dash. tcsh is a strange one and not even trying to be POSIX so don't expect any of the shell-based approaches to work there.

          – terdon
          Jan 3 at 20:21






          3




          3





          @GreenMatt of course, if you need portability, you should also avoid using echo.

          – terdon
          Jan 3 at 20:25





          @GreenMatt of course, if you need portability, you should also avoid using echo.

          – terdon
          Jan 3 at 20:25




          2




          2





          @GreenMatt lol. Say what you like about Perl, you just can't beat it for text manipulation and it is extremely portable.

          – terdon
          Jan 3 at 21:19





          @GreenMatt lol. Say what you like about Perl, you just can't beat it for text manipulation and it is extremely portable.

          – terdon
          Jan 3 at 21:19




          1




          1





          @Larry, not with that printf structure you can't, the format string gets repeated for each argument, but we only want one newline.

          – ilkkachu
          Jan 3 at 22:22





          @Larry, not with that printf structure you can't, the format string gets repeated for each argument, but we only want one newline.

          – ilkkachu
          Jan 3 at 22:22




          1




          1





          @Larry, mm, the command you posted as a comment prints one digit per line. But I'm starting to think you should post that as an answer of your own if you want to refine or discuss it further.

          – ilkkachu
          Jan 3 at 22:35





          @Larry, mm, the command you posted as a comment prints one digit per line. But I'm starting to think you should post that as an answer of your own if you want to refine or discuss it further.

          – ilkkachu
          Jan 3 at 22:35













          6














          You can remove newlines from any stream with tr -d 'n'. In your case



          (seq -s '' 1 9 ; echo -n 0; seq -s '' 1 9) | tr -d 'n'


          While other answers may concentrate on modifying your original approach, this is the way that should just remove newline characters regardless of what is before |.






          share|improve this answer



















          • 1





            Nice. This also has the benefit of being portable to most (all?) shells. I think the OP wants the final newline, so another option might be ( seq -s '' 1 9 ; echo -n 0 ; seq -s '' 1 9 ) | tr -d 'n' ; printf "n".

            – terdon
            Jan 3 at 20:34











          • Ah yes, I never think of tr.

            – GreenMatt
            Jan 3 at 20:38











          • +1. Also, worth saying that BSD version of seq does treat -s '' more fully than GNU's — no newline is printed even when it exits (they q-n wouldn't arise at all there)

            – poige
            Jan 4 at 2:43













          • My take on this: unix.stackexchange.com/a/492380/6622

            – poige
            Jan 4 at 4:09
















          6














          You can remove newlines from any stream with tr -d 'n'. In your case



          (seq -s '' 1 9 ; echo -n 0; seq -s '' 1 9) | tr -d 'n'


          While other answers may concentrate on modifying your original approach, this is the way that should just remove newline characters regardless of what is before |.






          share|improve this answer



















          • 1





            Nice. This also has the benefit of being portable to most (all?) shells. I think the OP wants the final newline, so another option might be ( seq -s '' 1 9 ; echo -n 0 ; seq -s '' 1 9 ) | tr -d 'n' ; printf "n".

            – terdon
            Jan 3 at 20:34











          • Ah yes, I never think of tr.

            – GreenMatt
            Jan 3 at 20:38











          • +1. Also, worth saying that BSD version of seq does treat -s '' more fully than GNU's — no newline is printed even when it exits (they q-n wouldn't arise at all there)

            – poige
            Jan 4 at 2:43













          • My take on this: unix.stackexchange.com/a/492380/6622

            – poige
            Jan 4 at 4:09














          6












          6








          6







          You can remove newlines from any stream with tr -d 'n'. In your case



          (seq -s '' 1 9 ; echo -n 0; seq -s '' 1 9) | tr -d 'n'


          While other answers may concentrate on modifying your original approach, this is the way that should just remove newline characters regardless of what is before |.






          share|improve this answer













          You can remove newlines from any stream with tr -d 'n'. In your case



          (seq -s '' 1 9 ; echo -n 0; seq -s '' 1 9) | tr -d 'n'


          While other answers may concentrate on modifying your original approach, this is the way that should just remove newline characters regardless of what is before |.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 3 at 20:23









          Kamil MaciorowskiKamil Maciorowski

          1,69011030




          1,69011030








          • 1





            Nice. This also has the benefit of being portable to most (all?) shells. I think the OP wants the final newline, so another option might be ( seq -s '' 1 9 ; echo -n 0 ; seq -s '' 1 9 ) | tr -d 'n' ; printf "n".

            – terdon
            Jan 3 at 20:34











          • Ah yes, I never think of tr.

            – GreenMatt
            Jan 3 at 20:38











          • +1. Also, worth saying that BSD version of seq does treat -s '' more fully than GNU's — no newline is printed even when it exits (they q-n wouldn't arise at all there)

            – poige
            Jan 4 at 2:43













          • My take on this: unix.stackexchange.com/a/492380/6622

            – poige
            Jan 4 at 4:09














          • 1





            Nice. This also has the benefit of being portable to most (all?) shells. I think the OP wants the final newline, so another option might be ( seq -s '' 1 9 ; echo -n 0 ; seq -s '' 1 9 ) | tr -d 'n' ; printf "n".

            – terdon
            Jan 3 at 20:34











          • Ah yes, I never think of tr.

            – GreenMatt
            Jan 3 at 20:38











          • +1. Also, worth saying that BSD version of seq does treat -s '' more fully than GNU's — no newline is printed even when it exits (they q-n wouldn't arise at all there)

            – poige
            Jan 4 at 2:43













          • My take on this: unix.stackexchange.com/a/492380/6622

            – poige
            Jan 4 at 4:09








          1




          1





          Nice. This also has the benefit of being portable to most (all?) shells. I think the OP wants the final newline, so another option might be ( seq -s '' 1 9 ; echo -n 0 ; seq -s '' 1 9 ) | tr -d 'n' ; printf "n".

          – terdon
          Jan 3 at 20:34





          Nice. This also has the benefit of being portable to most (all?) shells. I think the OP wants the final newline, so another option might be ( seq -s '' 1 9 ; echo -n 0 ; seq -s '' 1 9 ) | tr -d 'n' ; printf "n".

          – terdon
          Jan 3 at 20:34













          Ah yes, I never think of tr.

          – GreenMatt
          Jan 3 at 20:38





          Ah yes, I never think of tr.

          – GreenMatt
          Jan 3 at 20:38













          +1. Also, worth saying that BSD version of seq does treat -s '' more fully than GNU's — no newline is printed even when it exits (they q-n wouldn't arise at all there)

          – poige
          Jan 4 at 2:43







          +1. Also, worth saying that BSD version of seq does treat -s '' more fully than GNU's — no newline is printed even when it exits (they q-n wouldn't arise at all there)

          – poige
          Jan 4 at 2:43















          My take on this: unix.stackexchange.com/a/492380/6622

          – poige
          Jan 4 at 4:09





          My take on this: unix.stackexchange.com/a/492380/6622

          – poige
          Jan 4 at 4:09











          4














          I assume you don't want just that particular string, but strings of incrementing digits with variable lengths. For that, it may be useful to be able to change the width by changing one number, instead of having to build it from multiple calls to seq.



          In Bash, you could use something like this (for a 19-long sequence):



          for ((i=1; i <= 19; i++)); do printf "%d" "$(( i % 10 ))"; done; echo


          This should work in a standard shell (and works in at least dash and busybox, anyway):



          i=1; while [ "$i" -le 19 ]; do printf "%d" "$(( i % 10 ))"; i=$((i+1)); done; echo





          share|improve this answer


























          • +1: The latter approach looks like everything it needs should be guaranteed to be available in any POSIX-y shell to me.

            – Charles Duffy
            Jan 3 at 22:01
















          4














          I assume you don't want just that particular string, but strings of incrementing digits with variable lengths. For that, it may be useful to be able to change the width by changing one number, instead of having to build it from multiple calls to seq.



          In Bash, you could use something like this (for a 19-long sequence):



          for ((i=1; i <= 19; i++)); do printf "%d" "$(( i % 10 ))"; done; echo


          This should work in a standard shell (and works in at least dash and busybox, anyway):



          i=1; while [ "$i" -le 19 ]; do printf "%d" "$(( i % 10 ))"; i=$((i+1)); done; echo





          share|improve this answer


























          • +1: The latter approach looks like everything it needs should be guaranteed to be available in any POSIX-y shell to me.

            – Charles Duffy
            Jan 3 at 22:01














          4












          4








          4







          I assume you don't want just that particular string, but strings of incrementing digits with variable lengths. For that, it may be useful to be able to change the width by changing one number, instead of having to build it from multiple calls to seq.



          In Bash, you could use something like this (for a 19-long sequence):



          for ((i=1; i <= 19; i++)); do printf "%d" "$(( i % 10 ))"; done; echo


          This should work in a standard shell (and works in at least dash and busybox, anyway):



          i=1; while [ "$i" -le 19 ]; do printf "%d" "$(( i % 10 ))"; i=$((i+1)); done; echo





          share|improve this answer















          I assume you don't want just that particular string, but strings of incrementing digits with variable lengths. For that, it may be useful to be able to change the width by changing one number, instead of having to build it from multiple calls to seq.



          In Bash, you could use something like this (for a 19-long sequence):



          for ((i=1; i <= 19; i++)); do printf "%d" "$(( i % 10 ))"; done; echo


          This should work in a standard shell (and works in at least dash and busybox, anyway):



          i=1; while [ "$i" -le 19 ]; do printf "%d" "$(( i % 10 ))"; i=$((i+1)); done; echo






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jan 3 at 22:02

























          answered Jan 3 at 22:00









          ilkkachuilkkachu

          63k10103180




          63k10103180













          • +1: The latter approach looks like everything it needs should be guaranteed to be available in any POSIX-y shell to me.

            – Charles Duffy
            Jan 3 at 22:01



















          • +1: The latter approach looks like everything it needs should be guaranteed to be available in any POSIX-y shell to me.

            – Charles Duffy
            Jan 3 at 22:01

















          +1: The latter approach looks like everything it needs should be guaranteed to be available in any POSIX-y shell to me.

          – Charles Duffy
          Jan 3 at 22:01





          +1: The latter approach looks like everything it needs should be guaranteed to be available in any POSIX-y shell to me.

          – Charles Duffy
          Jan 3 at 22:01











          4














          Consider also:



          printf '%d' $(seq -w 1 1 99 | cut -c2)


          We generate the numbers 01..99, zero-padded (-w), then strip off the tens-place. Those ones-place numbers are then sent to printf to be printed individually.



          To get your desired output, use 19 instead:



          $ printf '%d' $(seq -w 1 1 19 | cut -c2)
          1234567890123456789





          share|improve this answer






























            4














            Consider also:



            printf '%d' $(seq -w 1 1 99 | cut -c2)


            We generate the numbers 01..99, zero-padded (-w), then strip off the tens-place. Those ones-place numbers are then sent to printf to be printed individually.



            To get your desired output, use 19 instead:



            $ printf '%d' $(seq -w 1 1 19 | cut -c2)
            1234567890123456789





            share|improve this answer




























              4












              4








              4







              Consider also:



              printf '%d' $(seq -w 1 1 99 | cut -c2)


              We generate the numbers 01..99, zero-padded (-w), then strip off the tens-place. Those ones-place numbers are then sent to printf to be printed individually.



              To get your desired output, use 19 instead:



              $ printf '%d' $(seq -w 1 1 19 | cut -c2)
              1234567890123456789





              share|improve this answer















              Consider also:



              printf '%d' $(seq -w 1 1 99 | cut -c2)


              We generate the numbers 01..99, zero-padded (-w), then strip off the tens-place. Those ones-place numbers are then sent to printf to be printed individually.



              To get your desired output, use 19 instead:



              $ printf '%d' $(seq -w 1 1 19 | cut -c2)
              1234567890123456789






              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Jan 4 at 0:28









              JoL

              1,154412




              1,154412










              answered Jan 3 at 20:08









              Jeff SchallerJeff Schaller

              44.6k1162143




              44.6k1162143























                  1














                  To remove the trailing newline, just use a command execution:



                   $ echo "test$(seq -s '' 9)no-newline"
                  test12345679no-newline


                  Or capture it in a variable:



                   $ var=$(seq -s '' 9); echo "${var}0${var}"
                  1234567890123456789


                  Or also:



                   $ printf '%s' {{0..9},0,{0..9}}; echo
                  1234567890123456789





                  share|improve this answer






























                    1














                    To remove the trailing newline, just use a command execution:



                     $ echo "test$(seq -s '' 9)no-newline"
                    test12345679no-newline


                    Or capture it in a variable:



                     $ var=$(seq -s '' 9); echo "${var}0${var}"
                    1234567890123456789


                    Or also:



                     $ printf '%s' {{0..9},0,{0..9}}; echo
                    1234567890123456789





                    share|improve this answer




























                      1












                      1








                      1







                      To remove the trailing newline, just use a command execution:



                       $ echo "test$(seq -s '' 9)no-newline"
                      test12345679no-newline


                      Or capture it in a variable:



                       $ var=$(seq -s '' 9); echo "${var}0${var}"
                      1234567890123456789


                      Or also:



                       $ printf '%s' {{0..9},0,{0..9}}; echo
                      1234567890123456789





                      share|improve this answer















                      To remove the trailing newline, just use a command execution:



                       $ echo "test$(seq -s '' 9)no-newline"
                      test12345679no-newline


                      Or capture it in a variable:



                       $ var=$(seq -s '' 9); echo "${var}0${var}"
                      1234567890123456789


                      Or also:



                       $ printf '%s' {{0..9},0,{0..9}}; echo
                      1234567890123456789






                      share|improve this answer














                      share|improve this answer



                      share|improve this answer








                      edited Jan 4 at 11:17

























                      answered Jan 4 at 11:01









                      IsaacIsaac

                      12.2k11954




                      12.2k11954























                          0














                          I wonder why you don't just:



                          echo 1234567890123456789


                          And what's the point of printing just 19 columns instead of 20?



                          If you want it repeated (by default: for the whole width of the terminal)



                          chdr(){ c=${1:-$COLUMNS}; while [ "$c" -gt 0 ]; do printf '%.*s' "$c" 1234567890; c=$((c-10)); done; echo; }
                          chdr 17
                          12345678901234567
                          chdr
                          12345678901234567890123456789012345678901234567890123456789012345678901234567890


                          Of course, that won't work in csh (huh).



                          FYI: seq isn't portable (there's jot on *BSD, but it's quite different).






                          share|improve this answer






























                            0














                            I wonder why you don't just:



                            echo 1234567890123456789


                            And what's the point of printing just 19 columns instead of 20?



                            If you want it repeated (by default: for the whole width of the terminal)



                            chdr(){ c=${1:-$COLUMNS}; while [ "$c" -gt 0 ]; do printf '%.*s' "$c" 1234567890; c=$((c-10)); done; echo; }
                            chdr 17
                            12345678901234567
                            chdr
                            12345678901234567890123456789012345678901234567890123456789012345678901234567890


                            Of course, that won't work in csh (huh).



                            FYI: seq isn't portable (there's jot on *BSD, but it's quite different).






                            share|improve this answer




























                              0












                              0








                              0







                              I wonder why you don't just:



                              echo 1234567890123456789


                              And what's the point of printing just 19 columns instead of 20?



                              If you want it repeated (by default: for the whole width of the terminal)



                              chdr(){ c=${1:-$COLUMNS}; while [ "$c" -gt 0 ]; do printf '%.*s' "$c" 1234567890; c=$((c-10)); done; echo; }
                              chdr 17
                              12345678901234567
                              chdr
                              12345678901234567890123456789012345678901234567890123456789012345678901234567890


                              Of course, that won't work in csh (huh).



                              FYI: seq isn't portable (there's jot on *BSD, but it's quite different).






                              share|improve this answer















                              I wonder why you don't just:



                              echo 1234567890123456789


                              And what's the point of printing just 19 columns instead of 20?



                              If you want it repeated (by default: for the whole width of the terminal)



                              chdr(){ c=${1:-$COLUMNS}; while [ "$c" -gt 0 ]; do printf '%.*s' "$c" 1234567890; c=$((c-10)); done; echo; }
                              chdr 17
                              12345678901234567
                              chdr
                              12345678901234567890123456789012345678901234567890123456789012345678901234567890


                              Of course, that won't work in csh (huh).



                              FYI: seq isn't portable (there's jot on *BSD, but it's quite different).







                              share|improve this answer














                              share|improve this answer



                              share|improve this answer








                              edited Jan 4 at 3:54

























                              answered Jan 4 at 3:29









                              pizdelectpizdelect

                              71429




                              71429























                                  0














                                  When using tr to get rid of trailing new-line it's worth realising that it deletes all occurrences of the characters given in its -d option. Thus you can get it a bit more slim:



                                  (seq 1 9; echo 0; seq 1 9) | tr -d 'n'


                                  — even echo doesn't need to have -n anymore.



                                  And for completeness sake: BSD's version of seq when -s '' specified doesn't produce new-line on its exit.






                                  share|improve this answer




























                                    0














                                    When using tr to get rid of trailing new-line it's worth realising that it deletes all occurrences of the characters given in its -d option. Thus you can get it a bit more slim:



                                    (seq 1 9; echo 0; seq 1 9) | tr -d 'n'


                                    — even echo doesn't need to have -n anymore.



                                    And for completeness sake: BSD's version of seq when -s '' specified doesn't produce new-line on its exit.






                                    share|improve this answer


























                                      0












                                      0








                                      0







                                      When using tr to get rid of trailing new-line it's worth realising that it deletes all occurrences of the characters given in its -d option. Thus you can get it a bit more slim:



                                      (seq 1 9; echo 0; seq 1 9) | tr -d 'n'


                                      — even echo doesn't need to have -n anymore.



                                      And for completeness sake: BSD's version of seq when -s '' specified doesn't produce new-line on its exit.






                                      share|improve this answer













                                      When using tr to get rid of trailing new-line it's worth realising that it deletes all occurrences of the characters given in its -d option. Thus you can get it a bit more slim:



                                      (seq 1 9; echo 0; seq 1 9) | tr -d 'n'


                                      — even echo doesn't need to have -n anymore.



                                      And for completeness sake: BSD's version of seq when -s '' specified doesn't produce new-line on its exit.







                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered Jan 4 at 4:08









                                      poigepoige

                                      4,1851646




                                      4,1851646






























                                          draft saved

                                          draft discarded




















































                                          Thanks for contributing an answer to Unix & Linux Stack Exchange!


                                          • 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%2funix.stackexchange.com%2fquestions%2f492315%2fhow-to-avoid-printing-a-newline-when-seq-completes%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

                                          To store a contact into the json file from server.js file using a class in NodeJS

                                          Redirect URL with Chrome Remote Debugging Android Devices

                                          Dieringhausen