unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Mon, 09 Jan 2023 14:09:43 +0200	[thread overview]
Message-ID: <83cz7nq588.fsf@gnu.org> (raw)
In-Reply-To: <f1b503c5-3f3a-7a5e-8b2b-b72445f13908@gmail.com> (message from Jim Porter on Sun, 8 Jan 2023 15:34:03 -0800)

> Date: Sun, 8 Jan 2023 15:34:03 -0800
> From: Jim Porter <jporterbugs@gmail.com>
> 
> Attached are some patches to do this. Aside from the user-facing change 
> that the Home key works like C-a now, this also means that users don't 
> have to set 'eshell-prompt-regexp' anymore (unless they want to use 
> paragraph navigation, that is). In fact, maybe it would be better to map 
> M-{ and M-} to 'eshell-prompt-(previous|next)'. That would have the same 
> effect as '(backward|forward)-paragraph' (I think), but it would be more 
> robust.
> 
> Any thoughts here?

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.





  reply	other threads:[~2023-01-09 12:09 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 [this message]
2023-01-09 17:52   ` Jim Porter
2023-01-10 12:13     ` Eli Zaretskii
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=83cz7nq588.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).