GNU bug report logs - #12644
24.2.50; Doc fix

Previous Next

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

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

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

From: Dani Moncayo <dmoncayo <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.2.50; Doc fix
Date: Sun, 14 Oct 2012 12:38:09 +0200

Here is a couple of fixes for the Emacs Manual.


=== modified file 'doc/emacs/mini.texi'
--- doc/emacs/mini.texi 2012-10-06 14:18:03 +0000
+++ doc/emacs/mini.texi 2012-10-12 21:50:07 +0000
@@ -550,7 +550,7 @@
 completion command replaces that with the next completion alternative,
 in a cyclic manner.  If you give @code{completion-cycle-threshold} a
 numeric value @var{n}, completion commands switch to this cycling
-behavior only when there are fewer than @var{n} alternatives.
+behavior only when there are @var{n} or fewer alternatives.

 @cindex Icomplete mode
 @findex icomplete-mode
@@ -689,8 +689,8 @@
   Once inside the minibuffer for @kbd{C-x @key{ESC} @key{ESC}}, you
 can use the usual minibuffer history commands (@pxref{Minibuffer
 History}) to move through the history list.  After finding the desired
-previous command, you can edit its expression as usual and then repeat
-it by typing @key{RET}.
+previous command, you can edit its expression as usual and then
+execute it by typing @key{RET}.

 @vindex isearch-resume-in-command-history
   Incremental search does not, strictly speaking, use the minibuffer.


----
Note: the first hunk fixes a mistake; the second one changes "repeat"
with "execute", since if you edit the expression in the minibuffer
before executing it, you are not repeating anything, but executing a
new command.
----

In GNU Emacs 24.2.50.1 (i386-mingw-nt6.1.7601)
 of 2012-10-12 on DANI-PC
Bzr revision: 110524 jan.h.d <at> swipnet.se-20121012175039-offa3q6viik07s2v
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --with-gcc (4.7) --no-opt --enable-checking --cflags
 -I../../libs/libxpm-3.5.8/include -I../../libs/libxpm-3.5.8/src
 -I../../libs/libpng-1.4.10 -I../../libs/zlib-1.2.6
 -I../../libs/giflib-4.1.4-1/include -I../../libs/jpeg-6b-4/include
 -I../../libs/tiff-3.8.2-1/include
 -I../../libs/libxml2-2.7.8-w32-bin/include/libxml2
 -I../../libs/gnutls-3.0.16/include
 -I../../libs/libiconv-1.14-2-mingw32-dev/include'

Important settings:
  value of $LANG: en_US.UTF8
  locale-coding-system: cp1252
  default enable-multibyte-characters: t


-- 
Dani Moncayo

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

From: Glenn Morris <rgm <at> gnu.org>
To: Dani Moncayo <dmoncayo <at> gmail.com>
Cc: 12644 <at> debbugs.gnu.org
Subject: Re: bug#12644: 24.2.50; Doc fix
Date: Wed, 17 Oct 2012 12:58:06 -0400

Dani Moncayo wrote:

>  in a cyclic manner.  If you give @code{completion-cycle-threshold} a
>  numeric value @var{n}, completion commands switch to this cycling
> -behavior only when there are fewer than @var{n} alternatives.
> +behavior only when there are @var{n} or fewer alternatives.

Thanks. By experiment, you are correct; but the variable's doc and the
code comments also describe the former behaviour, so I wonder if the code
should be changed?

> -previous command, you can edit its expression as usual and then repeat
> -it by typing @key{RET}.
> +previous command, you can edit its expression as usual and then
> +execute it by typing @key{RET}.

Applied.

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

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 12644 <at> debbugs.gnu.org, Dani Moncayo <dmoncayo <at> gmail.com>
Subject: Re: bug#12644: 24.2.50; Doc fix
Date: Wed, 17 Oct 2012 16:30:30 -0400

>> in a cyclic manner.  If you give @code{completion-cycle-threshold} a
>> numeric value @var{n}, completion commands switch to this cycling
>> -behavior only when there are fewer than @var{n} alternatives.
>> +behavior only when there are @var{n} or fewer alternatives.
> Thanks. By experiment, you are correct; but the variable's doc and the
> code comments also describe the former behaviour, so I wonder if the code
> should be changed?

I don't think anybody cares about such off-by-one differences here, so
you can change the doc to match the code or vice-versa: either way
is fine.


        Stefan

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

From: Glenn Morris <rgm <at> gnu.org>
To: 12644-done <at> debbugs.gnu.org
Subject: Re: bug#12644: 24.2.50; Doc fix
Date: Wed, 17 Oct 2012 23:30:41 -0400

Version: 24.3

Stefan Monnier wrote:

> I don't think anybody cares about such off-by-one differences here, so

Doc fixes it is then.

Previous Next

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