On 08/05/2019, noah pugsley <noah.pugs...@gmail.com> wrote: > You know, I guess it's just personal convention from habit. I think I > started doing that way back before I could remember how the redirects work > without looking them up. Too lazy to change now. > > So yeah, if you're trying to divine something clever from that, I wouldn't. > :-)
Okay, yeah, but maybe I can still "divine" something clever and cater to laziness too. Suppose we created a shell script named x and put that e.g. in ~/bin once that's in our path, and then we made it executable. Contents of ~/bin/x: #!/bin/sh $@ > ~/.x.`basename $1`.log 2>&1 & Then we could just type $ x firefox and get nice combined logs of just the last run in case anything went wrong, but otherwise we'd have peace and quiet. I won't claim this beats dmenu, but still. This does no error-checking, but I'm not sure if the added complexity of that would be an advantage to a proficient user. If anyone sees anything seriously wrong with this, speak now or forever hold your peace. > Original Message > From: ropers > Sent: Tuesday, May 7, 2019 21:07 > To: noah pugsley > Cc: Edgar Pettijohn; Steve Litt; misc@openbsd.org > Subject: Re: When will be created a great desktop experience for OpenBSD? > >> From: ropers >> Tangentially related: Does anyone here routinely use the default fvwm? >> >> Now for a really noobish question: Those that do, do you also launch >> graphical apps by typing something like this in xterm: >> >> $ firefox > /dev/null 2>&1 & >> >> or do you normally do something else that I've totally overlooked? > > On 08/05/2019, noah pugsley <noah.pugs...@gmail.com> wrote: >> Maybe I'm a weirdo, but no matter what I use for a window manager, I >> start >> all programs from the cli. All. >> >> For Firefox or Chrome something like this: >> >> $ firefox & bw ; exit >> >> bw is a shortcut to an xterm with a bunch of options. Kill the one with >> the >> console crap and poop out a fresh one. > > You probably know this, but just for the record/archives, the >> $ firefox > /dev/null 2>&1 & > line that I quoted earlier should normally take care of "the console crap": > It redirects firefox's stdout to /dev/null, then redirects firefox's > stderr to stdout and thus to /dev/null, and then sets firefox to run > in the background. > > (So if, I don't know, bw is perhaps just a script you wrote to avoid > "the console crap", then maybe it's not even necessary? I imagine it > might even be easier to keep your history if you're not constantly > spawning new xterms. > If you're way ahead of me here and if I'm just totally missing the > point, the plot and something obvious, feel free to engage in random > acts of clue-battery. ;) >
