Activity for alx
| Type | On... | Excerpt | Status | Date |
|---|---|---|---|---|
| Comment | Post #289936 |
```sh
$ dpkg -l | grep -e moreutils -e fd-find
ii fd-find 8.7.0-3+b1 amd64 Simple, fast and user-friendly alternative to find
ii moreutils 0.67-1 amd64 addition... (more) |
— | over 1 year ago |
| Comment | Post #289936 |
```sh
$ find
.
./l1
./l1/l2
./l1/l2/f2
./l1/l2/f5
./l1/l2/f4
./l1/l2/d0
./l1/l2/d0/f2
./l1/l2/d0/f5
./l1/l2/d0/f4
./l1/l2/d0/f3
./l1/l2/d0/f1
./l1/l2/d0/f0
./l1/l2/f3
./l1/l2/d5
./l1/l2/d5/f2
./l1/l2/d5/f5
./l1/l2/d5/f4
./l1/l2/d5/f3
./l1/l2/d5/f1
./l1/l2/d5/f0
./l1/l2/d4
./l1... (more) |
— | over 1 year ago |
| Comment | Post #289899 |
Thanks! That makes sense. (more) |
— | over 1 year ago |
| Edit | Post #289933 |
Post edited: remove superfluous sort |
— | over 1 year ago |
| Edit | Post #289933 |
Post edited: oops; we need to sort before head(1). |
— | over 1 year ago |
| Edit | Post #289933 |
Post edited: sort last |
— | over 1 year ago |
| Edit | Post #289934 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289934 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289934 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289934 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289934 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289934 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289934 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289934 | Initial revision | — | over 1 year ago |
| Answer | — |
A: How to identify and separate standalone applications from libraries in Linux package lists? This answer is not directly usable under Arch, since I don't know the tools there. I show you a way to do it on Debian, which may inspire you to find a similar way in Arch. With apt-file(1), you can list the files that a package provides. From that list, you can see if the package provides files... (more) |
— | over 1 year ago |
| Edit | Post #289933 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289933 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289933 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289933 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289933 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289933 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289933 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289933 | Initial revision | — | over 1 year ago |
| Answer | — |
A: How to list the first x files in each directory Here's my approach: ```sh find l1 -type d \ | while read d; do find $d -maxdepth 1 -type f \ | head -n3; done; ``` If your middle directories also contain files, it will also show them (of course, only the first 3). This is what it shows for me in a tree similar to yours, where I add... (more) |
— | over 1 year ago |
| Edit | Post #289931 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289931 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289931 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289931 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289931 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289931 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289931 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289931 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289931 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289931 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289931 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289931 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289931 | Post undeleted | — | over 1 year ago |
| Edit | Post #289931 | Post deleted | — | over 1 year ago |
| Edit | Post #289931 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289931 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289931 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289931 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289931 |
Post edited: |
— | over 1 year ago |
| Edit | Post #289931 | Initial revision | — | over 1 year ago |
| Answer | — |
A: How to overwrite each line of STDOUT with the next one? Instead of having new stdout lines overwrite the previous one, it seems better to specify that old stdout lines should be overwritten by anything that comes after them. This has the benefit that stdout cannot overwrite stderr (or anything else that goes in the tty). ```sh #!/bin/sh setterm ... (more) |
— | over 1 year ago |
| Comment | Post #289899 |
Why set `lines=` to empty before entering the alternate screen? (more) |
— | over 1 year ago |
| Comment | Post #289899 |
Why are the two trap(1) calls at different locations? (more) |
— | over 1 year ago |
| Comment | Post #289899 |
Makes sense. Thanks! (more) |
— | over 1 year ago |
| Comment | Post #289899 |
Thanks Kamil! Makes sense.
@quasimodo, no, that would have the same problems as my suggestion. (more) |
— | over 1 year ago |
| Comment | Post #289899 |
Why do you need the `echo x` trick? What happens without it?
I think this would be simpler:
```sh
...
lines="$(tee /dev/tty | tail -n "$n")"
leave
printf '%s\n' "$lines"
```
Am I missing anything?
(more) |
— | over 1 year ago |