Re: [dev] [dwm] new release - transition from Openbox

2019-02-05 Thread Eric Pruitt
On Tue, Feb 05, 2019 at 07:20:22PM +0100, Szpak wrote: > That's a reasonable choice. I actually do the same in my environment. W-key > is probably the only way to not interact with any app. I use Caps Lock after mapping it to Hyper: xmodmap -e "remove mod4 = Hyper_L" \ -e "remove

Re: [dev] [dwm] new release - transition from Openbox

2019-02-05 Thread Szpak
Not all keyboards have a logo key, most of them have an alt key though. Well, yes, that may be truth. I've never seen one, though (apart from 8-bits of '80).

Re: [dev] [dwm] new release - transition from Openbox

2019-02-05 Thread Quentin Rameau
> That's a reasonable choice. I actually do the same in my environment. > W-key is probably the only way to not interact with any app. Should be > default one in my opinion. Not all keyboards have a logo key, most of them have an alt key though.

Re: [dev] [dwm] new release - transition from Openbox

2019-02-05 Thread Szpak
Hi, thanks for advice. One of the big pluses is pinning an app to a workspace. When I boot, I get two xterm windows in workspace 1, a browser in workspace 2, and my email client in workspace 3. That sounds interesting. At the moment I do the same at startup with xdotool set_desktop n and xdoto

Re: [dev] [dwm] new release - transition from Openbox

2019-02-05 Thread Quentin Rameau
> > One of the big pluses is pinning an app to a workspace. When I boot, I > > get two xterm windows in workspace 1, a browser in workspace 2, and my > > email client in workspace 3. > > That's intriguing. Would you please explain how to do this? Read the Rule array in config.h.

Re: [dev] [dwm] new release - transition from Openbox

2019-02-05 Thread Greg Reagle
On Mon, Feb 4, 2019, at 20:03, Sean MacLennan wrote: > One of the big pluses is pinning an app to a workspace. When I boot, I > get two xterm windows in workspace 1, a browser in workspace 2, and my > email client in workspace 3. That's intriguing. Would you please explain how to do this?

Re: [dev] quark and uds

2019-02-05 Thread sylvain . bertrand
On Tue, Feb 05, 2019 at 05:01:57AM -0500, Martin Tournoij wrote: > as soon as you start doing more than printing raw strings. Not even raw strings, but raw "lines" (\n added by echo). My 3c. -- Sylvain

Re: [dev] quark and uds

2019-02-05 Thread Martin Tournoij
On Tue, Feb 5, 2019, at 21:40, k...@shike2.com wrote: > >> "My 2c": I would prefer shell "printf" than "echo -n -e" > > > > yeah, good point. Any of which works. > > Yes, but echo -n is not POSIX. -n is mentioned, but its meaning is not defined ("defined by implementation"). -e isn't mentioned a

Re: [dev] quark and uds

2019-02-05 Thread k0ga
>> "My 2c": I would prefer shell "printf" than "echo -n -e" > > yeah, good point. Any of which works. Yes, but echo -n is not POSIX.