On Sat, 3 Sep 2011, Thomas Adam wrote:
OK. I am unable to reproduce this, even with your config. It just does the
right thing for me.
Try the CVS version of FVWM (use branch-2_6) and see if the problem is still
there.
I did it ( --> version 2.6.3) : problem still there
I asked in this f
On Sat, Sep 03, 2011 at 08:10:27PM +0200, Pierre Frenkiel wrote:
> On Sat, 3 Sep 2011, Thomas Adam wrote:
>
> >And in your example, the xclock window remains sticky across a restart
> >because of the fix above.
> Sorry, but i sais the contrary inmy last post: the xclock
> window DOESN'T get th
On Sat, 3 Sep 2011, Thomas Adam wrote:
And in your example, the xclock window remains sticky across a restart
because of the fix above.
Sorry, but i sais the contrary inmy last post: the xclock
window DOESN'T get the sticky flag ...
The only thing I can think of is how you're restarting F
On Sat, Sep 03, 2011 at 07:30:03PM +0200, Pierre Frenkiel wrote:
> Can the differences in behaviuor come from the Linux distrib?
> Which one are you using?
How are you restarting FVWM? In 2.6.2, I fixed a problem in restoring
states with recapturing windows due to WM_COMMAND:
https:/
On Fri, 2 Sep 2011, Thomas Adam wrote:
I'll simplify this a little. Let's say you did this:
Style xclock !A, B
Options "A" and "B" would apply to xclock. They're logically ORed together.
Such that when you do this:
Style xclock A
Going from ¬A to A results in this:
Style xclock A
On Fri, Sep 02, 2011 at 09:59:59PM +0100, Thomas Adam wrote:
> On Fri, Sep 02, 2011 at 10:41:33PM +0200, Pierre Frenkiel wrote:
> > The base of pedagogy being repetition, I'll repeat (or summarize)
>
> Right -- it's this sort of information you didn't supply beforehand. Now I
> can explain to y
On Fri, Sep 02, 2011 at 10:41:33PM +0200, Pierre Frenkiel wrote:
> The base of pedagogy being repetition, I'll repeat (or summarize)
Right -- it's this sort of information you didn't supply beforehand. Now I
can explain to you why what you're seeing is not a bug.
> current setting:
>
On Fri, 2 Sep 2011, Thomas Adam wrote:
How is it complicated?
because of what follows: some parameters works, and other not, and behaviour
not the same with fvwm restart and FvwmConsole
So you're saying that certain attibutes work across a restart of FVWM, but
not others? That's simply n
On Fri, Sep 02, 2011 at 04:09:22PM +0200, Pierre Frenkiel wrote:
>That worked, and with "read debug" also, but the behaviour is much more
>complicated (a good way to drive somebody crazy!)
How is it complicated?
> 1/ with FvwmConsole, all parameters work(Title, Sticky,..)...but
>
On Fri, 2 Sep 2011, Thomas Adam wrote:
And you've confirmed that's the version of FVWM you're actually starting?
i.e., it's found in your $PATH?
yes(checked with fvwm -V), and anyway, I first purged the Debian package
I would do the following:
1. Comment out the "Style xclock NoTitle" l
On Fri, Sep 02, 2011 at 11:40:46AM +0200, Pierre Frenkiel wrote:
> Hi, Thomas,
>
> On Thu, 1 Sep 2011, Thomas Adam wrote:
>
> >Hmm, this would be on Debian or Ubuntu, I presume? I recommend you compile
> >up 2.6.2 manually and install that in preference of what Debian ships.
>
> It's Debian S
Hi, Thomas,
On Thu, 1 Sep 2011, Thomas Adam wrote:
Hmm, this would be on Debian or Ubuntu, I presume? I recommend you compile
up 2.6.2 manually and install that in preference of what Debian ships.
It's Debian Squeeze.
I compiled 2.6.2 ==> same problems
Again, I'll need to see your conf
Hello,
On Thu, Sep 01, 2011 at 06:51:55PM +0200, Pierre Frenkiel wrote:
> 2.5.30
Hmm, this would be on Debian or Ubuntu, I presume? I recommend you compile
up 2.6.2 manually and install that in preference of what Debian ships.
> I checked again that it's not the case for me.
> The changes
Hi Thomas,
Thank's a lot for your detailed reply.
On Thu, 1 Sep 2011, Thomas Adam wrote:
What version of FVWM are you using?
2.5.30
It used to be the case long ago that the Style command didn't apply
immediately; the window had to be recaptured. But this doesn't happen
anymore. Styles a
On Thu, Sep 01, 2011 at 03:55:41PM +0200, Pierre Frenkiel wrote:
> On Thu, 1 Sep 2011, Thomas Adam wrote:
>
> >On 1 September 2011 10:39, Pierre Frenkiel wrote:
> >>hi everybody,
> >>I added the parameter StayOnTOP to Style line for xclock, and that doesn't
> >
> >It's 'StaysOnTop'; note the extr
On 1 September 2011 10:39, Pierre Frenkiel wrote:
> hi everybody,
> I added the parameter StayOnTOP to Style line for xclock, and that doesn't
It's 'StaysOnTop'; note the extra 's' there.
-- Thomas Adam
16 matches
Mail list logo