<
Parent
~inquiry
> I liked that solution of yours with jobs instead of
> termux. Being a command line junkie myself (or rather,
> a REFORMED command line junkie) I am ashamed to say
> I never tried that, I would always stuck with tmux
> and I never liked the experience. I disliked having to
> learn the keystrokes to do things, I also faced the same
> problems as you with the names of each pane (they would
> all say 'bash'), and in a virtual terminal without fbdev
> (as happens in BSD based systems and ones where I didn't
> remember to compile the relevant drivers) that little bar
> at the bottom takes precious screen real estate.
I wound up loving tmux, but of course at some point began wondering if there might be a simpler way to cover the vast majority of my use cases with an even thinner keystroke interface layer that *also* somehow solved my forgetting what window/pane something in particular was running. The older I get, the more "out of sight, out of mind" torments me....
FWIW, I tweaked PROMPT_COMMAND a bit more, prepending its value with "clear;":
export PROMPT_COMMAND='clear;echo "=== jobs ===";jobs'
so that the jobs output always winds up in the top-left of the screen, which saves me time for being able to count on that output always been in the same place, but of course there's always at least a small inconvenience, namely the last line always showing that "clear" is "Done":
=== jobs ===
[1] Stopped digg (wd: ~)
[3] Stopped usenet (wd: ~/News)
[5]- Stopped mp
[6] Stopped weblist x
[7] Stopped gopher
[8] Stopped cl
[9]+ Stopped vic z
[10] Done clear
So I'll just have to see if that annoyance ends up out-weighing what the "clear" accomplishes.
> Also, I am sorry I haven't been around to reply to other
> posts, my head just hasn't been quite there lately.
<taps the surface of his analog watch while feigning impatience>
:-)
Write a reply
~detritus wrote (thread):
maybe try `jobs | head -n -1`
also, analog watches are the best, as is anything that doesn't have a processor