On Mon, Nov 15, 2021 at 01:26:31AM +0100, Dominik Vogt wrote:
> 0001: Improve Snap... docuemntation.
> 0002: Improve EdgeMoveDelay documentation.
> 0003: Remove superfluous "#if 1".
Applied, thanks!
Kindly,
Thomas
not the code quality.
Right, I understand. Yeah, that's fair. I think the majority of the bigger
breaking changes have largely happened (such as deprecating certain modules),
but you're right -- we should take stoke of that, and what's left and make
that a focus of the release schedule(s).
Kindly,
Thomas
levant section for .adoc files and then that would also apply to Vim as
well (which is what I use).
Kindly,
Thomas
ip efence (and possibly
the BSDs), but it all pales in light of Valgrind.
I know Dan used to use one of the proprietary IBM profilers on fvwm's code
base from time-to-time as well, but I don't recall what that was called.
Kindly,
Thomas
On Mon, Nov 15, 2021 at 02:07:58AM +0100, Dominik Vogt wrote:
> 0001: Remove Efence and Dmalloc support.
> 0002: Remove trailing whitespace.
Applied. Thanks!
Kindly,
Thomas
On Mon, Nov 15, 2021 at 12:11:51PM +0100, Dominik Vogt wrote:
Thanks. Will apply. With respect this this patch:
> 0007: Remove the "MWM COMPATIBILITY" section. Nobody cares anymore.
Presumably the "OPEN LOOK AND XVIEW COMPATIBILITY" section can go as well?
Kindly,
Thomas
am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Patches 1 - 4 before it apply just fine.
Any thoughts?
Thomas
e instead), and some
context_t which has evaluated which window, etc., the command needs in order
to run. Then you can add some function pointers for checking/validating the
parsed string, etc.
Kindly,
Thomas
attached patch mocks up a global monitor to use if init fails.
> It works at the first glance, but the patch is not very clean.
> Please comment.
It sucks. Under whar circumstances is this likely to fail? I mean, I
appreciate the point you're making, but whatelse am I missing?
Kindly,
Thomas
On Fri, Nov 26, 2021 at 12:45:36AM +0100, Dominik Vogt wrote:
> On Thu, Nov 25, 2021 at 11:04:25PM +0000, Thomas Adam wrote:
> > On Wed, Nov 24, 2021 at 03:13:34PM +0100, Dominik Vogt wrote:
> > > From FScreen.c:FScreenParseGeometryWithScreen():
> > >
> > &
On Wed, Nov 24, 2021 at 03:43:47PM +0100, Dominik Vogt wrote:
> Does anybody know why this is a macro and not a function?
> (screen.h)
Because when I wrote it, it wasn't as complex as it is now.
See the ta/update-fvwm-screen branch, I've converted it to a function instead.
Kindly,
Thomas
On Wed, Nov 24, 2021 at 03:13:34PM +0100, Dominik Vogt wrote:
> From FScreen.c:FScreenParseGeometryWithScreen():
>
> I can't fix this because I don't understand what the code does.
I will fix this.
Kindly,
Thomas
I am not sure whom to send this e-mail to, so out of desperation and am
sending it to the fvwm-workers. If this is the wrong place, I would
appreciate it if you could tell me where I could get help.
On April 10, 2004, I installed FVWM-2.4.18 using ./configure
--without-gnome and got, among
201 - 213 of 213 matches
Mail list logo