From: Lars Ingebrigtsen <larsi@gnus.org>
To: Tom Tromey <tromey@redhat.com>
Cc: 16050@debbugs.gnu.org
Subject: bug#16050: 24.3; let copy-to-register choose default location of point for insert-register
Date: Tue, 10 May 2022 17:59:36 +0200 [thread overview]
Message-ID: <875ymdfkev.fsf@gnus.org> (raw)
In-Reply-To: <87y540r8df.fsf@fleche.redhat.com> (Tom Tromey's message of "Wed, 04 Dec 2013 07:36:12 -0700")
Tom Tromey <tromey@redhat.com> writes:
> I sometimes use registers for repetitive insertion of text.
>
> Sometimes I want point to end up at the end of the insertion.
> I know I can do this with a prefix argument, but it would be nicer if I
> could specify this automatically for a given register, say when creating
> the contents.
>
> For example, when I invoke copy-to-register, if point is at the end of
> the region, then that could indicate that I want point to be at the end
> of the region at insertion time.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
I don't think we can change the behaviour of these commands, because
that would be annoying to many users that are used to the current way
they work.
> Or, perhaps a prefix argument to copy-to-register would work ok as well.
Unfortunately, the prefix argument is already taken there.
In addition, "remembering" this data is kinda tricky -- we allow saving
registers to file, and we'd have to extend the on-file format, etc.
Everything's possible with a little programming, of course, but the
interface problems are more difficult -- I don't immediately see any
good way for the user to specify that it's a point-at-the-end register.
We could add a special command for that, but...
Hm... perhaps we could make `C-u' for insert-register "sticky" for that
register? That is, if you `C-u C-x r i a', then that "a" register would
keep that behaviour for the rest of the session (until toggled off with
a subsequent `C-u C-x r i a', perhaps).
But that's a pretty convoluted interface, and changes the current
behaviour.
Anybody got any ideas here?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-10 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 14:36 bug#16050: 24.3; let copy-to-register choose default location of point for insert-register Tom Tromey
2022-05-10 15:59 ` Lars Ingebrigtsen [this message]
2022-06-09 14:10 ` Lars Ingebrigtsen
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=875ymdfkev.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=16050@debbugs.gnu.org \
--cc=tromey@redhat.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).