Hi there,
I'm new at FVWM and I use Debian Lenny with fvwm "2.5.16".
My goal is to migrate from KDE 3.5 to Fvwm, because KDE 3
is no longer available as soon as Debian Squeeze will appear
(and KDE 4 is not an option for me).
I use the SloppyFocus policy combined with the GrabFocus policy.
I want
2010/8/10 Michael Großer :
> The problem: If I switch to another viewport and then
> back to the prior one, then sometimes no window has the
> focus. If I give a window a focus and close it, then
> again no window has the focus.
>
> How can I solve this problem?
You can't.
> My idea is that I use
Hi!
Thank you very much. This "destroy_window" event could
be the solution I was looking for.
I will try to solve my problem over the weekend.
I like software that is flexible enough to satisfy
all my wishes in my role as a user. I wish I had
recognized the power of fvwm many years earlier.
Mic
On Wed, Aug 11, 2010 at 11:37:51AM +0200, Michael Großer wrote:
> Hi!
>
> Thank you very much. This "destroy_window" event could
> be the solution I was looking for.
>
> I will try to solve my problem over the weekend.
AFAICT there's nothing left to solve?
Oh, and do not top-post on this list,
Thomas Adam wrote:
> On Wed, Aug 11, 2010 at 11:37:51AM +0200, Michael Großer wrote:
>> Hi!
>>
>> Thank you very much. This "destroy_window" event could
>> be the solution I was looking for.
>>
>> I will try to solve my problem over the weekend.
>
> AFAICT there's nothing left to solve?
>
I ne
On Wed, Aug 11, 2010 at 01:23:43PM +0200, Michael Großer wrote:
> space for all my different projects. I configured
> a lot of bindings so I can use the keyboard to
> create new windows or operate with the viewports.
> I studied the sample config files of the fvwm95
> project to get suggestions. I
Thomas Adam wrote:
> On Wed, Aug 11, 2010 at 01:23:43PM +0200, Michael Großer wrote:
>> space for all my different projects. I configured
>> a lot of bindings so I can use the keyboard to
>> create new windows or operate with the viewports.
>> I studied the sample config files of the fvwm95
>> proj
On Wed, Aug 11, 2010 at 02:27:25PM +0200, Michael Großer wrote:
> Thomas Adam wrote:
> > On Wed, Aug 11, 2010 at 01:23:43PM +0200, Michael Großer wrote:
> >> space for all my different projects. I configured
> >> a lot of bindings so I can use the keyboard to
> >> create new windows or operate with
Thomas Adam wrote:
> On Wed, Aug 11, 2010 at 02:27:25PM +0200, Michael Großer wrote:
>
>> 2. destroy_window
>> =
>> This page...
>> http://www.fvwm.org/documentation/manpages/unstable/FvwmEvent.php
>> ... mentions "destroy_window" only two times.
>> I can guess what it does, and I
On Wed, Aug 11, 2010 at 04:19:20PM +0200, Michael Großer wrote:
> Thomas Adam wrote:
> > On Wed, Aug 11, 2010 at 02:27:25PM +0200, Michael Großer wrote:
> >
> >> 2. destroy_window
> >> =
> >> This page...
> >> http://www.fvwm.org/documentation/manpages/unstable/FvwmEvent.php
> >> .
Thomas Adam wrote:
> On Wed, Aug 11, 2010 at 04:19:20PM +0200, Michael Großer wrote:
>> Thomas Adam wrote:
>> > On Wed, Aug 11, 2010 at 02:27:25PM +0200, Michael Großer wrote:
>> >
>> >> 2. destroy_window
>> >> =
>> >> This page...
>> >> http://www.fvwm.org/documentation/manpages/u
On Thu, Aug 12, 2010 at 10:03:01AM +0200, Michael Großer wrote:
> I cannot find any displayable man page.
> But, I found some kind of source file named "FvwmEvent.1.in".
> There, I found:
Download the file -- the direct link to the raw file is here:
http://github.com/ThomasAdam/fvwm/raw/49a53ee40
On Wed, Aug 11, 2010 at 04:19:20PM +0200, Michael Großer wrote:
> Thomas Adam wrote:
> > On Wed, Aug 11, 2010 at 02:27:25PM +0200, Michael Großer wrote:
> >
> >> 2. destroy_window
> >> =
> >> This page...
> >> http://www.fvwm.org/documentation/manpages/unstable/FvwmEvent.php
> >> .
> On Thu, Aug 12, 2010 at 10:03:01AM +0200, Michael Großer wrote:
> > I cannot find any displayable man page.
> > But, I found some kind of source file named "FvwmEvent.1.in".
> > There, I found:
>
> Download the file -- the direct link to the raw file is here:
>
> http://github.com/ThomasAdam/fv
On Thu, Aug 12, 2010 at 03:59:26PM +0200, michael.gros...@gmx.de wrote:
> Why not "res_name --> WM_NAME"?
> I cannot see the logic...
That's because it's not meant to be easy to understand by those who aren't
programmers, I suppose.
I'll reiterate it again for you though.
The WM_CLASS XAtom has
On Thu, Aug 12, 2010 at 08:19:10AM +0100, Thomas Adam wrote:
> I started this for FvwmEvent -- you can see the changes to the manpage here:
>
> http://github.com/ThomasAdam/fvwm/commit/49a53ee408cba26f7649fc4b56df0d309b485cfd
>
> Run that file through "man" -- see the table produced. Is that wha
Thomas Adam wrote:
> On Thu, Aug 12, 2010 at 08:19:10AM +0100, Thomas Adam wrote:
>> I started this for FvwmEvent -- you can see the changes to the manpage here:
>>
>> http://github.com/ThomasAdam/fvwm/commit/49a53ee408cba26f7649fc4b56df0d309b485cfd
>>
>> Run that file through "man" -- see the ta
Michael Großer writes:
> Our conversation drifted into a direction where I stated that
> I didn't understand the difference between "res_class" and
> "res_name".
>
> You answered that only programmers are supposed to understand
> the documentation related to "res_class" and "res_name", and that
>
Dan Espen wrote:
> Michael Großer writes:
>
>> Our conversation drifted into a direction where I stated that
>> I didn't understand the difference between "res_class" and
>> "res_name".
>>
>> You answered that only programmers are supposed to understand
>> the documentation related to "res_class"
On Sun, Jan 01, 2012 at 10:06:33PM +0100, Michael Großer wrote:
> I recommend to recheck this piece of documentation:
>
> +-++
> |res_class||
> | | Runs when the WM_CLASS |
> |
On Sun, Jan 01, 2012 at 07:17:24PM +0100, Michael Großer wrote:
> This event is absent in the table, and I don't understand the
> meaning of the quoted statement.
Removing it is easier.
-- Thomas Adam
--
"Deep in my heart I wish I was wrong. But deep in my heart I know I am
not." -- Morrissey
Thomas Adam wrote:
> 2010/8/10 Michael Großer :
>> The problem: If I switch to another viewport and then
>> back to the prior one, then sometimes no window has the
>> focus. If I give a window a focus and close it, then
>> again no window has the focus.
>>
>> How can I solve this problem?
>
> You
On Fri, Aug 13, 2010 at 01:31:36PM +0200, Michael Großer wrote:
> Then, I handle the dirty details.
> > # 1. if a window is already focussed, then do nothing
Current implies focused, of course, but:
DestroyFunc focus_a_window
AddToFunc focus_a_window
+ I Current (Focused) Break
> > # 2. if no
Thomas Adam wrote:
> On Wed, Aug 11, 2010 at 01:23:43PM +0200, Michael Großer wrote:
>> clock at the bottom right corner of my screen
>> using 3 instances of xclock to let it show
>> me the day of the week (1st instance), the
>> date (2nd instance) and the time (3rd instance).
>> Fvwm is automatica
Michael Großer wrote:
> No unstabilising Waits anymore. I use the "-geometry" option now to place the
> instances onto the right coordinates. And the Schedule command
> ensures that the clocks start in the right order (the "date" overlays
> the "day of week", the "time" overlays the "date" (and not
25 matches
Mail list logo
