GNU bug report logs - #27890
26.0.50; describe-font does not use Help buffer history

Previous Next

Package: emacs;

Reported by: Alex <agrambot <at> gmail.com>

Date: Mon, 31 Jul 2017 21:26:02 UTC

Severity: minor

Tags: fixed, patch

Found in version 26.0.50

Fixed in version 26.1

Done: npostavs <at> users.sourceforge.net

Bug is archived. No further changes may be made.

Full log


Message #16 received at 27890 <at> debbugs.gnu.org (full text, mbox):

From: Alex <agrambot <at> gmail.com>
To: npostavs <at> users.sourceforge.net
Cc: 27890 <at> debbugs.gnu.org
Subject: Re: bug#27890: 26.0.50; describe-font does not use Help buffer history
Date: Sat, 05 Aug 2017 20:01:33 -0600
npostavs <at> users.sourceforge.net writes:

> tags 27890 + patch
> quit
>
> Alex <agrambot <at> gmail.com> writes:
>
>> Alex <agrambot <at> gmail.com> writes:
>>
>>> describe-font does not add to the *Help* buffer's history. The [Back]
>>> button does appear when there is a non-empty history, but going back and
>>> then forward does not restore the font description.
>>
>> Here's a patch for it.
>>
>> +  (let ((xref-item (list #'describe-font fontname))
> [...]
>> +      (help-setup-xref xref-item (called-interactively-p 'interactive))
>
> Looks fine, personally I wouldn't bother introducing that local
> variable.

I introduced that variable because the procedure conditionally sets
fontname if it's an empty sequence. As it stands, the procedure would
error without capturing that variable ahead of time due to `length' being
called on a font object.

I figured this was the simplest way around that problem. Do you have an
easier way in mind? I could perhaps change the setq line to instead set
fontname to (face-attribute 'default :family), which would allow for
removing the local variable safely.




This bug report was last modified 7 years and 282 days ago.

Previous Next


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