GNU bug report logs - #19916
24.4; rmail-summary-next-msg declares argument incorrectly

Previous Next

Package: emacs;

Reported by: schule <at> fsavigny.de (Florian v. Savigny)

Date: Sat, 21 Feb 2015 20:41:02 UTC

Severity: minor

Found in version 24.4

Fixed in version 25.1

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 19916 in the body.
You can then email your comments to 19916 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#19916; Package emacs. (Sat, 21 Feb 2015 20:41:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to schule <at> fsavigny.de (Florian v. Savigny):
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Sat, 21 Feb 2015 20:41:03 GMT) Full text and rfc822 format available.

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

From: schule <at> fsavigny.de (Florian v. Savigny)
To: bug-gnu-emacs <at> gnu.org
Subject: 24.4;
 rmail-summary-next-msg declares argument incorrectly
Date: Sat, 21 Feb 2015 19:17:56 +0100


As I am fairly certain that this is a bug in the source code, I am not including any of the automatic information on my system which M-x report-emacs-bug produces.

Description of the bug:  rmail-summary-next-msg declares its attribute
	       	   	 NUMBER as &optional, but does not treat it
	       	   	 like that, at least when called
	       	   	 non-interactively.

Reproducible: always

How: Calling (rmail-summary-next-msg) non-interactively.

Undesired behaviour:

	  Throws the following exception:

	  	 and: Wrong type argument: number-or-marker-p, nil

	  This is an obscure error if you have called
	  (rmail-summary-next-message) in accordance with the
	  documentation.

Explanation:	This can easily be tracked to the following line in the source
		code for the function, where it expects NUMBER to be non-nil:

		(and (> number 0) (end-of-line)) ;; line 3 after the docstring

Line 827 in the source file in the following version of rmailsum.el:
;; Copyright (C) 1985, 1993-1996, 2000-2014 Free Software Foundation,


Workaround: Calling (rmail-summary-next-msg 1) instead of using no argument.




Best regards,

Florian v. Savigny
Reply sent to Glenn Morris <rgm <at> gnu.org>:
You have taken responsibility. (Tue, 24 Feb 2015 07:45:02 GMT) Full text and rfc822 format available.
Notification sent to schule <at> fsavigny.de (Florian v. Savigny):
bug acknowledged by developer. (Tue, 24 Feb 2015 07:45:02 GMT) Full text and rfc822 format available.

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

From: Glenn Morris <rgm <at> gnu.org>
To: 19916-done <at> debbugs.gnu.org
Subject: Re: bug#19916: 24.4;
 rmail-summary-next-msg declares argument incorrectly
Date: Tue, 24 Feb 2015 02:44:26 -0500

Version: 25.1

Thanks; fixed.
bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Tue, 24 Mar 2015 11:24:04 GMT) Full text and rfc822 format available.
This bug report was last modified 10 years and 146 days ago.

Previous Next

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