Manoj Srivastava wrote:
I am curious what could have caused it - in order to compile fvwm I
had to install a lot of new packages, so maybe it has to do
something with that - does fvwm exectuable/FvwmEvent module have
some external dependencies which, if lacking, won't prevent them
from running,
On Sun, 23 May 2004 16:55:34 +0200
ddtl [EMAIL PROTECTED] wrote:
Anyway, if nobody else had reported the problem it is
probably not worth the effort.
AFAIK, there is nothing wrong with the debian package, and I use
FvwmEvent extensively.
Furthermore, your ideas for re-installing are a bit
On Thu, 20 May 2004 21:48:09 +0200, ddtl [EMAIL PROTECTED] said:
I am curious what could have caused it - in order to compile fvwm I
had to install a lot of new packages, so maybe it has to do
something with that - does fvwm exectuable/FvwmEvent module have
some external dependencies which,
Mikhael Goikhman wrote:
On 19 May 2004 22:31:41 +0200, [EMAIL PROTECTED] wrote:
Maybe Debian's patch modifies something - it (the patch) is quite
large (200 Kb), and though I couldn't find that it modifies
the code itself, maybe some settings were affected.
Well, this is pretty easy to
What is your fvwm version and full FvwmEvent config?
I use fvwm 2.5.10 (from Debian unstable), .fvwm2rc is at
the end of the post (without menu definitions key bindings,
as they are not important)
and what can I do to get the desired effect?
This is answered in FAQ #3.18.
On 19 May 2004 16:15:56 +0200, ddtl wrote:
What is your fvwm version and full FvwmEvent config?
I use fvwm 2.5.10 (from Debian unstable), .fvwm2rc is at
the end of the post (without menu definitions key bindings,
as they are not important)
I can't reproduce any problem, both map and
Mikhael Goikhman wrote:
On 19 May 2004 16:15:56 +0200, ddtl wrote:
What is your fvwm version and full FvwmEvent config?
I use fvwm 2.5.10 (from Debian unstable), .fvwm2rc is at
the end of the post (without menu definitions key bindings,
as they are not important)
I can't reproduce any
On 19 May 2004 20:18:44 +0200, [EMAIL PROTECTED] wrote:
Mikhael Goikhman wrote:
On 19 May 2004 16:15:56 +0200, ddtl wrote:
What is your fvwm version and full FvwmEvent config?
I use fvwm 2.5.10 (from Debian unstable), .fvwm2rc is at
the end of the post (without menu definitions key
Yes, I did. Copy-paste the following lines into FvwmConsole. They should
work for 2.5.10.
DestroyModuleConfig FvwmEvent*
*FvwmEvent: add_window Maximize
KillModule FvwmEvent
FvwmEvent
Still no go.
Is it possible you just destroy StartFunction later in your config?
Are you sure
On 19 May 2004 22:31:41 +0200, [EMAIL PROTECTED] wrote:
Maybe Debian's patch modifies something - it (the patch) is quite
large (200 Kb), and though I couldn't find that it modifies
the code itself, maybe some settings were affected.
Well, this is pretty easy to verify. Download and unpack
Hello,
I want to configure fvwm so that new windows would be
automatically maximized.
Obviously, the way to achieve this is by using the FvwmEvent module.
I tried to put the following in .fvwm2rc:
Module FvwmEvent
*FvwmEvent: map Maximize
but it doesn't works.
Why is that, and what can I do
On 18 May 2004 19:55:36 +0200, ddtl wrote:
I want to configure fvwm so that new windows would be
automatically maximized.
Obviously, the way to achieve this is by using the FvwmEvent module.
I tried to put the following in .fvwm2rc:
Module FvwmEvent
*FvwmEvent: map Maximize
but it
12 matches
Mail list logo
