GNU bug report logs - #22210
25.0.50; display-message-or-buffer docstring refers to wrong argument in display-buffer

Previous Next

Package: emacs;

Reported by: Sebastian Wiesner <swiesner <at> lunaryorn.com>

Date: Sat, 19 Dec 2015 09:17:02 UTC

Severity: normal

Found in version 25.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #13 received at 22210-done <at> debbugs.gnu.org (full text, mbox):

From: Sebastian Wiesner <swiesner <at> lunaryorn.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 22210-done <at> debbugs.gnu.org
Subject: Re: bug#22210: 25.0.50;
 display-message-or-buffer docstring refers to wrong argument in
 display-buffer
Date: Sat, 19 Dec 2015 12:40:28 +0100
Am 19.12.2015 um 12:35 schrieb Eli Zaretskii <eliz <at> gnu.org>:

>> From: Sebastian Wiesner <swiesner <at> lunaryorn.com>
>> Date: Sat, 19 Dec 2015 10:15:56 +0100
>> 
>> The docstring of `display-message-or-buffer' reads as follows:
>> 
>> ----
>> 
>> (display-message-or-buffer MESSAGE &optional BUFFER-NAME NOT-THIS-WINDOW FRAME)
>> 
>> […]
>> 
>> Optional arguments NOT-THIS-WINDOW and FRAME are as for ‘display-buffer’,
>> and only used if a buffer is displayed.
>> 
>> ----
>> 
>> However, display-buffer does not actually have a NOT-THIS-WINDOW argument:
>> 
>> (display-buffer BUFFER-OR-NAME &optional ACTION FRAME)
>> 
>> The source of display-message-or-buffer reveals that NOT-THIS-WINDOW is actually 
>> passed in the ACTION argument.
>> 
>> I think the argument of display-message-or-buffer should be renamed to ACTION 
>> as well.
> 
> Thanks, fixed.

Thank you for the quick fix.  Besides, I noticed that the same issue is also in the Emacs Lisp reference.



This bug report was last modified 9 years and 234 days ago.

Previous Next


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