From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Eli Zaretskii <eliz@gnu.org>,
monnier@iro.umontreal.ca, andreyk.mad@gmail.com,
emacs-devel@gnu.org
Subject: Re: Change in vc-git ls-files-unknown makes emacs hang
Date: Fri, 20 Dec 2019 20:14:51 +0300 [thread overview]
Message-ID: <m2lfr6or5g.fsf@fastmail.fm> (raw)
In-Reply-To: <97287846-5a3c-8da9-9907-abedbd877ee4@yandex.ru> (Dmitry Gutov's message of "Fri, 20 Dec 2019 17:40:34 +0200")
On 20/12/2019 17:40 +0200, Dmitry Gutov wrote:
> On 20.12.2019 17:36, Filipp Gunbin wrote:
>> Dmitry, thanks, it helps - no freezes and no visible delays now, at
>> least not yet.
>
> Very good.
>
> Does the resulting VC-Dir buffer look usable?
Yes, currently no problems. I'm in emacs with the patch now, will post
if anything appears in the neartime.
>> When I was trying to generate trace, I started & killed (-s USR2) emacs
>> several times, and saw that desktop had several buffers which could
>> trigger the problem.
>
> So there were several VC-Dir buffers like that in that session?
My feeling was that any dired buffer for a directory underneath home dir
(where .git is) also invoked freeze.
next prev parent reply other threads:[~2019-12-20 17:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 14:16 Change in vc-git ls-files-unknown makes emacs hang Filipp Gunbin
2019-12-19 14:41 ` Dmitry Gutov
2019-12-19 20:44 ` Filipp Gunbin
2019-12-19 22:42 ` Dmitry Gutov
2019-12-20 7:33 ` Eli Zaretskii
2019-12-20 10:52 ` Filipp Gunbin
2019-12-20 14:13 ` Dmitry Gutov
2019-12-20 15:36 ` Filipp Gunbin
2019-12-20 15:40 ` Dmitry Gutov
2019-12-20 17:14 ` Filipp Gunbin [this message]
2019-12-20 22:18 ` Dmitry Gutov
2019-12-21 21:51 ` Proced signals (was: Change in vc-git ls-files-unknown makes emacs hang) Juri Linkov
2019-12-22 17:02 ` Eli Zaretskii
2019-12-19 20:45 ` Change in vc-git ls-files-unknown makes emacs hang Stefan Monnier
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=m2lfr6or5g.fsf@fastmail.fm \
--to=fgunbin@fastmail.fm \
--cc=andreyk.mad@gmail.com \
--cc=dgutov@yandex.ru \
--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 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.