From: "Alfred M. Szmidt" <ams@gnu.org>
To: Eduardo Ochs <eduardoochs@gmail.com>
Cc: thievol@posteo.net, raman@google.com, eller.helmut@gmail.com,
tino.calancha@gmail.com, emacs-devel@gnu.org
Subject: Re: Please, Restore Previous Behavior for jump-to-register
Date: Sun, 10 Dec 2023 03:28:17 -0500 [thread overview]
Message-ID: <E1rCFAf-0002gX-Sd@fencepost.gnu.org> (raw)
In-Reply-To: <CADs++6iGpaxcvUJPinwsM1b23THbXO+3dBQaCPo3gQQ5ptWqSA@mail.gmail.com> (message from Eduardo Ochs on Sun, 10 Dec 2023 02:44:22 -0300)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
The old behavior is to not ask for confirmation when overwriting a
register, and some people - including me - would like to have a simple
way to make `C-x r SPC' (`point-to-register') behave in the old way...
Is there a way to do that by just setting variables?
If not, can you implement a way to do that?
More importantly, the documentation for how registers behave is out of
sync with this new behaviour. The old behaviour should really be made
default until.
‘C-x r <SPC> R’
Record the position of point and the current buffer in register R
(‘point-to-register’).
‘C-x r j R’
Jump to the position and buffer saved in register R
(‘jump-to-register’).
Typing ‘C-x r <SPC>’ (‘point-to-register’), followed by a character
‘R’, saves both the position of point and the current buffer in register
R. The register retains this information until you store something else
in it.
next prev parent reply other threads:[~2023-12-10 8:28 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 10:02 Please, Restore Previous Behavior for jump-to-register Tino Calancha
2023-12-08 13:48 ` Helmut Eller
2023-12-08 15:19 ` Eduardo Ochs
2023-12-08 20:35 ` T.V Raman
2023-12-08 20:45 ` Eduardo Ochs
2023-12-09 6:58 ` Thierry Volpiatto
2023-12-09 16:40 ` T.V Raman
2023-12-10 1:58 ` Eduardo Ochs
2023-12-10 5:15 ` Thierry Volpiatto
2023-12-10 5:44 ` Eduardo Ochs
2023-12-10 8:28 ` Alfred M. Szmidt [this message]
2023-12-10 9:31 ` Eli Zaretskii
2023-12-10 9:47 ` Alfred M. Szmidt
2023-12-10 9:37 ` João Távora
2023-12-10 9:45 ` Eli Zaretskii
2023-12-10 6:02 ` Teemu Likonen
2023-12-10 8:21 ` Alfred M. Szmidt
2023-12-10 10:14 ` Rudolf Schlatte
2023-12-10 11:18 ` Andreas Schwab
2023-12-10 11:30 ` Alfred M. Szmidt
2023-12-10 12:34 ` Eduardo Ochs
2023-12-10 14:57 ` Eli Zaretskii
2023-12-10 16:26 ` Daniel Colascione
2023-12-10 16:57 ` Thierry Volpiatto
2023-12-10 17:27 ` Rudolf Schlatte
2023-12-10 17:33 ` Thierry Volpiatto
2023-12-10 17:46 ` Thierry Volpiatto
2023-12-10 19:20 ` João Távora
2023-12-10 19:44 ` T.V Raman
2023-12-10 20:08 ` João Távora
2023-12-10 20:30 ` Alfred M. Szmidt
2023-12-10 20:37 ` João Távora
2023-12-11 0:54 ` T.V Raman
2023-12-11 5:58 ` Alfred M. Szmidt
2023-12-11 12:27 ` Eli Zaretskii
2023-12-11 18:16 ` Dmitry Gutov
2023-12-11 20:04 ` Colin Baxter
2023-12-12 5:31 ` Po Lu
2023-12-12 5:43 ` Alfred M. Szmidt
2023-12-12 10:05 ` João Távora
2023-12-14 7:48 ` Eli Zaretskii
2023-12-14 15:16 ` Alfred M. Szmidt
2023-12-14 15:31 ` João Távora
2023-12-14 15:34 ` T.V Raman
2023-12-14 15:45 ` Dmitry Gutov
2023-12-14 16:22 ` João Távora
2023-12-14 16:32 ` João Távora
2023-12-14 16:39 ` Ihor Radchenko
2023-12-14 17:52 ` [External] : " Drew Adams
2023-12-14 20:17 ` Stefan Kangas
2023-12-14 20:56 ` João Távora
2023-12-14 22:54 ` Drew Adams
2023-12-14 23:06 ` João Távora
2023-12-14 23:08 ` Dmitry Gutov
2023-12-15 0:27 ` Adam Porter
2023-12-14 22:53 ` Drew Adams
2023-12-16 22:15 ` Merging bookmark+ features into Emacs itself Stefan Kangas
2023-12-16 23:07 ` [External] : " Drew Adams
2023-12-15 15:02 ` [External] : Re: Please, Restore Previous Behavior for jump-to-register T.V Raman
2023-12-14 16:57 ` Eli Zaretskii
2023-12-14 17:53 ` [External] : " Drew Adams
2023-12-14 16:53 ` Eli Zaretskii
2023-12-14 17:10 ` Alfred M. Szmidt
2023-12-14 17:20 ` Eli Zaretskii
2023-12-14 17:35 ` Alfred M. Szmidt
2023-12-14 17:53 ` [External] : " Drew Adams
2023-12-14 17:50 ` Drew Adams
2023-12-14 15:55 ` Alfred M. Szmidt
2023-12-14 17:48 ` [External] : " Drew Adams
2023-12-14 16:52 ` Eli Zaretskii
2023-12-14 17:01 ` Alfred M. Szmidt
2023-12-14 17:07 ` Eli Zaretskii
2023-12-14 17:10 ` Alfred M. Szmidt
2023-12-14 17:25 ` Eli Zaretskii
2023-12-14 18:05 ` Alfred M. Szmidt
2023-12-14 18:57 ` Eli Zaretskii
2023-12-14 20:20 ` Stefan Kangas
2023-12-14 20:48 ` Alfred M. Szmidt
2023-12-14 16:48 ` Eli Zaretskii
2023-12-14 17:01 ` Alfred M. Szmidt
2023-12-14 17:11 ` Eli Zaretskii
2023-12-14 17:35 ` Alfred M. Szmidt
2023-12-14 20:23 ` Stefan Kangas
2023-12-14 20:48 ` Alfred M. Szmidt
2023-12-10 19:25 ` Alfred M. Szmidt
2023-12-10 21:07 ` Eduardo Ochs
2023-12-08 15:32 ` [External] : " Drew Adams
2023-12-08 16:36 ` Eli Zaretskii
2023-12-08 18:41 ` [External] : " Drew Adams
2023-12-08 14:28 ` James Thomas
2023-12-13 13:00 ` João Pedro
2023-12-16 4:22 ` Richard Stallman
2023-12-16 10:28 ` Jean Louis
2023-12-16 20:19 ` Eli Zaretskii
2023-12-16 22:03 ` João Pedro
2023-12-18 4:13 ` Richard Stallman
2023-12-14 8:22 ` Protesilaos Stavrou
2023-12-14 17:01 ` Alfred M. Szmidt
2023-12-14 20:27 ` Stefan Kangas
2023-12-14 21:50 ` Rudolf Adamkovič
2023-12-15 9:22 ` Steve Perry
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=E1rCFAf-0002gX-Sd@fencepost.gnu.org \
--to=ams@gnu.org \
--cc=eduardoochs@gmail.com \
--cc=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=raman@google.com \
--cc=thievol@posteo.net \
--cc=tino.calancha@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).