all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim Van Holder <tim.vanholder@gmail.com>
To: 6803@debbugs.gnu.org
Subject: bug#6803: 24.0.50; pc-selection-mode no longer plays nice with dired (or vice versa)
Date: Thu, 05 Aug 2010 13:07:02 +0200	[thread overview]
Message-ID: <871vadl3mx.fsf@leeloo.anubex.internal> (raw)

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.

In GNU Emacs 24.0.50.10 (i686-pc-linux-gnu, GTK+ Version 2.8.20)
 of 2010-08-05 on leeloo
Windowing system distributor `The Cygwin/X Project', version 11.0.10503000
configured using `configure  '--with-x''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: en_US.UTF-8
  value of $XMODIFIERS: nil
  locale-coding-system: utf-8-unix
  default enable-multibyte-characters: t





             reply	other threads:[~2010-08-05 11:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-05 11:07 Tim Van Holder [this message]
2010-08-05 20:41 ` bug#6803: 24.0.50; pc-selection-mode no longer plays nice with dired (or vice versa) Juanma Barranquero
2010-08-06  6:49   ` Tim Van Holder
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871vadl3mx.fsf@leeloo.anubex.internal \
    --to=tim.vanholder@gmail.com \
    --cc=6803@debbugs.gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.