all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Chris Moore" <christopher.ian.moore@gmail.com>
To: emacs-pretest-bug@gnu.org
Subject: wdired-use-dired-vertical-movement docstring improvements
Date: Mon, 5 Nov 2007 10:56:17 +0100	[thread overview]
Message-ID: <a9691ee20711050156i16c9065fke54bd8b6a45b403a@mail.gmail.com> (raw)

`sometimes' is missing its closing quote, and the docstring talks
about "if `track-eol' is honored" - well, isn't it always honored,
like all variables are?  Here's a patch.  Note that the docstring
still isn't quite right, because track-eol seems to have no effect on
the behavior.  Well, I have it set to the default 'nil' and
`sometimes' still works for me.

Chris.

*** a/wdired.el	Mon Nov  5 10:51:32 2007
--- b/wdired.el	Mon Nov  5 10:52:21 2007
***************
*** 130,137 ****
    "If t, the \"up\" and \"down\" movement works as in Dired mode.
  That is, always move the point to the beginning of the filename at line.

! If `sometimes, only move to the beginning of filename if the point is
! before it, and `track-eol' is honored.  This behavior is very handy
  when editing several filenames.

  If nil, \"up\" and \"down\" movement is done as in any other buffer."
--- 130,137 ----
    "If t, the \"up\" and \"down\" movement works as in Dired mode.
  That is, always move the point to the beginning of the filename at line.

! If `sometimes', only move to the beginning of filename if the point is
! before it, and `track-eol' is non-nil.  This behavior is very handy
  when editing several filenames.

  If nil, \"up\" and \"down\" movement is done as in any other buffer."

             reply	other threads:[~2007-11-05  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-05  9:56 Chris Moore [this message]
2007-11-05 11:51 ` wdired-use-dired-vertical-movement docstring improvements Thien-Thi Nguyen
2007-11-06  2:15 ` Richard Stallman
2007-11-10  5:04   ` Chris Moore

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=a9691ee20711050156i16c9065fke54bd8b6a45b403a@mail.gmail.com \
    --to=christopher.ian.moore@gmail.com \
    --cc=emacs-pretest-bug@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.