unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: marmot-te <marmot-te@riseup.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 43573@debbugs.gnu.org
Subject: bug#43573: 26.1; set-process-buffer doesn't create a process marker
Date: Sat, 03 Oct 2020 14:13:49 +0000	[thread overview]
Message-ID: <87wo07flcy.fsf@host.localdomain> (raw)
In-Reply-To: <87a6xfw6ef.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 950 bytes --]


On Thu, Sep 24 2020, Lars Ingebrigtsen wrote:

> marmot-te <marmot-te@riseup.net> writes:
>
>> I noticed that creating a buffer for a process with set-process-buffer
>> does not create also a marker specific to that process that can be
>> retrieved with process-mark afteward.
>
> Yes, pretty odd, but it's just a normal marker, I think, so if you want
> it to point somewhere else, you can just use do
>
> (set-marker (process-mark proc) (point-max) buffer)

Now I see it it feels so obvious :)

> However, while there is some potential for breakage here, I think it
> makes sense to have set-process-buffer do this, so I've applied it to
> Emacs 28.  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.
>
> I think that's very unlikely, but I guess we'll find out.

Ok, thanks you !

--
<:3nn~~
   <:3nn~~
      <:3nn~~

[-- Attachment #2.1: Type: text/html, Size: 1270 bytes --]

      reply	other threads:[~2020-10-03 14:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 19:44 bug#43573: 26.1; set-process-buffer doesn't create a process marker marmot-te
2020-09-24 15:17 ` Lars Ingebrigtsen
2020-10-03 14:13   ` marmot-te [this message]

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=87wo07flcy.fsf@host.localdomain \
    --to=marmot-te@riseup.net \
    --cc=43573@debbugs.gnu.org \
    --cc=larsi@gnus.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 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).