From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, miles@gnu.org
Subject: Re: need option so line-move-to-column ignores fields, plus patch
Date: Mon, 04 Sep 2006 13:18:08 -0400 [thread overview]
Message-ID: <E1GKI5I-00007g-RO@fencepost.gnu.org> (raw)
In-Reply-To: <2cd46e7f0609032143v311b670dra2d2ef679dd936@mail.gmail.com> (ken.manheimer@gmail.com)
> So, can we find specific cases where some other incompatible behavior
> is positively desirable? It would be useful for people to look
> for the other facilities that use fields, to see what cases there are
> where we would not want this behavior.
i don't expect line-move-ignore-fields to be used everywhere, or even
as the default.
I am looking for a way to avoid the need for such an option,
a way to make the command DTRT for everyone without need for
parameters. And I think I have found one.
I would like people to help me check whether this solution really works.
i would want motion from the structure (left-hand)
side of a line (corresponding to the minibuffer's prompt), to another
line with structure, to remain in the structure side if the columns
line up.
Since the minibuffer has only one prompt, this case cannot occur
in the minibuffer. Therefore, if we make C-n and C-p do this,
the change need not have any effect on the minibuffer.
So far I see no problem with my proposal as modified by your request.
But what about comint? It uses fields for the prompts, right?
Would this behavior be right for comint?
offhand, that policy is not what i prefer, however. i do not see it
necessary to retain the cursor within the structure area or the
content area when moving between lines.
In that case, what behavior WOULD you prefer?
next prev parent reply other threads:[~2006-09-04 17:18 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 15:48 need option so line-move-to-column ignores fields, plus patch Ken Manheimer
2006-08-31 16:25 ` Ken Manheimer
2006-08-31 17:11 ` David Kastrup
2006-08-31 22:57 ` Richard Stallman
2006-09-01 4:17 ` Miles Bader
2006-09-01 6:39 ` Ken Manheimer
2006-09-03 15:17 ` Richard Stallman
2006-09-04 4:43 ` Ken Manheimer
2006-09-04 17:18 ` Richard Stallman [this message]
2006-09-04 19:56 ` Ken Manheimer
2006-09-06 8:49 ` Richard Stallman
2006-09-06 16:52 ` Ken Manheimer
2006-09-07 6:54 ` Richard Stallman
2006-09-07 14:47 ` Ken Manheimer
2006-09-23 23:29 ` Ken Manheimer
2006-09-24 16:28 ` Richard Stallman
2006-09-24 20:17 ` Ken Manheimer
2006-09-25 20:48 ` Richard Stallman
2006-09-24 22:04 ` Chong Yidong
2006-09-24 22:10 ` Chong Yidong
2006-09-25 1:53 ` Ken Manheimer
2006-10-11 4:13 ` Ken Manheimer
2006-10-11 18:50 ` Richard Stallman
2006-10-11 19:19 ` Ken Manheimer
2006-10-12 22:37 ` Richard Stallman
2006-09-25 1:31 ` Ken Manheimer
2006-09-25 8:36 ` Slawomir Nowaczyk
2006-09-25 20:48 ` Richard Stallman
2006-09-25 21:43 ` Chong Yidong
2006-09-27 17:18 ` Ken Manheimer
2006-09-29 16:32 ` Richard Stallman
2006-09-29 18:21 ` Chong Yidong
2006-09-07 6:54 ` Richard Stallman
2006-09-07 14:27 ` Ken Manheimer
2006-09-05 4:48 ` Miles Bader
2006-09-01 6:30 ` Ken Manheimer
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=E1GKI5I-00007g-RO@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=miles@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 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).