On Sat, Apr 04, 2020 at 09:18:04PM +0200, Lothar Brendel wrote:
> Package: grace
> Version: 1:5.1.25-7+b1
> Severity: normal
> 
> Dear Maintainer,
> 
> xmgrace's UI got slightly inferior since version 1:5.1.25-6: The menu 
> accelerators have dissapreared, the font is less fitting.
> 
> Actually, I beg to differ regarding bug #727796 and its fix. The Xresources 
> hardcoded in xmgrace.c are *fallback* resources, employed via 
> XtAppSetFallbackResources(). They can be and *are* overriden by user 
> specified Xresources (I don't know why this didn't work in the bug reporter's 
> case). What's a bit annoying: *All* of them are dismissed as soon as a 
> resource file is given, even an empty one.
> 
> This can be verified nicely in version 1:5.1.23-3: Without an 
> /etc/X11/app-defaults/XMgrace, the UI has colors, a nice font, and menu 
> accelerators. With an empty /etc/X11/app-defaults/XMgrace, it is b/w, has a 
> monospaced font and no menu accelerators. Unfortunately, with the 
> /etc/X11/app-defaults/XMgrace shipped since version 1:5.1.23-6, it has 
> colors, but still the monospaced font and still no menu accelerators. This I 
> consider a regression.

Some of this may be DE-dependent; I get a monospaced font *with*
accelerators.  But I take your point.

> My suggestion: Don't cripple the fallback resources in the code and instead 
> of supplying a deficient /etc/X11/app-defaults/XMgrace, provide an example in 
> the docs. The example file could contain precisely the fallback values, then 
> the user could edit just the relevant bits.

This seems reasonable.  I feel like very, very few people are
customizing their Xresources file in the current day.  



-- 
Nicholas Breen
nbr...@debian.org

Reply via email to