gmane.comp.window-managers.wmii

Re: no program starts with M+p: not yet solved

Davide Anchisi — 2008-09-26T09:40:01

Thank you, now it works. I removed everything and installed the latest hg release. Best, davide 2008/9/24 Davide Anchisi gmail.com>:

Re: no program starts with M+p: not yet solved

Davide Anchisi — 2008-09-24T17:02:43

I will try that way, Thanks, Davide 2008/9/24 Alex Kilgore gmail.com>:

Re: no program starts with M+p: not yet solved

Alex Kilgore — 2008-09-24T15:10:09

I had similar problems at one point, I still dont know what caused them, but I was able to work around the issue by removing most of wmii's components and installing the latest hg release...not a fix but a solution, could have been some leftovers from a previous install or something, as i think my wmii.sh was messed up along with some other stuff Thanks Alex Davide Anchisi wrote:

Re: no program starts with M+p: not yet solved

Davide Anchisi — 2008-09-24T10:10:59

I still cannot use M+p to run any program. Now the report in ~/.xsession-errors: wmiir: fatal: Can't open file '/rbar/status': file not found is gone (and the status bar was always ok). Any other idea were to look or what to do? Thanks for any help, Davide

Re: no program starts with M+p

Davide Anchisi — 2008-09-23T15:16:47

wmiir: fatal: Can't open file '/rbar/status': file not found In ~/.xsession-errors the only thing that seems relevant is: wmiir: fatal: Can't open file '/rbar/status': file not found Is it that? What does it mean?

Re: no program starts with M+p

sqweek — 2008-09-23T13:46:32

Alright, check the console you started X from or ~/.xsession-errors for diagnostics after attempting MOD-p. -sqweek

Re: no program starts with M+p

Davide Anchisi — 2008-09-23T12:34:00

2008/9/23 sqweek gmail.com>: Any application, such as rxvt, abiword, firefox, xclock, etc. Running a program from a terminal I have no problem at all and no warning message.

Re: no program starts with M+p

sqweek — 2008-09-23T11:14:35

The name of an application such as what? Run the program in a terminal and see if you get any diagnostics. Hahaha, this is what I get for dragging my feet on the announcement. But wmii+ixp-20080520 has libixp bundled, so I wouldn't be sure you're using 0.5. It shouldn't matter in any case, if there was something wrong with your libixp problem you'd be seeing much more serious problems. -sqweek

no program starts with M+p

Davide Anchisi — 2008-09-23T09:25:12

Dear all, I compiled and installed wmii (snapshot: wmii+ixp-20080520) on a new machine, and I cannot run any program using M+p. Typing the name of an application it gets displayed in the bar, but after pressing enter the program does not start. M+a and M+enter are working properly. I'm using: dmenu-3.9 plan9port-20080909 libixp (it should be 0.5, I got it via hg clone http://code.suckless.org/hg/libixp, 2 days ago) GNU/Linux Ubuntu 8.04 Thanks for any help, Davide

Re: sswriter

Jonathan 'Sky' Squirawski — 2008-09-18T19:11:04

Le Thu, 18 Sep 2008 18:22:47 +0200, Stanimir Dragiev cs.tu-berlin.de> a écrit : Lol I'm sure not. Yes I've my reasons :p One is that the new sswriter will be more efficient and faster. Each element will have its intervall of time to be checked (groups of elements will be possible) and data stored by the daemon. For example the time (with seconds) needs to be update more frequently than the battery charge. A reason for the client/server features is I want that sswriter monitor all my computers and send data to my web site. But the lamda user will be able to ignore these features. In brief... I've my scenarios :p Thanks :)

Re: sswriter

Stanimir Dragiev — 2008-09-18T16:22:47

Hi, * Jonathan 'Sky' Squirawski sky-siteweb.com> [2008-09-16 22:23]: That's OK with me. I just wanted to be helpful, if someone does have same preferences like me. My code is not that suckless -- you might have saved the world by not applying the patch :o))) I do not need these client/server features. I would achieve similar effect by using ssh and invoking sswriter, as is, and printing what I want (if I understand correctly). So, I think I'll stick to the current sswriter. But you surely have your reasons and scenarios for the new version. Happy coding! Good luck!

Re: sswriter

Jonathan 'Sky' Squirawski — 2008-09-16T20:16:29

Hello, I would enjoy to patch sswriter with your feature but actualy I'm rewriting it with a totaly new design. In my new version, sswriter is composed of a daemon and several tools to start/get some "monitoring elements" and can be used by the network. The final purpose is to have tools wich can monitor a group of computers and print some charts on a web site. But I want to keep a meaning to use it for a status bar same as before with more ease (by introduce the concept of profile to load a configuration in a file for example). Unfortunatly I'm not really ready to distribute this version of sswriter before a moment... :s Regards, Jonathan 'Sky' Squirawski Le Tue, 16 Sep 2008 16:58:34 +0200, stanio< at >cs.tu-berlin.de a écrit :

sswriter

2008-09-16T14:58:34

Hi, I used to have a plenty of perl scripts to fill the status line, but find the native way of doing this considerably faster => better. When I found sswriter on this thread in May I was missing the ability to get the content of a file at particular place in the output. After this feature have been implemented a month later the main thing I was missing was the ability to limit the number of chars in particular areas of the output. I need this, because I like to have the more important part on the right (battery, network ifaces, load, etc.) and the less important on the left, near the wmii/dwm tags. The less important part tends to have unpredictable size, e.g. incoming instant messages, and sometimes eats the space for the important part. I have implemented the areas concept some weeks after that. Please find below the patch for 0.3.1. If it gets corrupted by the mail transfer, I can provided it through http, too. Just drop a line, if needed. The code is far from good quality -- suggestions are welcome

Default configuration

Alex Kilgore — 2008-09-12T01:09:18

Hi everybody! so recently (after having upgraded to the mercurial releases from the snaps) I have been able to get a working configuration every time but with some tweaking, and I have a feeling im not doing it all the way that was intended. The way I have it set up, after browsing some of the various scripts, I noticed the config directory is ~/.wmii-hg/ now instead of .wmii-3.5? I have moved everything there, but for some reason, I needed to do like...wmii -r ~/.wmii-hg/wmiirc to make it work right Is there something I am missing here about how this is to be set up? or is this how you are supposed to choose between wmiirc and rc.wmii Another thing is, with this setup mod+a isnt doing what its supposed to either, it lists everything in ~/ for whatever reason, could someone point me in the right direction as to how this is supposed to be set up? By the way, I love the recent changes that were merged! =) Thanks, Alex

Re: Mouse focus behavior.

Thomas Gallen — 2008-09-08T04:01:43

Tried out 2.6.27-rc5 and it seems to be working. I thought it had been doing the same thing in 2.6.25 and 2.6.24 but I'm not known for my memory anyway. Thanks. Now if I can find out what's causing the mouse focus quirk then I would be in the clear. Thomas On Mon, Sep 08, 2008 at 10:23:10AM +0800, sqweek wrote:

Retagging floating clients

Alex Kilgore — 2008-09-08T03:05:17

I reported this issue on the tracker, thought I should send a notification in case it didnt get sent by google code What steps will reproduce the problem? 1. open two xterms 2. move both xterms to the floating layer 3. re-tag one of them with '2' What is the expected output? What do you see instead? expected: xterm gets re-tagged actual: wmii stops with cannot read /client/sel/tags unexpected eof What version of the product are you using (wmii -v)? On what operating system? wmii-hg2345 Debian/GNU Linux Lenny

Re: Mouse focus behavior.

sqweek — 2008-09-08T02:23:10

You sure that is xcompmgr? Linux 2.6.26-rc1 broke terminal SIGWINCH notification. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483564 The bug is fixed since 2.6.27-rc1. -sqweek On Mon, Sep 8, 2008 at 10:17 AM, Thomas Gallen gmail.com> wrote:

Re: Mouse focus behavior.

Thomas Gallen — 2008-09-08T02:17:37

I guess I'm just unlucky tonight... I'll go update other things and hope it's a bizzare glitch... The only thing out of the ordinary is that I'm using xcompmgr and while that does cause terminals to do funky things with resizing (or not resizing) I haven't had problems with focus before. Thanks for checking. Thomas On Sun, Sep 07, 2008 at 09:50:43PM -0400, Alex Kilgore wrote:

Re: Mouse focus behavior.

Alex Kilgore — 2008-09-08T01:50:43

Actually I do not see this one, I use hg2345 as well hm... Alex

Mouse focus behavior.

Thomas Gallen — 2008-09-07T23:09:51

With the latest tip I've noticed mouseover focus behavior has changed a bit. When moving the mouse over another window (either in the same column or to another column) the focus may not follow if you move the mouse too quickly. Unfortunately "too quickly" isn't exactly a blinding speed either. I'm also guessing it's not an anti-"oops moved the mouse too far" either because leaving the mouse over the unfocused window doesn't raise it after any amount of time. Anyone else noticing this? I'm using version hg2345. Thomas

Re: Two wmii.rc issues

Armando Di Cianno — 2008-09-05T16:25:03

FWIW, you really should always use "su -", which is the short form of "su -l", which simulates a full log in. The reason I suggest using "su -" as a habit and solely "su" when explicitly desired, is that there are common administration tasks that use environment variables and permissions, and over time, using solely "su", tends to cause a mish-mash of bad permissions on files you touch