Differences between revisions 23 and 40 (spanning 17 versions)
Revision 23 as of 2011-03-01 15:32:39
Size: 1803
Editor: sn18
Comment:
Revision 40 as of 2025-04-20 12:55:53
Size: 2101
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
The dirty (but not quick) way would be: One dirty (but not quick) way is:
Line 5: Line 5:
{{{
    sed -n ${n}p "$file"
{{{#!highlight bash
sed -n "${n}p" < "$file"
Line 8: Line 8:
but this reads the whole input file, even if you only wanted the third line.
Line 10: Line 9:
This one avoids that problem: But this reads the entire file even if only the third line is desired, which can be avoided by using the `q` command to quit on line `$n`, and deleting all other lines with the `d` command:
Line 12: Line 11:
{{{
    sed -n "$n{p;q;}" "$file"
{{{#!highlight bash
sed "${n}q;d" < "$file"
Line 15: Line 14:
At line $n the command "p" is run, printing it, with a "q" afterwards: quit the program.
Line 17: Line 15:
Another way, more obvious to some, is to grab the last line from a listing of the first ''n'' lines: Or
Line 19: Line 17:
{{{
   head -n $n $file | tail -n 1
{{{#!highlight bash
sed "$n!d;q" < "$file"
Line 22: Line 20:

Which appears to be faster with all of GNU, busybox and ast-open sed implementations.

Another method is to grab lines starting at `n`, then get the first line of that.

{{{#!highlight bash
<"$file" tail -n "+$n" | head -n 1
}}}

As that uses more specialized tools, that's generally generally significantly faster.
Line 24: Line 33:
{{{
   awk "NR==$n{print;exit}" file
{{{#!highlight bash
awk -v n="$n" 'NR==n{print;exit}' < "$file"
Line 27: Line 36:
If you want more than one line, it's pretty easy to adapt any of the previous methods:
Line 29: Line 37:
{{{
   x=3 y=4
   sed -n "$x,${y}p;${y}q;" "$file" # Print lines $x to $y; quit after $y.
   head -n $y "$file" | tail -n $((y - x + 1)) # Same
   head -n $y "$file" | tail -n +$x # If your tail supports it
   awk "NR>=$x{print} NR==$y{exit}" "$file" # Same
If more than one line is needed, it's easy to adapt any of the previous methods:

{{{#!highlight bash
x=3 y=4
sed "$x,$y!d;${y}q" < "$file" # Print lines $x to $y; quit after $y.
tail -n "+$x" < "$file" | head -n "$(( y - x + 1 ))" # Same, generally faster
awk -v x="$x" -v y="$y" 'NR>=x; NR==y{exit}' < "$file" # Same, generally slower
Line 36: Line 45:
In Bash 4, this can also be done with mapfile builtin:
Line 38: Line 46:
{{{
   mapfile -ts $((n-1)) -n 1
   echo "$MAPFILE"
Or a counter with a simple `read` loop, though that's going to be orders of magnitude slower for any input with more than a few hundred lines.

{{{#!highlight bash
# Bash/ksh/zsh
{
    m=0
    while ((m++ < x - 1)) && read -r _; do
        :
    done

    head -n "$((y - x + 1))"
} < "$file"
Line 42: Line 59:
By changing the value of argument for -n, you can get more than one line in the array MAPFILE.
Line 44: Line 60:
=== Note ===
In most cases, you should sanitize your variable n to be sure, that it's not containing any of non-digits, before feeding it to sed or awk. You can do it with such simple code:
To read into a variable, it is preferable to use `read` or `mapfile` aka `readarray` rather than an external utility. More than one line can be read into the given array variable or the default array `MAPFILE` by adjusting the argument to mapfile's -n option:
Line 47: Line 62:
{{{
   # Bash
   n=${n//[!0-9]/}
{{{#!highlight bash
# Bash4
{
  mapfile -s "$((x - 1))" -n "$((y - x + 1))" lines
  printf %s "${lines[@]}"
} < "$file"
}}}
Line 51: Line 70:
   # POSIX
   n=$(printf "%s" "$n"|tr -cd '0-9')
}}}
 . One can argue that an `n` value of `Five brown horses with 3 feet and 9 little piggies.` should yield an error rather than silently behave as though it was really `39`. If you want to code safe, quote your expansions and be done with it. --[[Lhunath]]
=== See Also ===
 * [[BashFAQ/001]]
 * http://wiki.bash-hackers.org/commands/builtin/mapfile

How can I print the n'th line of a file?

One dirty (but not quick) way is:

   1 sed -n "${n}p" < "$file"

But this reads the entire file even if only the third line is desired, which can be avoided by using the q command to quit on line $n, and deleting all other lines with the d command:

   1 sed "${n}q;d" < "$file"

Or

   1 sed "$n!d;q" < "$file"

Which appears to be faster with all of GNU, busybox and ast-open sed implementations.

Another method is to grab lines starting at n, then get the first line of that.

   1 <"$file" tail -n "+$n" | head -n 1

As that uses more specialized tools, that's generally generally significantly faster.

Another approach, using AWK:

   1 awk -v n="$n" 'NR==n{print;exit}' < "$file"

If more than one line is needed, it's easy to adapt any of the previous methods:

   1 x=3 y=4
   2 sed "$x,$y!d;${y}q" < "$file"                          # Print lines $x to $y; quit after $y.
   3 tail -n "+$x" < "$file" | head -n "$(( y - x + 1 ))"   # Same, generally faster
   4 awk -v x="$x" -v y="$y" 'NR>=x; NR==y{exit}' < "$file" # Same, generally slower

Or a counter with a simple read loop, though that's going to be orders of magnitude slower for any input with more than a few hundred lines.

   1 # Bash/ksh/zsh
   2 {
   3     m=0
   4     while ((m++ < x - 1)) && read -r _; do
   5         :
   6     done
   7 
   8     head -n "$((y - x + 1))"
   9 } < "$file"

To read into a variable, it is preferable to use read or mapfile aka readarray rather than an external utility. More than one line can be read into the given array variable or the default array MAPFILE by adjusting the argument to mapfile's -n option:

   1 # Bash4
   2 {
   3   mapfile -s "$((x - 1))" -n "$((y - x + 1))" lines
   4   printf %s "${lines[@]}"
   5 } < "$file"

See Also


CategoryShell

BashFAQ/011 (last edited 2025-04-20 12:55:53 by StephaneChazelas)