Re: FVWM: Command-line tool for listing windows?

[Kathryn Andersen]

On Mon, Jan 30, 2012 at 05:49:17PM -0500, Chris Siebenmann wrote:
> | On 30 January 2012 21:28, Chris Siebenmann  wrote:
> | > ??Does anyone know if there exists a good command line tool for
> | > listing either the window IDs or the window names of all windows
> | > of a specific class (or better yet, set of classes)? Or is this
> | > something that's better done with an fvwm module written in Perl
> | > with fvwm-perllib[*]?
> | 
> | xwininfo
> | xprop

>  At this point it might be useful to explain my overall motivation: I
> want to put together something that lets me select xterm windows from
> the keyboard based on their name, with name completion. My current plan
> is to use dmenu for the window name completion (and a script around it
> to then act on the window). But for this I need to feed the window names
> into dmenu[*].

I think wmctrl might help.  It doesn't come standard with X but you
should be able to install it as a separate package.

The command "wmctrl -l -x" will list all the windows managed by the
window manager, and include their WM_CLASS classes.  You could then
grep on the required classes and get the window names.

A bit of playing around got me this command line:

wmctrl -l -x | grep -i rxvt | cut -b47-

(note that I'm using rxvt rather than xterm for my terminals)

K.A.
-- 
 _--_|\ | Kathryn Andersen  
/  \| 
\_.--.*/| 
  v | 
| Melbourne -> Victoria -> Australia -> Southern Hemisphere
Maranatha!  |   -> Earth -> Sol -> Milky Way Galaxy -> Universe

Re: FVWM: Command-line tool for listing windows?

[Thomas Adam]

On 30 January 2012 21:28, Chris Siebenmann  wrote:
>  Does anyone know if there exists a good command line tool for listing
> either the window IDs or the window names of all windows of a specific
> class (or better yet, set of classes)? Or is this something that's
> better done with an fvwm module written in Perl with fvwm-perllib[*]?

xwininfo
xprop

But why not get FVWM to do it?   No need for a module, just a
conditional command.

All (SomeCondition, ClassName, OtherCondition) Echo "$[w.id]: $[w.class]"

-- Thomas Adam

Re: FVWM: Command-line tool for listing windows?

[Mag. Dr. Nikolaus Klepp]

Am Montag, 30. Januar 2012 schrieb Chris Siebenmann:
>  Does anyone know if there exists a good command line tool for listing
> either the window IDs or the window names of all windows of a specific
> class (or better yet, set of classes)? Or is this something that's
> better done with an fvwm module written in Perl with fvwm-perllib[*]?
>
>  Thanks in advance.
>
>   - cks
> [*: it's pretty easy to write a module to do this, but I'd prefer to
> have a command line tool that I can hook into other scripts; my
> shell scripting is better than my Perl.]


You could look at 
xwininfo -root -tree 



-- 

Mag. Dr. Nikolaus Klepp
Einnehmerstraße 14
A-4810 Gmunden
Tel.: +43 650 82 11 724
email: off...@klepp.biz

FVWM: Command-line tool for listing windows?

[Chris Siebenmann]

 Does anyone know if there exists a good command line tool for listing
either the window IDs or the window names of all windows of a specific
class (or better yet, set of classes)? Or is this something that's
better done with an fvwm module written in Perl with fvwm-perllib[*]?

 Thanks in advance.

- cks
[*: it's pretty easy to write a module to do this, but I'd prefer to
have a command line tool that I can hook into other scripts; my
shell scripting is better than my Perl.]

Re: FVWM: HEADS UP: Releasing 2.6.4 end of January

[Chris Siebenmann]

| > [...] There are several reasons as of why certain patches aren't
| > accepted. Some of the patches affect areas of fvwm which in the long
| > term goal should be replaced by modules. Others are unclean, and no
| > one has been willing to clean up the code and write documentation for
| > the patches.
| 
| i get this but if no work has happened why cant we use the patches?
| its these delays which make users want to use another window manager

 You should be able to use the patches without problems, assuming that
they apply cleanly; just build a personal version of fvwm with the
patches applied. No one requires that you run only fvwm source straight
from the distribution tarballs or the CVS repository.

 If the patches do not apply cleanly or do not work as-is, well, someone
has to do the work to make them work. The fvwm maintainers are not going
to do this work for patches that they feel are a bad idea, for obvious
reasons.

- cks, who patches his own version of fvwm and accepts the
   job of maintaining those patches

Re: FVWM: HEADS UP: Releasing 2.6.4 end of January

[Harry portobello]

On 29 January 2012 08:08, Viktor Griph  wrote:
> 2012/1/27 Harry portobello :
>> we have lots of patches like adding round corners and fluxbox handels
>> which have not been added to fvwm in long time - and why is this? why
>> isnt the maintainer - thomas - adding these?
>
> There is no single maintainer of fvwm. It is maintained by
> fvwm-workers. Thomas has been putting a lot of time and effort into
> releasing 2.6, when no other fvwm-worker really has had the time to do
> so. There are several reasons as of why certain patches aren't
> accepted. Some of the patches affect areas of fvwm which in the long
> term goal should be replaced by modules. Others are unclean, and no
> one has been willing to clean up the code and write documentation for
> the patches.

i get this but if no work has happened why cant we use the patches?
its these delays which make users want to use another window manager

>> so a new maintainer should listen more to this i hope
>
> And what makes you think that another fvwm-worker will have more time
> now, when Thomas have been mostly alone doing the all hard work for
> quite some time. Just because he no longer have the time either, it
> doesn't mean that other fvwm-workers will have more time.

i hope theyd be more responsive to questions like this - and not to ignore them

Harry