sort but keep header line at the top

You can keep the header at the top like this with bash:

command | (read -r; printf "%s\n" "$REPLY"; sort) 

Or do it with perl:

command | perl -e 'print scalar (<>); print sort { ... } <>' 

I found a nice awk version that works nicely in scripts:

awk 'NR == 1; NR > 1 {print $0 | "sort -n"}' 

The pee command from moreutils is designed for tasks like this.

Example:

To keep one header line, and sort the second (numeric) column in stdin:

<your command> | pee 'head -n 1' 'tail -n +2 | sort -k 2,2 -n' 

Explanation:

pee : pipe stdin to one or more commands and concatenate the results.

head -n 1 : Print the first line of stdin.

tail -n +2 : Print the second and following lines from stdin.

sort -k 2,2 -n : Numerically sort by the second column.

Test:

printf "header\na 1\nc 3\nb 2\n" | pee 'head -n 1' 'tail -n +2 | sort -k 2,2 -n' 

gives

header a 1 b 2 c 3 

Hackish but effective: prepend 0 to all header lines and 1 to all other lines before sorting. Strip the prefix after sorting.

… | awk '{print (NR <= 2 ? "0 " : "1 ") $0}' | sort -k 1 -k… | cut -b 3- 

Here's some magic perl line noise that you can pipe your output through to sort everything but keep the first line at the top: perl -e 'print scalar <>, sort <>;'

I tried the command | {head -1; sort; } solution and can confirm that it really screws things up--head reads in multiple lines from the pipe, then outputs just the first one. So the rest of the output, that head did not read, is passed to sort--NOT the rest of the output starting from line 2!

The result is that you are missing lines (and one partial line!) that were in the beginning of your command output (except you still have the first line) - a fact that is easy to confirm by adding a pipe to wc at the end of the above pipeline - but that is extraordinarily difficult to trace down if you don't know this! I spent at least 20 minutes trying to work out why I had a partial line (first 100 bytes or so cut off) in my output before solving it.

What I ended up doing, which worked beautifully and didn't require running the command twice, was:

myfile=$(mktemp) whatever command you want to run > $myfile head -1 $myfile sed 1d $myfile | sort rm $myfile 

If you need to put the output into a file, you can modify this to:

myfile=$(mktemp) whatever command you want to run > $myfile head -1 $myfile > outputfile sed 1d $myfile | sort >> outputfile rm $myfile 

I think this is easiest.

ps -ef | ( head -n 1 ; sort ) 

or this which is possibly faster as it does not create a sub shell

ps -ef | { head -n 1 ; sort ; } 

Other cool uses

shuffle lines after header row

cat file.txt | ( head -n 1 ; shuf ) 

reverse lines after header row

cat file.txt | ( head -n 1 ; tac ) 

Simple and straightforward!

<command> | head -n 1; <command> | sed 1d | sort <....> 

• sed nd ---> 'n' specifies line no., and 'd' stands for delete.

I came here looking for a solution for the command w. This command shows details of who is logged in and what they are doing.

To show the results sorted, but with the headers kept at the top (there are 2 lines of headers), I settled on:

w | head -n 2; w | tail -n +3 | sort 

Obviously this runs the command w twice and therefore may not be suitable for all situations. However, to its advantage it is substantially easier to remember.

Note that the tail -n +3 means 'show all lines from the 3rd onwards' (see man tail for details).

Expanding on @Mikel's answer, here is a version of the body() function that adds a few features:

1. It detects if there is input coming in on a pipe, and if not prints out usage information to STDERR.

2. If no command is given, it uses sort as the default.

3. If the first parameter is a number, it uses that number as the number of header lines (default 1)

In testing, it works on Linux bash and macOS zsh

I made a gist at github: https://gist.github.com/alanhoyle/7ec6bd445a790b62567d8b1ff6941c66

Thus:

body() { local HEADER_LINES=1 local COMMAND="sort" if [ -t 0 ]; then >&2 echo "ERROR: body requires piped input!" >&2 echo "body: prints the header from a STDIN and sends the 'body' to another command for" >&2 echo " additional processing. Useful for sort/grep when you want to keep headers" >&2 echo "USAGE: COMMAND | body [ N ] [ COMMAND_TO_PROCESS_OUTPUT ]" >&2 echo " if the first parameter N is a whole number, it prints that number of lines" >&2 echo " before proceeding [ default: skip $HEADER_LINES ]" >&2 echo " if the [ COMMAND_TO PROCESS_OUTPUT ] is omitted, '$COMMAND' is used" return 1 fi local re='^[0-9]+$' if [[ $1 =~ $re ]] ; then HEADER_LINES=$1 shift >&2 echo "body: skipping $HEADER_LINES" fi local THIS_COMMAND=$@ if [ -z "$THIS_COMMAND" ] ; then >&2 echo "body: running default $COMMAND" fi for line in $(eval echo "{1..$HEADER_LINES}") do IFS= read -r header printf '%s\n' "$header" done if [ -z "$THIS_COMMAND" ] ; then ( $COMMAND ) else "$@" fi } 

Example:

$ body ERROR: body requires piped input! body: prints the header from a STDIN and sends the 'body' to another command for additional processing. Useful for sort/grep when you want to keep headers USAGE: COMMAND | body [ N ] [ COMMAND_TO_PROCESS_OUTPUT ] if the first parameter N is a whole number, it prints that number of lines before proceeding [ default: skip 1 ] if the [ COMMAND_TO PROCESS_OUTPUT ] is omitted, 'sort' is used $ echo -e "header\n30\n33\n20" header 30 33 20 $ echo -e "header\n30\n33\n20" | body body: running sort by default header 20 30 33 $ echo -e "header\n30\n33\n20" | body grep 0 header 30 20 $ echo -e "header\n30\n33\n20" | body 2 body: skipping 2 body: running sort by default header 30 20 33 

Basically, you need something that reads one line and only one line from the input and outputs it and then leave the rest of the input to sort.

There are quite a few utilities that can read one line and print it:

• head -n 1
• sed q
• awk '{print; exit}'

But most implementations of those read their input in chunks, and will generally end up reading more than one line. On seekable input, they're able to rewind upon exit to just after the first line, but they can't do that on pipes or other non-seekable input.

You need an utility that give you a guarantee they don't read past the end of the first line. The options are:

• line: that used to be a standard utility but was obsoleted by POSIX on the ground that it was redundant with the read builtin of sh. That read lines one byte at a time, and output it. It was always outputting a line, even when there was none or a non-delimited one on input.
• sed -u q: some sed implementations support a -u option for unbuffered and some of those that support it, with it also read their input one byte at a time. You also need a sed implementation that doesn't read one line in advance when the $ address is not used. Which probably doesn't leave many implementations besides GNU sed. GNU sed also outputs a full line if the input only had a non-delimited line.
• IFS= read -r line: that reads up to one line and is guaranteed not read past the end of the line. Except for zsh's read builtin, it can't cope with NUL bytes. It doesn't print the line it has read, but you can use printf for that. With zsh, read -re reads the line and echoes it; it adds a newline character if missing on input.

So your best bet in sh-like shells would be:

sort_body() ( if IFS= read -r line; then printf '%s\n' "$line" && exec sort "$@" else # no input or only a non-delimited header line printf %s "$line" # no point in running sort as there's no input left fi ) 

Then:

cmd | sort_body -nk1,1 .. <file sort_body -u 

(not sort_body -u file, the thing to sort has to be passed on sort_body's stdin).

If those are CSVs or TSVs (or more see manual), that sounds like a job for mlr (miller).

Like with a file looking like:

$ cat /usr/share/distro-info/debian.csv version,codename,series,created,release,eol,eol-lts,eol-elts 1.1,Buzz,buzz,1993-08-16,1996-06-17,1997-06-05 1.2,Rex,rex,1996-06-17,1996-12-12,1998-06-05 1.3,Bo,bo,1996-12-12,1997-06-05,1999-03-09 2.0,Hamm,hamm,1997-06-05,1998-07-24,2000-03-09 2.1,Slink,slink,1998-07-24,1999-03-09,2000-10-30 2.2,Potato,potato,1999-03-09,2000-08-15,2003-07-30 [...] 

$ mlr --ragged --csv cut -f codename,created then sort -f codename /usr/share/distro-info/debian.csv codename,created Bo,1996-12-12 Bookworm,2021-08-14 Bullseye,2019-07-06 Buster,2017-06-17 Buzz,1993-08-16 Etch,2005-06-06 [...] 

That is, the order is not only preserved, but the field names in there can also be used in the cut or sort specifications.

Using Raku (formerly known as Perl_6)

~$ raku -e '.put for "\x0061".."\x07A";' | raku -e 'put get; .put for lines.sort.reverse.head(10);' #OR ~$ raku -e '.put for "\x0061".."\x07A";' | raku -e 'put lines[0]; .put for lines[1..*].sort.reverse.head(10);' 

Sample Input: English alphabet, one letter per line

Sample Output (truncated to first 10 lines via .head(10):

a z y x w v u t s r q 

Answering this to complement Perl answers already posted. The put get call 1. 'gets' a single line and out-'puts' it, then 2. advances the read cursor so the first line isn't read again (e.g. by lines). If you need to read a 2-line header (for example), use (put get) xx 2.

When sorting a file, sometimes you want to filter a little first--an example is removing blank lines. That's easy with Raku, simply interpose a call to .map({$_ if .chars}) after the call to lines (and before the call to sort).

A nice advantage of Raku is built-in, high-level support for Unicode. A Cyrillic alphabet equivalent of the Raku code at top is as follows:

~$ raku -e '.put for "\x0430".."\x044F";' | raku -e 'put get; .put for lines.sort.reverse.head(10);' 

OR, taking input off the command line:

~$ raku -e '.put for "\x0430".."\x044F";' > Cyrillic.txt ~$ raku -e 'put lines[0]; .put for lines[1..*].sort.reverse.head(10);' Cyrillic.txt 

Sample Output (either Cyrillic example above):

а я ю э ь ы ъ щ ш ч ц 

See URLs below for further discussion on the Raku/Perl6 mailing list regarding how to translate Perl(5) file-input idioms into Raku.

https://www.nntp.perl.org/group/perl.perl6.users/2018/11/msg6295.html
https://www.nntp.perl.org/group/perl.perl6.users/2019/07/msg6825.html

https://raku.org

command | head -1; command | tail -n +2 | sort