From: Markus Triska <triska@metalevel.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 66313-done@debbugs.gnu.org
Subject: bug#66313: Acknowledgement (29.1.50; process-mark sometimes does not yield the expected value)
Date: Sat, 07 Oct 2023 17:28:32 +0200 [thread overview]
Message-ID: <87sf6mv4db.fsf@metalevel.at> (raw)
In-Reply-To: <83ttr2zd8g.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 07 Oct 2023 18:03:27 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> I fixed this on the emacs-29 branch
Thank you! I now found the related issue #43573, where Lars states:
"If this breaks anything (and that is possible -- somebody could be
using `process-mark' as a weird way to keep track of what the
previous buffer was -- it should be reverted."
Also, I found commit 7b3e94b6648ed00c6948c09267894b548b2868e7, where the
following (then) new piece of documentation was added to processes.texi:
if non-@code{nil}, the process mark will be
set to point to the end of @var{buffer}.
When I wrote ediprolog.el, this was not documented as such.
Is the behaviour now consistent with the documentation, or must the
documentation or behaviour be changed? Should the change introduced in
#43573 be reverted as indicated above, because it broke something?
Thank you and all the best,
Markus
next prev parent reply other threads:[~2023-10-07 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 20:00 bug#66313: 29.1.50; process-mark sometimes does not yield the expected value Markus Triska
[not found] ` <handler.66313.B.169627630221147.ack@debbugs.gnu.org>
2023-10-07 14:15 ` bug#66313: Acknowledgement (29.1.50; process-mark sometimes does not yield the expected value) Markus Triska
2023-10-07 15:03 ` Eli Zaretskii
2023-10-07 15:28 ` Markus Triska [this message]
2023-10-07 15:56 ` Eli Zaretskii
2023-10-07 16:12 ` Markus Triska
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sf6mv4db.fsf@metalevel.at \
--to=triska@metalevel.at \
--cc=66313-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.