From: Tim Van Holder <tim.vanholder@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 6803@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 [thread overview]
Message-ID: <AANLkTinsTrsMaHL2vZ+ozpTiBBciEpecqaKLzHhdYEY=@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinLEL5y=m-MkbSZYvnzTkxTE1HmsSOnTjoyNnsd@mail.gmail.com>
On 5 August 2010 22:41, Juanma Barranquero <lekktu@gmail.com> wrote:
> On Thu, Aug 5, 2010 at 13:07, Tim Van Holder <tim.vanholder@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?
next prev parent reply other threads:[~2010-08-06 6:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 11:07 bug#6803: 24.0.50; pc-selection-mode no longer plays nice with dired (or vice versa) Tim Van Holder
2010-08-05 20:41 ` Juanma Barranquero
2010-08-06 6:49 ` Tim Van Holder [this message]
2021-07-18 12:57 ` Lars Ingebrigtsen
2021-08-16 12:12 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTinsTrsMaHL2vZ+ozpTiBBciEpecqaKLzHhdYEY=@mail.gmail.com' \
--to=tim.vanholder@gmail.com \
--cc=6803@debbugs.gnu.org \
--cc=lekktu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).