GNU bug report logs - #44341
27.1; define-minor-mode generates inaccurate docstring

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Philipp Stephani <p.stephani2 <at> gmail.com>
Cc: 44341 <at> debbugs.gnu.org, thibault <at> thb.lt, monnier <at> iro.umontreal.ca
Subject: Re: bug#44341: 27.1; define-minor-mode generates inaccurate docstring
Date: Mon, 02 Nov 2020 17:52:38 +0200

> From: Philipp Stephani <p.stephani2 <at> gmail.com>
> Date: Mon, 2 Nov 2020 13:28:06 +0100
> Cc: 44341 <at> debbugs.gnu.org, Thibault Polge <thibault <at> thb.lt>
> 
> Am So., 1. Nov. 2020 um 16:30 Uhr schrieb Stefan Monnier
> <monnier <at> iro.umontreal.ca>:
> 
> > >     disable ; Should disable (as a random symbol)
> > >     disable ; Again
> > >     "What?" ; Same.
> >
> > These should be considered as errors.  Whether we catch them and signal
> > an error or silently do something else is not particular important
> > to me.
> 
> We should definitely signal an error here. A form such as (my-mode
> 'enable) actually disabling the mode is very confusing.

Signaling an error would be an incompatible change.  Someone who has

  (my-mode 'disable)

in their Lisp code will complain that it makes perfect sense.

I object to making incompatible changes in this area; let's fix the
problems wrt documentation, but it's too late to introduce
incompatible changes into this stuff, which is used all over, in Emacs
and elsewhere.  Wed already had the first bug report about such
incompatible changes, less than a day after it was pushed.  I'm quite
certain that incompatible change was unintended, but here you propose
to make it quite intentionally, and that would be a serious mistake,
IMO.

Previous Next

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