GNU bug report logs - #16740
24.2; Please allow C-p and C-n in minibuffer

Previous Next

Package: emacs;

Reported by: Ed Avis <eda <at> waniasset.com>

Date: Thu, 13 Feb 2014 11:05:02 UTC

Severity: wishlist

Tags: moreinfo

Found in version 24.2

Done: Stefan Kangas <stefan <at> marxist.se>

Bug is archived. No further changes may be made.

Forwarded to https://lists.gnu.org/archive/html/bug-bash/2014-02/msg00045.html

Full log


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

From: Stefan Kangas <stefan <at> marxist.se>
To: Juri Linkov <juri <at> linkov.net>
Cc: Lars Ingebrigtsen <larsi <at> gnus.org>, Ed Avis <eda <at> waniasset.com>,
 16740-done <at> debbugs.gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: Re: bug#16740: 24.2; Please allow C-p and C-n in minibuffer
Date: Tue, 28 Dec 2021 19:05:25 -0800
Juri Linkov <juri <at> linkov.net> writes:

>>> Before closing, we need to decide whether to bind C-p and C-n
>>> to the same commands that were bound in 2014 to [up] and [down],
>>> i.e. whether to apply such patch:
>> [...]
>>>    (define-key map [down]  'next-line-or-history-element)
>>> +  (define-key map "\C-n"  'next-line-or-history-element)
>>
>> If I remember correctly, I think the idea was to have a way for the user
>> to skip the nice magical DWIM stuff that's on up/down, so C-n/C-p was
>> left alone on purpose.  And I think that's still the right decision.
>
> This was my recollection too.  So if no one has new arguments
> to change this decision, this request could be closed.

OK, closing.




This bug report was last modified 3 years and 223 days ago.

Previous Next


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