From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Dani Moncayo <dmoncayo@gmail.com>
Cc: "17346@debbugs.gnu.org" <17346@debbugs.gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#17346: 24.4.50; Why is the goal column limited to C-n and C-p ?
Date: Sat, 30 Apr 2022 16:11:41 +0000 [thread overview]
Message-ID: <SJ0PR10MB54883DB7185869D190DE4F61F3FF9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87wnf6zite.fsf@gnus.org>
> On the other hand, I think anybody's who has done a `C-x C-n' would
> want <prior> and <next> to also respect the goal column, really.
Why would you assume that?
> So I think I'd be in favour of just changing the behaviour here.
>
> Does anybody else have an opinion?
Can users not, themselves, get this behavior for
anything they like? Can't they define a command
that does what `scroll-up-command` (or whatever)
does but also respects the goal column?
If you want to provide a user options that makes
some particular set of commands respect the goal
column, then do so. The option value could be a
list of such commands.
Alternatively, users could maybe put some property
on the command symbol to indicate this.
However you might want to implement such a feature,
it should (1) be opt in and (2) let users control
the set of affected commands.
next prev parent reply other threads:[~2022-04-30 16:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 11:29 bug#17346: 24.4.50; Why is the goal column limited to C-n and C-p ? Dani Moncayo
2014-04-25 14:43 ` Dani Moncayo
2014-04-25 16:14 ` Stefan Monnier
2014-04-29 6:25 ` Dani Moncayo
2014-04-29 21:54 ` Stefan Monnier
2014-05-29 15:10 ` Dani Moncayo
2014-10-09 7:24 ` Dani Moncayo
2014-10-09 15:44 ` Stefan Monnier
2014-10-09 16:03 ` Dani Moncayo
2014-10-09 16:30 ` Dani Moncayo
2014-10-09 19:45 ` Stefan Monnier
2014-10-09 20:43 ` Dani Moncayo
2014-10-09 21:12 ` Stefan Monnier
2014-10-09 21:32 ` Dani Moncayo
2014-10-10 1:09 ` Stefan Monnier
2014-10-09 16:57 ` Stefan Monnier
2022-04-30 15:34 ` Lars Ingebrigtsen
2022-04-30 16:11 ` Drew Adams [this message]
2022-06-05 19:37 ` Lars Ingebrigtsen
2022-06-05 22:56 ` Drew Adams
2014-04-25 16:20 ` Michael Welsh Duggan
2014-04-25 16:49 ` Dani Moncayo
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=SJ0PR10MB54883DB7185869D190DE4F61F3FF9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=17346@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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).