From: Drew Adams <drew.adams@oracle.com>
To: Alan Schmitt <alan.schmitt@polytechnique.org>, help-gnu-emacs@gnu.org
Subject: RE: Cannot go down in dired when the file name is tool long
Date: Fri, 13 Sep 2013 09:47:25 -0700 (PDT) [thread overview]
Message-ID: <1b468a4c-4db4-4453-bbcc-f12011b9c6a7@default> (raw)
In-Reply-To: <m261u5ywiy.fsf@polytechnique.org>
> I have a strange problem with dired: if the window used is not wide
> enough, some file names may be longer than the width so they continue on
> the next line. Unfortunately in that case I cannot use the keyboard to
> go to the next file. More precisely, if I have the cursor on the file
> name before the line break, then hitting 'n' puts the cursor at the
> beginning of the file name on the same line. If I move the cursor to the
> right enough so that it goes to the part of the file name that is on the
> next line, then hitting 'n' correctly takes me to the next file.
>
> If I turn on `visual-line-mode` (which is ugly for dired) or
> truncate-lines (which is better), then things work as expected.
>
> Is there a way to have the usual wrapping and still be able to navigate
> the file? Could this be an interaction with another mode?
I don't see what you describe at all. Do you see this when starting
with `emacs -Q'? For me, that has `visual-line-mode' turned off, and
`n' acts normally in Dired.
If you see that problem with `emacs -Q', then consider reporting a bug:
`M-x report-emacs-bug'. If not, try bisecting your init file (~/.emacs)
recursively until you find the part that introduces the problem.
next prev parent reply other threads:[~2013-09-13 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 8:07 Cannot go down in dired when the file name is tool long Alan Schmitt
2013-09-13 16:47 ` Drew Adams [this message]
[not found] ` <mailman.2081.1379090869.10748.help-gnu-emacs@gnu.org>
2013-09-16 7:21 ` Alan Schmitt
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=1b468a4c-4db4-4453-bbcc-f12011b9c6a7@default \
--to=drew.adams@oracle.com \
--cc=alan.schmitt@polytechnique.org \
--cc=help-gnu-emacs@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.
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).