unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Problem with portable dumper
Date: Sat, 15 Feb 2020 21:58:13 +0100	[thread overview]
Message-ID: <877e0ny3dm.fsf@gmx.de> (raw)
In-Reply-To: <jwvy2t3k2j0.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 15 Feb 2020 15:42:05 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

Hi Stefan,

> That doesn't explain why you need a mutex object to be written in the
> dumped image of Emacs.
>
> AFAICT Tramp is not even preloaded, so changing Tramp should simply not
> affect the dump at all.

The changes in files.el and vc-hooks.el are not related to Tramp. I have
changed the find-file* family of functions as well as vc-refresh-state
to run asynchronously if indicated. Tramp just profits from it.

All of this was discussed in detail months ago, when I did work on that
branch. The pdumper was introduced later, while I was away from this
work, and now I have the said problem being back.

If you want to see what happened, compare doc/emacs/files.texi,
doc/lispref/files.texi, files.el and vc-hooks.el from between master and
feature/tramp-thread-safe. etc/NEWS in the branch says also something
about (condensed).

>         Stefan

Best regards, Michael.



  reply	other threads:[~2020-02-15 20:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-15 18:45 Problem with portable dumper Michael Albinus
2020-02-15 19:20 ` Eli Zaretskii
2020-02-15 20:33   ` Michael Albinus
2020-02-15 20:42     ` Stefan Monnier
2020-02-15 20:58       ` Michael Albinus [this message]
2020-02-15 21:03         ` Stefan Monnier
2020-02-16  3:28         ` Eli Zaretskii
2020-02-16 10:19           ` Michael Albinus
2020-02-16 15:24             ` Eli Zaretskii
2020-02-16 16:56               ` Michael Albinus

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=877e0ny3dm.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).