Bash method for viewing beginning and end of file
On queue-based clusters the Queue of pending jobs is shown from a command, say showqueue
.
The command returns, in columns, a list of reasonable data like names, etc, but the columns/data don't really matter for the question.
I like using the utility watch
like watch showqueue
at times (with an alias of alias watch="watch "
to force alias expansion of my command to watch). There is valuable data (Running jobs), in the first few lines, then pending jobs, etc, and some valuable summaries at the end.
However, at times the output of showqueue goes off the screen (Unbelievable, I know)! Ideally, I'd like some way to be able to see the beginning and end of the file at the same time.
The best I have so far is: showqueue > file; head -n 20 file > file2; echo "..." >> file2 ; tail -n 20 file >> file2; cat file2
, and using watch
on an alias of that.
Does anyone know of anything a little more flexible or single-utility? My solution gets a little nastier with bash loops to make the "..." break multilined, it's not adaptive to resizing the terminal window at all, and I'm sure there's more that I missed.
Any suggestions?
bash text-processing
New contributor
add a comment |
On queue-based clusters the Queue of pending jobs is shown from a command, say showqueue
.
The command returns, in columns, a list of reasonable data like names, etc, but the columns/data don't really matter for the question.
I like using the utility watch
like watch showqueue
at times (with an alias of alias watch="watch "
to force alias expansion of my command to watch). There is valuable data (Running jobs), in the first few lines, then pending jobs, etc, and some valuable summaries at the end.
However, at times the output of showqueue goes off the screen (Unbelievable, I know)! Ideally, I'd like some way to be able to see the beginning and end of the file at the same time.
The best I have so far is: showqueue > file; head -n 20 file > file2; echo "..." >> file2 ; tail -n 20 file >> file2; cat file2
, and using watch
on an alias of that.
Does anyone know of anything a little more flexible or single-utility? My solution gets a little nastier with bash loops to make the "..." break multilined, it's not adaptive to resizing the terminal window at all, and I'm sure there's more that I missed.
Any suggestions?
bash text-processing
New contributor
Closed as duplicate, but the question only shares similarities (Mine is more about a command, I learned, and not files), and the answers here didn't show up there, but if you insist
– MadisonCooper
13 hours ago
2
Fair enough. I've reopened. Note that the answer that you have accepted will only work for large outputs as noted at my answer at Command to display first few and last few lines of a file (tryseq 30 | (head && tail)
for instance).
– Stéphane Chazelas
13 hours ago
2
I meant that answer. That Q&A has two answers of mine because another Q&A was merged with it (see question history)
– Stéphane Chazelas
13 hours ago
add a comment |
On queue-based clusters the Queue of pending jobs is shown from a command, say showqueue
.
The command returns, in columns, a list of reasonable data like names, etc, but the columns/data don't really matter for the question.
I like using the utility watch
like watch showqueue
at times (with an alias of alias watch="watch "
to force alias expansion of my command to watch). There is valuable data (Running jobs), in the first few lines, then pending jobs, etc, and some valuable summaries at the end.
However, at times the output of showqueue goes off the screen (Unbelievable, I know)! Ideally, I'd like some way to be able to see the beginning and end of the file at the same time.
The best I have so far is: showqueue > file; head -n 20 file > file2; echo "..." >> file2 ; tail -n 20 file >> file2; cat file2
, and using watch
on an alias of that.
Does anyone know of anything a little more flexible or single-utility? My solution gets a little nastier with bash loops to make the "..." break multilined, it's not adaptive to resizing the terminal window at all, and I'm sure there's more that I missed.
Any suggestions?
bash text-processing
New contributor
On queue-based clusters the Queue of pending jobs is shown from a command, say showqueue
.
The command returns, in columns, a list of reasonable data like names, etc, but the columns/data don't really matter for the question.
I like using the utility watch
like watch showqueue
at times (with an alias of alias watch="watch "
to force alias expansion of my command to watch). There is valuable data (Running jobs), in the first few lines, then pending jobs, etc, and some valuable summaries at the end.
However, at times the output of showqueue goes off the screen (Unbelievable, I know)! Ideally, I'd like some way to be able to see the beginning and end of the file at the same time.
The best I have so far is: showqueue > file; head -n 20 file > file2; echo "..." >> file2 ; tail -n 20 file >> file2; cat file2
, and using watch
on an alias of that.
Does anyone know of anything a little more flexible or single-utility? My solution gets a little nastier with bash loops to make the "..." break multilined, it's not adaptive to resizing the terminal window at all, and I'm sure there's more that I missed.
Any suggestions?
bash text-processing
bash text-processing
New contributor
New contributor
edited 14 hours ago
Rui F Ribeiro
41.8k1483142
41.8k1483142
New contributor
asked 14 hours ago
MadisonCooperMadisonCooper
433
433
New contributor
New contributor
Closed as duplicate, but the question only shares similarities (Mine is more about a command, I learned, and not files), and the answers here didn't show up there, but if you insist
– MadisonCooper
13 hours ago
2
Fair enough. I've reopened. Note that the answer that you have accepted will only work for large outputs as noted at my answer at Command to display first few and last few lines of a file (tryseq 30 | (head && tail)
for instance).
– Stéphane Chazelas
13 hours ago
2
I meant that answer. That Q&A has two answers of mine because another Q&A was merged with it (see question history)
– Stéphane Chazelas
13 hours ago
add a comment |
Closed as duplicate, but the question only shares similarities (Mine is more about a command, I learned, and not files), and the answers here didn't show up there, but if you insist
– MadisonCooper
13 hours ago
2
Fair enough. I've reopened. Note that the answer that you have accepted will only work for large outputs as noted at my answer at Command to display first few and last few lines of a file (tryseq 30 | (head && tail)
for instance).
– Stéphane Chazelas
13 hours ago
2
I meant that answer. That Q&A has two answers of mine because another Q&A was merged with it (see question history)
– Stéphane Chazelas
13 hours ago
Closed as duplicate, but the question only shares similarities (Mine is more about a command, I learned, and not files), and the answers here didn't show up there, but if you insist
– MadisonCooper
13 hours ago
Closed as duplicate, but the question only shares similarities (Mine is more about a command, I learned, and not files), and the answers here didn't show up there, but if you insist
– MadisonCooper
13 hours ago
2
2
Fair enough. I've reopened. Note that the answer that you have accepted will only work for large outputs as noted at my answer at Command to display first few and last few lines of a file (try
seq 30 | (head && tail)
for instance).– Stéphane Chazelas
13 hours ago
Fair enough. I've reopened. Note that the answer that you have accepted will only work for large outputs as noted at my answer at Command to display first few and last few lines of a file (try
seq 30 | (head && tail)
for instance).– Stéphane Chazelas
13 hours ago
2
2
I meant that answer. That Q&A has two answers of mine because another Q&A was merged with it (see question history)
– Stéphane Chazelas
13 hours ago
I meant that answer. That Q&A has two answers of mine because another Q&A was merged with it (see question history)
– Stéphane Chazelas
13 hours ago
add a comment |
4 Answers
4
active
oldest
votes
Are you looking to do something like the following? Shows output from both head and tail.
$ showqueue | (head && tail)
5
Some implementations ofhead
may read more than 10 lines and leave nothing fortail
to read. The utility is not supposed to do that and I believe that the GNU tools are well behave in this respect. Usehead; echo '...'; tail
to get the dots in there as well.
– Kusalananda♦
14 hours ago
Yeah, combined with @Kusalananda's comment it's much more succinct than my solution. I'll mark as correct for now! Thanks.
– MadisonCooper
14 hours ago
4
@Kusalananda, nope, on my system, GNU head (coreutils 8.26) reads blocks of 8192 bytes. It does try to seek back, but obviously can't in case of a pipe. Though anyway, is there really a requirement forhead
to not over-read? (same on Mac, it seems to read by blocks)
– ilkkachu
14 hours ago
2
@ilkkachu yeah, even as it stands the tail part is occasionally blank even on sufficiently long output (I know since I'm using head -n 35, and that's full), but fortunately it's just a convenience to watch and I can wait 3 seconds for a refresh if needed.
– MadisonCooper
14 hours ago
3
@Kusalananda, POSIX allows implementations to do that when the input is not seekable and most implementations do. Not doing it would mean reading one byte at a time which would be very inefficient (or put the data back onto the pipe where supported which would cause all sorts of different problems). The onlyhead
implementation I know that reads one byte at a time to avoid reading past the 10th newline is ksh93'shead
builtin.
– Stéphane Chazelas
13 hours ago
|
show 3 more comments
awk solution for an arbitrary number of lines shown from the head and the tail (change n=3
to set the amount):
$ seq 99999 | awk -v n=3 'NR <= n; NR > n { a[NR] = $0; delete a[NR-n]; }
END { print "..."; for (i = NR-n+1; i <= NR; i++) if (i in a) print a[i]; }'
1
2
3
...
99997
99998
99999
As it's written, the head and tail parts will not overlap, even if the input is shorter than 2*n
lines.
In some awk implementations, using for (x in a) print a[x];
in the END
part also works. But in general, it's not guaranteed to return the array entries in the correct order, and doesn't in e.g. mawk.
Ifm
is the number of lines in the file, andm < 2n
, that will print2n - m
empty lines. Also have look here ;-).for (x in a)
will iterate in order only in GNU awk; if you think that it works inmawk
too, test with > 10 values.
– mosvy
13 hours ago
@mosvy, oh, whoops, I forgot to re-check that after realizingx in a
wasn't right. Fixed now, thanks. There's also another awk answer in the question Stéphane linked to. I like the modulo trick, though!
– ilkkachu
13 hours ago
add a comment |
Using the same approach as you, using a temporary file, but doing it slightly shorter:
showqueue >/tmp/q.out; head -n 20 /tmp/q.out; echo '...'; tail -n 20 /tmp/q.out
This would not suffer from the same issues as discussed under another answer, but would possibly show the same lines twice if the output was shorter than 40 lines.
add a comment |
You can use simple awk script. Added circle buffer there n=3 is for last 3 lines
awk 'NR<=n {print $0} { A[NR%n]=$0 } END { for (i=1; i<=n; ++i) if (NR+i>2*n)print A[(NR+i)%n] }' n=3 < <( seq 10 )
After update its not simple anymore though,
New contributor
1
This would only show the first and last line. To show more than that, you would have to changeNR==1
toNR <= 10
(or something), and then collect lines into a (circular?) buffer that you later output in theEND
block.
– Kusalananda♦
14 hours ago
yes let me update
– Abdurrahim
14 hours ago
This will print some lines twice when then the number of lines is less than 2 * n.
– mosvy
13 hours ago
:) ok adding that as well now I am curious what you will find next :D
– Abdurrahim
2 hours ago
add a comment |
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
});
}
});
MadisonCooper is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f508818%2fbash-method-for-viewing-beginning-and-end-of-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Are you looking to do something like the following? Shows output from both head and tail.
$ showqueue | (head && tail)
5
Some implementations ofhead
may read more than 10 lines and leave nothing fortail
to read. The utility is not supposed to do that and I believe that the GNU tools are well behave in this respect. Usehead; echo '...'; tail
to get the dots in there as well.
– Kusalananda♦
14 hours ago
Yeah, combined with @Kusalananda's comment it's much more succinct than my solution. I'll mark as correct for now! Thanks.
– MadisonCooper
14 hours ago
4
@Kusalananda, nope, on my system, GNU head (coreutils 8.26) reads blocks of 8192 bytes. It does try to seek back, but obviously can't in case of a pipe. Though anyway, is there really a requirement forhead
to not over-read? (same on Mac, it seems to read by blocks)
– ilkkachu
14 hours ago
2
@ilkkachu yeah, even as it stands the tail part is occasionally blank even on sufficiently long output (I know since I'm using head -n 35, and that's full), but fortunately it's just a convenience to watch and I can wait 3 seconds for a refresh if needed.
– MadisonCooper
14 hours ago
3
@Kusalananda, POSIX allows implementations to do that when the input is not seekable and most implementations do. Not doing it would mean reading one byte at a time which would be very inefficient (or put the data back onto the pipe where supported which would cause all sorts of different problems). The onlyhead
implementation I know that reads one byte at a time to avoid reading past the 10th newline is ksh93'shead
builtin.
– Stéphane Chazelas
13 hours ago
|
show 3 more comments
Are you looking to do something like the following? Shows output from both head and tail.
$ showqueue | (head && tail)
5
Some implementations ofhead
may read more than 10 lines and leave nothing fortail
to read. The utility is not supposed to do that and I believe that the GNU tools are well behave in this respect. Usehead; echo '...'; tail
to get the dots in there as well.
– Kusalananda♦
14 hours ago
Yeah, combined with @Kusalananda's comment it's much more succinct than my solution. I'll mark as correct for now! Thanks.
– MadisonCooper
14 hours ago
4
@Kusalananda, nope, on my system, GNU head (coreutils 8.26) reads blocks of 8192 bytes. It does try to seek back, but obviously can't in case of a pipe. Though anyway, is there really a requirement forhead
to not over-read? (same on Mac, it seems to read by blocks)
– ilkkachu
14 hours ago
2
@ilkkachu yeah, even as it stands the tail part is occasionally blank even on sufficiently long output (I know since I'm using head -n 35, and that's full), but fortunately it's just a convenience to watch and I can wait 3 seconds for a refresh if needed.
– MadisonCooper
14 hours ago
3
@Kusalananda, POSIX allows implementations to do that when the input is not seekable and most implementations do. Not doing it would mean reading one byte at a time which would be very inefficient (or put the data back onto the pipe where supported which would cause all sorts of different problems). The onlyhead
implementation I know that reads one byte at a time to avoid reading past the 10th newline is ksh93'shead
builtin.
– Stéphane Chazelas
13 hours ago
|
show 3 more comments
Are you looking to do something like the following? Shows output from both head and tail.
$ showqueue | (head && tail)
Are you looking to do something like the following? Shows output from both head and tail.
$ showqueue | (head && tail)
answered 14 hours ago
Timothy PulliamTimothy Pulliam
1,375925
1,375925
5
Some implementations ofhead
may read more than 10 lines and leave nothing fortail
to read. The utility is not supposed to do that and I believe that the GNU tools are well behave in this respect. Usehead; echo '...'; tail
to get the dots in there as well.
– Kusalananda♦
14 hours ago
Yeah, combined with @Kusalananda's comment it's much more succinct than my solution. I'll mark as correct for now! Thanks.
– MadisonCooper
14 hours ago
4
@Kusalananda, nope, on my system, GNU head (coreutils 8.26) reads blocks of 8192 bytes. It does try to seek back, but obviously can't in case of a pipe. Though anyway, is there really a requirement forhead
to not over-read? (same on Mac, it seems to read by blocks)
– ilkkachu
14 hours ago
2
@ilkkachu yeah, even as it stands the tail part is occasionally blank even on sufficiently long output (I know since I'm using head -n 35, and that's full), but fortunately it's just a convenience to watch and I can wait 3 seconds for a refresh if needed.
– MadisonCooper
14 hours ago
3
@Kusalananda, POSIX allows implementations to do that when the input is not seekable and most implementations do. Not doing it would mean reading one byte at a time which would be very inefficient (or put the data back onto the pipe where supported which would cause all sorts of different problems). The onlyhead
implementation I know that reads one byte at a time to avoid reading past the 10th newline is ksh93'shead
builtin.
– Stéphane Chazelas
13 hours ago
|
show 3 more comments
5
Some implementations ofhead
may read more than 10 lines and leave nothing fortail
to read. The utility is not supposed to do that and I believe that the GNU tools are well behave in this respect. Usehead; echo '...'; tail
to get the dots in there as well.
– Kusalananda♦
14 hours ago
Yeah, combined with @Kusalananda's comment it's much more succinct than my solution. I'll mark as correct for now! Thanks.
– MadisonCooper
14 hours ago
4
@Kusalananda, nope, on my system, GNU head (coreutils 8.26) reads blocks of 8192 bytes. It does try to seek back, but obviously can't in case of a pipe. Though anyway, is there really a requirement forhead
to not over-read? (same on Mac, it seems to read by blocks)
– ilkkachu
14 hours ago
2
@ilkkachu yeah, even as it stands the tail part is occasionally blank even on sufficiently long output (I know since I'm using head -n 35, and that's full), but fortunately it's just a convenience to watch and I can wait 3 seconds for a refresh if needed.
– MadisonCooper
14 hours ago
3
@Kusalananda, POSIX allows implementations to do that when the input is not seekable and most implementations do. Not doing it would mean reading one byte at a time which would be very inefficient (or put the data back onto the pipe where supported which would cause all sorts of different problems). The onlyhead
implementation I know that reads one byte at a time to avoid reading past the 10th newline is ksh93'shead
builtin.
– Stéphane Chazelas
13 hours ago
5
5
Some implementations of
head
may read more than 10 lines and leave nothing for tail
to read. The utility is not supposed to do that and I believe that the GNU tools are well behave in this respect. Use head; echo '...'; tail
to get the dots in there as well.– Kusalananda♦
14 hours ago
Some implementations of
head
may read more than 10 lines and leave nothing for tail
to read. The utility is not supposed to do that and I believe that the GNU tools are well behave in this respect. Use head; echo '...'; tail
to get the dots in there as well.– Kusalananda♦
14 hours ago
Yeah, combined with @Kusalananda's comment it's much more succinct than my solution. I'll mark as correct for now! Thanks.
– MadisonCooper
14 hours ago
Yeah, combined with @Kusalananda's comment it's much more succinct than my solution. I'll mark as correct for now! Thanks.
– MadisonCooper
14 hours ago
4
4
@Kusalananda, nope, on my system, GNU head (coreutils 8.26) reads blocks of 8192 bytes. It does try to seek back, but obviously can't in case of a pipe. Though anyway, is there really a requirement for
head
to not over-read? (same on Mac, it seems to read by blocks)– ilkkachu
14 hours ago
@Kusalananda, nope, on my system, GNU head (coreutils 8.26) reads blocks of 8192 bytes. It does try to seek back, but obviously can't in case of a pipe. Though anyway, is there really a requirement for
head
to not over-read? (same on Mac, it seems to read by blocks)– ilkkachu
14 hours ago
2
2
@ilkkachu yeah, even as it stands the tail part is occasionally blank even on sufficiently long output (I know since I'm using head -n 35, and that's full), but fortunately it's just a convenience to watch and I can wait 3 seconds for a refresh if needed.
– MadisonCooper
14 hours ago
@ilkkachu yeah, even as it stands the tail part is occasionally blank even on sufficiently long output (I know since I'm using head -n 35, and that's full), but fortunately it's just a convenience to watch and I can wait 3 seconds for a refresh if needed.
– MadisonCooper
14 hours ago
3
3
@Kusalananda, POSIX allows implementations to do that when the input is not seekable and most implementations do. Not doing it would mean reading one byte at a time which would be very inefficient (or put the data back onto the pipe where supported which would cause all sorts of different problems). The only
head
implementation I know that reads one byte at a time to avoid reading past the 10th newline is ksh93's head
builtin.– Stéphane Chazelas
13 hours ago
@Kusalananda, POSIX allows implementations to do that when the input is not seekable and most implementations do. Not doing it would mean reading one byte at a time which would be very inefficient (or put the data back onto the pipe where supported which would cause all sorts of different problems). The only
head
implementation I know that reads one byte at a time to avoid reading past the 10th newline is ksh93's head
builtin.– Stéphane Chazelas
13 hours ago
|
show 3 more comments
awk solution for an arbitrary number of lines shown from the head and the tail (change n=3
to set the amount):
$ seq 99999 | awk -v n=3 'NR <= n; NR > n { a[NR] = $0; delete a[NR-n]; }
END { print "..."; for (i = NR-n+1; i <= NR; i++) if (i in a) print a[i]; }'
1
2
3
...
99997
99998
99999
As it's written, the head and tail parts will not overlap, even if the input is shorter than 2*n
lines.
In some awk implementations, using for (x in a) print a[x];
in the END
part also works. But in general, it's not guaranteed to return the array entries in the correct order, and doesn't in e.g. mawk.
Ifm
is the number of lines in the file, andm < 2n
, that will print2n - m
empty lines. Also have look here ;-).for (x in a)
will iterate in order only in GNU awk; if you think that it works inmawk
too, test with > 10 values.
– mosvy
13 hours ago
@mosvy, oh, whoops, I forgot to re-check that after realizingx in a
wasn't right. Fixed now, thanks. There's also another awk answer in the question Stéphane linked to. I like the modulo trick, though!
– ilkkachu
13 hours ago
add a comment |
awk solution for an arbitrary number of lines shown from the head and the tail (change n=3
to set the amount):
$ seq 99999 | awk -v n=3 'NR <= n; NR > n { a[NR] = $0; delete a[NR-n]; }
END { print "..."; for (i = NR-n+1; i <= NR; i++) if (i in a) print a[i]; }'
1
2
3
...
99997
99998
99999
As it's written, the head and tail parts will not overlap, even if the input is shorter than 2*n
lines.
In some awk implementations, using for (x in a) print a[x];
in the END
part also works. But in general, it's not guaranteed to return the array entries in the correct order, and doesn't in e.g. mawk.
Ifm
is the number of lines in the file, andm < 2n
, that will print2n - m
empty lines. Also have look here ;-).for (x in a)
will iterate in order only in GNU awk; if you think that it works inmawk
too, test with > 10 values.
– mosvy
13 hours ago
@mosvy, oh, whoops, I forgot to re-check that after realizingx in a
wasn't right. Fixed now, thanks. There's also another awk answer in the question Stéphane linked to. I like the modulo trick, though!
– ilkkachu
13 hours ago
add a comment |
awk solution for an arbitrary number of lines shown from the head and the tail (change n=3
to set the amount):
$ seq 99999 | awk -v n=3 'NR <= n; NR > n { a[NR] = $0; delete a[NR-n]; }
END { print "..."; for (i = NR-n+1; i <= NR; i++) if (i in a) print a[i]; }'
1
2
3
...
99997
99998
99999
As it's written, the head and tail parts will not overlap, even if the input is shorter than 2*n
lines.
In some awk implementations, using for (x in a) print a[x];
in the END
part also works. But in general, it's not guaranteed to return the array entries in the correct order, and doesn't in e.g. mawk.
awk solution for an arbitrary number of lines shown from the head and the tail (change n=3
to set the amount):
$ seq 99999 | awk -v n=3 'NR <= n; NR > n { a[NR] = $0; delete a[NR-n]; }
END { print "..."; for (i = NR-n+1; i <= NR; i++) if (i in a) print a[i]; }'
1
2
3
...
99997
99998
99999
As it's written, the head and tail parts will not overlap, even if the input is shorter than 2*n
lines.
In some awk implementations, using for (x in a) print a[x];
in the END
part also works. But in general, it's not guaranteed to return the array entries in the correct order, and doesn't in e.g. mawk.
edited 13 hours ago
answered 14 hours ago
ilkkachuilkkachu
62.7k10103180
62.7k10103180
Ifm
is the number of lines in the file, andm < 2n
, that will print2n - m
empty lines. Also have look here ;-).for (x in a)
will iterate in order only in GNU awk; if you think that it works inmawk
too, test with > 10 values.
– mosvy
13 hours ago
@mosvy, oh, whoops, I forgot to re-check that after realizingx in a
wasn't right. Fixed now, thanks. There's also another awk answer in the question Stéphane linked to. I like the modulo trick, though!
– ilkkachu
13 hours ago
add a comment |
Ifm
is the number of lines in the file, andm < 2n
, that will print2n - m
empty lines. Also have look here ;-).for (x in a)
will iterate in order only in GNU awk; if you think that it works inmawk
too, test with > 10 values.
– mosvy
13 hours ago
@mosvy, oh, whoops, I forgot to re-check that after realizingx in a
wasn't right. Fixed now, thanks. There's also another awk answer in the question Stéphane linked to. I like the modulo trick, though!
– ilkkachu
13 hours ago
If
m
is the number of lines in the file, and m < 2n
, that will print 2n - m
empty lines. Also have look here ;-). for (x in a)
will iterate in order only in GNU awk; if you think that it works in mawk
too, test with > 10 values.– mosvy
13 hours ago
If
m
is the number of lines in the file, and m < 2n
, that will print 2n - m
empty lines. Also have look here ;-). for (x in a)
will iterate in order only in GNU awk; if you think that it works in mawk
too, test with > 10 values.– mosvy
13 hours ago
@mosvy, oh, whoops, I forgot to re-check that after realizing
x in a
wasn't right. Fixed now, thanks. There's also another awk answer in the question Stéphane linked to. I like the modulo trick, though!– ilkkachu
13 hours ago
@mosvy, oh, whoops, I forgot to re-check that after realizing
x in a
wasn't right. Fixed now, thanks. There's also another awk answer in the question Stéphane linked to. I like the modulo trick, though!– ilkkachu
13 hours ago
add a comment |
Using the same approach as you, using a temporary file, but doing it slightly shorter:
showqueue >/tmp/q.out; head -n 20 /tmp/q.out; echo '...'; tail -n 20 /tmp/q.out
This would not suffer from the same issues as discussed under another answer, but would possibly show the same lines twice if the output was shorter than 40 lines.
add a comment |
Using the same approach as you, using a temporary file, but doing it slightly shorter:
showqueue >/tmp/q.out; head -n 20 /tmp/q.out; echo '...'; tail -n 20 /tmp/q.out
This would not suffer from the same issues as discussed under another answer, but would possibly show the same lines twice if the output was shorter than 40 lines.
add a comment |
Using the same approach as you, using a temporary file, but doing it slightly shorter:
showqueue >/tmp/q.out; head -n 20 /tmp/q.out; echo '...'; tail -n 20 /tmp/q.out
This would not suffer from the same issues as discussed under another answer, but would possibly show the same lines twice if the output was shorter than 40 lines.
Using the same approach as you, using a temporary file, but doing it slightly shorter:
showqueue >/tmp/q.out; head -n 20 /tmp/q.out; echo '...'; tail -n 20 /tmp/q.out
This would not suffer from the same issues as discussed under another answer, but would possibly show the same lines twice if the output was shorter than 40 lines.
edited 13 hours ago
answered 14 hours ago
Kusalananda♦Kusalananda
138k17258426
138k17258426
add a comment |
add a comment |
You can use simple awk script. Added circle buffer there n=3 is for last 3 lines
awk 'NR<=n {print $0} { A[NR%n]=$0 } END { for (i=1; i<=n; ++i) if (NR+i>2*n)print A[(NR+i)%n] }' n=3 < <( seq 10 )
After update its not simple anymore though,
New contributor
1
This would only show the first and last line. To show more than that, you would have to changeNR==1
toNR <= 10
(or something), and then collect lines into a (circular?) buffer that you later output in theEND
block.
– Kusalananda♦
14 hours ago
yes let me update
– Abdurrahim
14 hours ago
This will print some lines twice when then the number of lines is less than 2 * n.
– mosvy
13 hours ago
:) ok adding that as well now I am curious what you will find next :D
– Abdurrahim
2 hours ago
add a comment |
You can use simple awk script. Added circle buffer there n=3 is for last 3 lines
awk 'NR<=n {print $0} { A[NR%n]=$0 } END { for (i=1; i<=n; ++i) if (NR+i>2*n)print A[(NR+i)%n] }' n=3 < <( seq 10 )
After update its not simple anymore though,
New contributor
1
This would only show the first and last line. To show more than that, you would have to changeNR==1
toNR <= 10
(or something), and then collect lines into a (circular?) buffer that you later output in theEND
block.
– Kusalananda♦
14 hours ago
yes let me update
– Abdurrahim
14 hours ago
This will print some lines twice when then the number of lines is less than 2 * n.
– mosvy
13 hours ago
:) ok adding that as well now I am curious what you will find next :D
– Abdurrahim
2 hours ago
add a comment |
You can use simple awk script. Added circle buffer there n=3 is for last 3 lines
awk 'NR<=n {print $0} { A[NR%n]=$0 } END { for (i=1; i<=n; ++i) if (NR+i>2*n)print A[(NR+i)%n] }' n=3 < <( seq 10 )
After update its not simple anymore though,
New contributor
You can use simple awk script. Added circle buffer there n=3 is for last 3 lines
awk 'NR<=n {print $0} { A[NR%n]=$0 } END { for (i=1; i<=n; ++i) if (NR+i>2*n)print A[(NR+i)%n] }' n=3 < <( seq 10 )
After update its not simple anymore though,
New contributor
edited 2 hours ago
New contributor
answered 14 hours ago
AbdurrahimAbdurrahim
1012
1012
New contributor
New contributor
1
This would only show the first and last line. To show more than that, you would have to changeNR==1
toNR <= 10
(or something), and then collect lines into a (circular?) buffer that you later output in theEND
block.
– Kusalananda♦
14 hours ago
yes let me update
– Abdurrahim
14 hours ago
This will print some lines twice when then the number of lines is less than 2 * n.
– mosvy
13 hours ago
:) ok adding that as well now I am curious what you will find next :D
– Abdurrahim
2 hours ago
add a comment |
1
This would only show the first and last line. To show more than that, you would have to changeNR==1
toNR <= 10
(or something), and then collect lines into a (circular?) buffer that you later output in theEND
block.
– Kusalananda♦
14 hours ago
yes let me update
– Abdurrahim
14 hours ago
This will print some lines twice when then the number of lines is less than 2 * n.
– mosvy
13 hours ago
:) ok adding that as well now I am curious what you will find next :D
– Abdurrahim
2 hours ago
1
1
This would only show the first and last line. To show more than that, you would have to change
NR==1
to NR <= 10
(or something), and then collect lines into a (circular?) buffer that you later output in the END
block.– Kusalananda♦
14 hours ago
This would only show the first and last line. To show more than that, you would have to change
NR==1
to NR <= 10
(or something), and then collect lines into a (circular?) buffer that you later output in the END
block.– Kusalananda♦
14 hours ago
yes let me update
– Abdurrahim
14 hours ago
yes let me update
– Abdurrahim
14 hours ago
This will print some lines twice when then the number of lines is less than 2 * n.
– mosvy
13 hours ago
This will print some lines twice when then the number of lines is less than 2 * n.
– mosvy
13 hours ago
:) ok adding that as well now I am curious what you will find next :D
– Abdurrahim
2 hours ago
:) ok adding that as well now I am curious what you will find next :D
– Abdurrahim
2 hours ago
add a comment |
MadisonCooper is a new contributor. Be nice, and check out our Code of Conduct.
MadisonCooper is a new contributor. Be nice, and check out our Code of Conduct.
MadisonCooper is a new contributor. Be nice, and check out our Code of Conduct.
MadisonCooper is a new contributor. Be nice, and check out our Code of Conduct.
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f508818%2fbash-method-for-viewing-beginning-and-end-of-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
Closed as duplicate, but the question only shares similarities (Mine is more about a command, I learned, and not files), and the answers here didn't show up there, but if you insist
– MadisonCooper
13 hours ago
2
Fair enough. I've reopened. Note that the answer that you have accepted will only work for large outputs as noted at my answer at Command to display first few and last few lines of a file (try
seq 30 | (head && tail)
for instance).– Stéphane Chazelas
13 hours ago
2
I meant that answer. That Q&A has two answers of mine because another Q&A was merged with it (see question history)
– Stéphane Chazelas
13 hours ago