Re: [dev] Introducing XLSH
2011/10/21 Michał Siejak : > Back to the topic: xlsh github page now has proper wiki with HOWTOs on > compiling and installing it on Arch and Ubuntu Linux as well as > configuration articles. Head to: https://github.com/Nadrin/xlsh/wiki Thanks for writing this, Michał. Some reports on getting it working on Debian. In order to start it as your X display manager you need the following line in your /etc/inittab: x:2:respawn:/usr/local/sbin/xlshd -f Similar to arch, but different runlevel. Since the xdotool in debian/wheezy does not support the --sync option to the search command, I had to apply the hack in attached diff to give the xterm window focus. I'm sure there are better ways, it it seems to work. Also, xlsh fails to set my PATH to what's in include/config.h, but rather leaves it as /sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin as specified in xlshrc. I don't know why. -- Mikael Schönenberg diff --git a/etc/xlshrc b/etc/xlshrc index ca9fbba..e1df4f4 100644 --- a/etc/xlshrc +++ b/etc/xlshrc @@ -19,7 +19,7 @@ fi xrdb -merge "$XRESFILE" xsetroot -solid "$BGCOLOR" if which xdotool; then - ( xwindow=$(xdotool search --sync --class $TERMINAL) -xdotool windowfocus "$xwindow" )& + ( xwindow=$(sleep 1 && xdotool search --class $TERMINAL) +xdotool windowfocus --sync "$xwindow" )& fi exec $TERMINAL -g 80x15+$px+$py -e $(which xlsh)
Re: [dev] [dwm] sloppy focus
On Mon, Jul 4, 2011 at 20:17, Benjamin R. Haskell wrote: > I don't understand how to effectively use IRC without doing one of the > following: > > 1. keeping it on-screen (which seems impractical to me, partly because I > still don't quite "get" dwm) > > or > > 2. having some kind of indication that you've been addressed (urgent hints > or whatever). Teach your fellow IRCers that it's an asynchronous communication form, and that they can wait until you have time to read? -- Mikael Schönenberg
Re: [dev] [surf] patches: configurable file locations, bookmark writer, history writer
On Wed, Sep 9, 2009 at 15:31, Ray Kohler wrote: > The difficulty with using xprop to read and write surf's URL is that > even though I have the XID when the session starts, there's a risk > that it changes. Links may open themselves in new windows, or the user > might choose to do it with webkit's context menu. It seems > uncomfortable to require the user of a bookmark managing system to do > some manual step to indicate which window their action applies to, so > I chose to let the window initiate the action, as in these patches, > which resolves the ambiguity. Presumably, it's the currently focused window when the user creates the bookmark. Or is that too naive? -- Mikael Schönenberg
