* bug#64518: 29.0.92; outline-mode sexp movement commands don't follow outline structure
@ 2023-07-07 16:21 Spencer Baugh
2023-07-07 18:19 ` Eli Zaretskii
0 siblings, 1 reply; 3+ messages in thread
From: Spencer Baugh @ 2023-07-07 16:21 UTC (permalink / raw)
To: 64518
This is more of a feature request.
Functions like C-M-f (forward-sexp) and C-M-SPC (mark-sexp) are supposed
to be configured by individual modes to behave in a way appropriate for
that mode. But outline-mode does not do this.
For example, C-M-b/C-M-f ({backward,forward}-sexp) could behave like
outline-{backward,forward}-same-level, since that's analogous to how
they behave in Lisp. C-M-SPC could behave like outline-mark-subtree.
C-M-u could back out of the current heading, up to the next level, lke
outline-up-heading. And so on.
Since these are the standard Emacs structured editing commands, it would
be good for outline-mode to customize them to have the correct
"structured" behavior. (Probably behind some defcustom, since this
would be a behavior change)
Right now they are much less useful than they could otherwise be...
^ permalink raw reply [flat|nested] 3+ messages in thread* bug#64518: 29.0.92; outline-mode sexp movement commands don't follow outline structure
2023-07-07 16:21 bug#64518: 29.0.92; outline-mode sexp movement commands don't follow outline structure Spencer Baugh
@ 2023-07-07 18:19 ` Eli Zaretskii
2023-09-07 21:32 ` Stefan Kangas
0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii @ 2023-07-07 18:19 UTC (permalink / raw)
To: Spencer Baugh; +Cc: 64518
> From: Spencer Baugh <sbaugh@janestreet.com>
> Date: Fri, 07 Jul 2023 12:21:14 -0400
>
>
> Functions like C-M-f (forward-sexp) and C-M-SPC (mark-sexp) are supposed
> to be configured by individual modes to behave in a way appropriate for
> that mode. But outline-mode does not do this.
outline-mode is not a programming-language mode, so sexp-related
commands make no sense for it. It is more related to text-mode.
Outline mode and its derivatives already have motion commands that
move in terms of headings and trees/subtrees. I see no reason to
confuse users with some kind of artificial notion of "sexps" applied
to text.
So I think your feature request is a step in the wrong direction.
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#64518: 29.0.92; outline-mode sexp movement commands don't follow outline structure
2023-07-07 18:19 ` Eli Zaretskii
@ 2023-09-07 21:32 ` Stefan Kangas
0 siblings, 0 replies; 3+ messages in thread
From: Stefan Kangas @ 2023-09-07 21:32 UTC (permalink / raw)
To: Eli Zaretskii, Spencer Baugh; +Cc: 64518
tags 64518 + wontfix
close 64518
thanks
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Spencer Baugh <sbaugh@janestreet.com>
>> Date: Fri, 07 Jul 2023 12:21:14 -0400
>>
>>
>> Functions like C-M-f (forward-sexp) and C-M-SPC (mark-sexp) are supposed
>> to be configured by individual modes to behave in a way appropriate for
>> that mode. But outline-mode does not do this.
>
> outline-mode is not a programming-language mode, so sexp-related
> commands make no sense for it. It is more related to text-mode.
>
> Outline mode and its derivatives already have motion commands that
> move in terms of headings and trees/subtrees. I see no reason to
> confuse users with some kind of artificial notion of "sexps" applied
> to text.
>
> So I think your feature request is a step in the wrong direction.
I agree, and I'm therefore closing this as wontfix. Sorry.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-09-07 21:32 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-07-07 16:21 bug#64518: 29.0.92; outline-mode sexp movement commands don't follow outline structure Spencer Baugh
2023-07-07 18:19 ` Eli Zaretskii
2023-09-07 21:32 ` Stefan Kangas
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).