unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Daniel Colascione" <dancol@dancol.org>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: Daniel Colascione <dancol@dancol.org>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 1072155: Avoid duplicate entries in process-environment after re-dumping
Date: Wed, 3 Apr 2019 09:58:35 -0700	[thread overview]
Message-ID: <2f59c1ff3d4ad006c09634813e6724b8.squirrel@dancol.org> (raw)
In-Reply-To: <83h8bfe94g.fsf@gnu.org>

>> Date: Tue, 2 Apr 2019 13:11:53 -0700
>> From: "Daniel Colascione" <dancol@dancol.org>
>> Cc: "Daniel Colascione" <dancol@dancol.org>,
>>  emacs-devel@gnu.org
>>
>> >> Don't we want to reset process-environment to its old value in
>> >> dump_unwind_cleanup?
>> >
>> > You are thinking about re-dumping from an interactive session?
>>
>> Yes
>>
>> > In
>> > that case, probably yes.  But currently we only support dumping from
>> > batch sessions, and in that case I don't see a need to restore
>> > process-environment, am I missing something?
>>
>> We "support" dumping only from dedicated batch instances in that for now
>> we should consider only bugs in that use case release-blocking, but I
>> don't want to gratuitously break other use cases like dumping
>> interactive
>> sessions without killing them, since these use cases are meant to work
>> and
>> we'll give them the same level of support someday soon.
>
> OK, but is there any reason dump_unwind_cleanup doesn't restore
> post-gc-hook?  Omission?

Not restoring post-gc-hook is a bug. Thanks for spotting that!





  reply	other threads:[~2019-04-03 16:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190321155613.6127.22574@vcs0.savannah.gnu.org>
     [not found] ` <20190321155614.E6343209B2@vcs0.savannah.gnu.org>
2019-04-02 19:02   ` [Emacs-diffs] master 1072155: Avoid duplicate entries in process-environment after re-dumping Daniel Colascione
2019-04-02 19:24     ` Eli Zaretskii
2019-04-02 20:11       ` Daniel Colascione
2019-04-03  9:22         ` Eli Zaretskii
2019-04-03 16:58           ` Daniel Colascione [this message]
2019-04-03 17:32             ` Eli Zaretskii

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=2f59c1ff3d4ad006c09634813e6724b8.squirrel@dancol.org \
    --to=dancol@dancol.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 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).