GNU bug report logs - #69454
Not possible to insert an empty vtable

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Joost Kremers <joostkremers <at> fastmail.fm>
Cc: adam <at> alphapapa.net, larsi <at> gnus.org, 69454 <at> debbugs.gnu.org, eric.marsden <at> risk-engineering.org
Subject: bug#69454: Not possible to insert an empty vtable
Date: Fri, 31 May 2024 08:24:33 +0300

> From: Joost Kremers <joostkremers <at> fastmail.fm>
> Cc: Adam Porter <adam <at> alphapapa.net>,  Lars Ingebrigtsen <larsi <at> gnus.org>,
>   69454 <at> debbugs.gnu.org,  Eric Marsden <eric.marsden <at> risk-engineering.org>
> Date: Thu, 30 May 2024 23:52:20 +0200
> 
> On Thu, May 30 2024, Joost Kremers wrote:
> > 0002-Fix-recomputing-of-vtable-column-alignment.patch
> >
> > This one fixes what I believe to be another bug: `vtable--compute-columns`
> > should be able to recompute the columns, including setting the alignment
> > property. It didn't actually do the latter, though.
> 
> Actually, forget about this one. I just realised that `vtable--compute-columns`
> doesn't override the alignment property because it may have been set explicitly
> in `make-vtable`. The actual problem is that if a table is created without data,
> the alignment property of each column is set to `right`, even though there's no
> reason to do so.
> 
> I'll try and come up with a better patch.

Thanks for working on this.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.