From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 60666@debbugs.gnu.org
Subject: bug#60666: 30.0.50; [PATCH] Use field properties in Eshell buffers
Date: Tue, 10 Jan 2023 14:13:46 +0200 [thread overview]
Message-ID: <83o7r6oadh.fsf@gnu.org> (raw)
In-Reply-To: <537ece85-8808-c7fa-71b0-c355ff3740bb@gmail.com> (message from Jim Porter on Mon, 9 Jan 2023 09:52:53 -0800)
> Date: Mon, 9 Jan 2023 09:52:53 -0800
> Cc: 60666@debbugs.gnu.org
> From: Jim Porter <jporterbugs@gmail.com>
>
> On 1/9/2023 4:09 AM, Eli Zaretskii wrote:
> > The only thought I have is "what if anyone _does_ like Home to do what
> > it does now?" So this change should have a NEWS ebtry about the
> > incompatible changes, and a recipe for how to get back the old
> > behavior for those who want it.
>
> Thanks, that makes sense. I've added a NEWS entry to the first part (see
> attached). The recipe seems like it's on the edge of what would be
> reasonable for users to paste into their configs though. I don't have a
> strong opinion here, but if you think the recipe is too long, maybe we
> could add the 'move-beginning-of-line-ignoring-fields' function to
> simple.el. It might possibly be useful for some small number of people
> who want to selectively disable field text motion.
I don't think I understand why keeping eshell-bol and telling people
to bind <HOME> to that function if they want wouldn't be a much more
reasonable solution. I'm probably missing something.
Adding a function that is used in just two places doesn't sound TRT to
me.
next prev parent reply other threads:[~2023-01-10 12:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 23:34 bug#60666: 30.0.50; [PATCH] Use field properties in Eshell buffers Jim Porter
2023-01-09 12:09 ` Eli Zaretskii
2023-01-09 17:52 ` Jim Porter
2023-01-10 12:13 ` Eli Zaretskii [this message]
2023-01-10 19:28 ` Jim Porter
2023-01-10 20:11 ` Eli Zaretskii
2023-01-10 20:51 ` Jim Porter
2023-01-11 12:15 ` Eli Zaretskii
2023-01-12 18:10 ` Jim Porter
2023-01-13 13:07 ` Eli Zaretskii
2023-01-14 19:30 ` Jim Porter
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=83o7r6oadh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60666@debbugs.gnu.org \
--cc=jporterbugs@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).