GNU bug report logs - #6803
24.0.50; pc-selection-mode no longer plays nice with dired (or vice versa)

Previous Next

Full log

View this message in rfc822 format

From: Tim Van Holder <tim.vanholder <at> gmail.com>
To: Juanma Barranquero <lekktu <at> gmail.com>
Cc: 6803 <at> debbugs.gnu.org
Subject: bug#6803: 24.0.50; pc-selection-mode no longer plays nice with  dired (or vice versa)
Date: Fri, 6 Aug 2010 08:49:57 +0200

On 5 August 2010 22:41, Juanma Barranquero <lekktu <at> gmail.com> wrote:
> On Thu, Aug 5, 2010 at 13:07, Tim Van Holder <tim.vanholder <at> gmail.com> wrote:
>> Dired normally has the up and down arrows bound to dired-previous-line
>> (also bound to [p]) and dired-next-line (also bound to [n]), respectively.
>> However, when pc-selection-mode is enabled, these bindings are
>> apparently overridden now, to previous-line-nomark and next-line-nomark,
>> respectively, breaking the normal dired navigation (point is not
>> automatically put on the file name).
>> Looking at 'C-h m' for dired in an older emacs version (a 23.0.60.1
>> build) and today's bzr head, the cause seems to be that while the older
>> dired explicitly bound <up> and <down>, the current dired seems to rely
>> on remapping <next-line> and <previous-line> instead.
>
> Right, this is a consequence of bug#6632 and revno:100864.
>
> Perhaps it should be reverted, but then, the use case mentioned in the
> bug will still be there.
>
> Opinions?
>
>     Juanma

Do dired-next/previous-line set the mark? If not (or if it's likely
that the distinction does not really matter in dired mode), I suppose
dired could just remap the -nomark variants of next/previous-line too.
If it does, maybe it could add -nomark variants of its own functions?

Previous Next

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