From: Eli Zaretskii <eliz@gnu.org>
To: arthur miller <arthur.miller@live.com>
Cc: emacs-devel@gnu.org
Subject: Re: Suggestion: two new commands: beginning-of-list and end-of-list
Date: Tue, 10 Sep 2024 18:48:32 +0300 [thread overview]
Message-ID: <86plpbtsq7.fsf@gnu.org> (raw)
In-Reply-To: <AS8PR02MB10107A5DFA8AD0445297A8F1D969A2@AS8PR02MB10107.eurprd02.prod.outlook.com> (message from arthur miller on Tue, 10 Sep 2024 15:10:26 +0000)
> From: arthur miller <arthur.miller@live.com>
> CC: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
> Date: Tue, 10 Sep 2024 15:10:26 +0000
>
> >> I think it makes sense to keep backward-up-list as it is, since it handles
> >> literal strings as it does. But the behaviour is controlled via special vars
> >> esape-strings and no-syntax-crossing. If we want similar command as
> >> beginning-of-string, we have to wrap it and let-bind those variables to
> >> change how it works.
> >
> >Yes, but is that a problem?
>
> Everyone who would like to customize it has to write their own.
Why would someone want to customize a command that does its job well?
> >The converse of C-M-u is C-M-d, but it doesn't move to the end of a
> >list, it moves _inside_ one level.
>
> Down-list? I don't think it is close to the end-of-list.
Try it on a deeply-nested list, and you will see the difference.
next prev parent reply other threads:[~2024-09-10 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 18:32 Suggestion: two new commands: beginning-of-list and end-of-list arthur miller
2024-09-09 19:11 ` Eli Zaretskii
2024-09-09 19:41 ` Sv: " arthur miller
2024-09-09 19:41 ` arthur miller
2024-09-10 11:30 ` Eli Zaretskii
2024-09-10 15:10 ` Sv: " arthur miller
2024-09-10 15:48 ` Eli Zaretskii [this message]
2024-09-11 5:39 ` arthur miller
2024-09-12 4:24 ` Emanuel Berg
2024-09-11 3:17 ` Sv: " Karthik Chikmagalur
2024-09-11 5:48 ` Sv: " arthur miller
2024-09-10 12:05 ` Yuri Khan
-- strict thread matches above, loose matches on Subject: below --
2024-09-13 13:30 arthur miller
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=86plpbtsq7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arthur.miller@live.com \
--cc=emacs-devel@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).