Ooops, didn't think of that!
Then the only correct solution is to drop my request and leave things
as they are.
I'll then just store the parameters otherwhere (file).
Thank you guys for explaining!
Stefan
On 3/5/18, Dominik Vogt wrote:
> On Mon, Mar 05, 2018 at 11:57:27AM
On Mon, Mar 05, 2018 at 11:57:27AM +, Thomas Adam wrote:
> Hi,
>
> On Mon, Mar 05, 2018 at 04:38:08AM +0100, Stefan Blachmann wrote:
> > Hi fvwm-workers,
> >
> > the 1024 char limit in the read line buffer in fvwm/read.c has become too
> > small.
> > This caused a breakage in my
On Mon, Mar 05, 2018 at 07:17:53AM -0500, Dan Espen wrote:
> It would be nice to see Fvwm actually work with RandR.
Hi Dan,
> Working would be sensing the change and moving windows into the new
> screen dimensions. Every once and a while I get the urge to try my
> 1600x1200 panel as 1200x1600.
Branch: refs/heads/ta/randr
Home: https://github.com/fvwmorg/fvwm
Commit: a93ce952f7c0d96bf796e78022037a91405a4b98
https://github.com/fvwmorg/fvwm/commit/a93ce952f7c0d96bf796e78022037a91405a4b98
Author: Thomas Adam
Date: 2018-03-05 (Mon, 05 Mar 2018)
Thomas Adam writes:
> Hi,
>
> Now that the copyright issue has been sorted out, and we're largely able to
> resume things, I can't remember what we said about what the next steps were
> with fvwm.
>
> I know we had some conversations around the state of fvwm2, with this odd
>
Hi,
On Mon, Mar 05, 2018 at 04:38:08AM +0100, Stefan Blachmann wrote:
> Hi fvwm-workers,
>
> the 1024 char limit in the read line buffer in fvwm/read.c has become too
> small.
> This caused a breakage in my MissingSubmenuFunction menu generator
> after after addition of programs + update; the
Branch: refs/heads/origin/dv/stable-fvwm2
Home: https://github.com/fvwmorg/fvwm