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
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
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 modu
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.
| > [...] 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 pat
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 main
