From: Philipp Stephani <p.stephani2@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: "Emacs developers" <emacs-devel@gnu.org>,
"Daniel Martín" <mardani29@yahoo.es>
Subject: Re: Pushing the mark from a primitive like goto-char
Date: Mon, 28 Dec 2020 16:32:10 +0100 [thread overview]
Message-ID: <CAArVCkTuUevNOhi+T65r1BoObHctSx9x363dDKTUeiihcVQnGg@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmme+zxQSY75W5eMST6vCxf_7Ka562CHNKPpA8dtYZwVcA@mail.gmail.com>
Am Mo., 28. Dez. 2020 um 15:56 Uhr schrieb Stefan Kangas
<stefankangas@gmail.com>:
>
> Philipp Stephani <p.stephani2@gmail.com> writes:
>
> >> goto-char is an interactive function that has the potential to take you
> >> long distances, so it might be a good idea, for user convenience, to
> >> push the mark as a documented side effect (is it a good idea?).
> >
> > goto-char is a low-level primitive that's used pervasively in Emacs
> > Lisp code. I think that pushing the mark would be a way too drastic
> > change.
>
> Agreed.
>
> But would it perhaps make sense to push the mark only when it is called
> interactively?
I don't think we should have functions that behave significantly
differently when called interactively - too much confusion.
> Or to replace `M-g c' with a new command that also
> pushes mark?
That sounds feasible. Maybe we should then also introduce a
customization option to control the behavior.
next prev parent reply other threads:[~2020-12-28 15:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1im8mgmb7.fsf.ref@yahoo.es>
2020-12-28 12:14 ` Pushing the mark from a primitive like goto-char Daniel Martín
2020-12-28 14:17 ` Philipp Stephani
2020-12-28 14:45 ` Daniel Martín
2020-12-28 14:49 ` Eli Zaretskii
2020-12-28 14:56 ` Stefan Kangas
2020-12-28 15:32 ` Philipp Stephani [this message]
2020-12-28 16:49 ` martin rudalics
2020-12-28 17:15 ` Juri Linkov
2020-12-29 8:54 ` martin rudalics
2020-12-29 14:41 ` Stefan Kangas
2020-12-29 16:59 ` martin rudalics
2020-12-29 17:56 ` Drew Adams
2020-12-29 19:25 ` Juri Linkov
2020-12-29 19:47 ` Eli Zaretskii
2020-12-30 9:36 ` Juri Linkov
2020-12-29 19:54 ` Drew Adams
2020-12-30 9:41 ` Juri Linkov
2020-12-30 17:32 ` Drew Adams
2020-12-30 5:26 ` Richard Stallman
2020-12-31 2:43 ` Howard Melman
2021-01-05 19:06 ` Daniel Martín via "Emacs development discussions.
2021-01-05 19:17 ` Stefan Monnier
2021-01-05 19:19 ` Stefan Monnier
2021-01-05 19:52 ` Philipp Stephani
2021-01-05 20:01 ` Stefan Monnier
2021-01-05 20:29 ` Drew Adams
2021-01-06 5:12 ` Richard Stallman
2021-01-05 19:29 ` Eli Zaretskii
2021-01-05 19:53 ` Philipp Stephani
2021-01-08 19:30 ` Daniel Martín via "Emacs development discussions.
2021-01-05 19:56 ` Philipp Stephani
2021-01-06 19:26 ` Gabriel do Nascimento Ribeiro
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=CAArVCkTuUevNOhi+T65r1BoObHctSx9x363dDKTUeiihcVQnGg@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mardani29@yahoo.es \
--cc=stefankangas@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).