From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: A project-files implementation for Git projects Date: Fri, 20 Sep 2019 09:45:12 -0400 Message-ID: References: <8736h9rdc4.fsf@gnu.org> <87tv9kz2x6.fsf@gnu.org> <87a7bbjdwe.fsf@gnu.org> <87a7ba8uvx.fsf@gnu.org> <87pnk2zvvy.fsf@gnu.org> <838sqpx9eq.fsf@gnu.org> <83y2yow9dy.fsf@gnu.org> <838sqnw2na.fsf@gnu.org> <3007947f-f4eb-e3e8-8c14-1b372323aa1c@yandex.ru> <831rwfvzd6.fsf@gnu.org> <64bcedbf-d891-dcad-ac65-5719920f58e2@yandex.ru> <83k1a4tct2.fsf@gnu.org> <83tv97run8.fsf@gnu.org> <5ba04bf6-ed74-a18e-9074-5aa481ec3669@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="203446"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: Eli Zaretskii , emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Sep 20 15:46:02 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iBJEW-000qkF-Ho for ged-emacs-devel@m.gmane.org; Fri, 20 Sep 2019 15:46:00 +0200 Original-Received: from localhost ([::1]:59834 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iBJEU-0002we-5u for ged-emacs-devel@m.gmane.org; Fri, 20 Sep 2019 09:45:58 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56450) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iBJE0-0002uE-Gk for emacs-devel@gnu.org; Fri, 20 Sep 2019 09:45:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iBJDy-0008VM-Tc for emacs-devel@gnu.org; Fri, 20 Sep 2019 09:45:27 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:14718) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iBJDq-0008My-W5; Fri, 20 Sep 2019 09:45:19 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 0F81C100951; Fri, 20 Sep 2019 09:45:15 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id C12B31009C1; Fri, 20 Sep 2019 09:45:13 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1568987113; bh=ShrMOzzSt6m6CoueQLHyWzsEGSY4B3LH2OBSe2/mLoo=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=FFwQmvsk/jlymwefW9Loh5pRprqpjbsoswPIImJnhQ7dHt7EoNCChz43ek2qcq+Cg W2J9ZWYTP3/yEso4T3WMnBgbMwEEmSh41/BxqHeFO5ts/uNlxQavxaFCEgzkGQwjbE xs9I96l4Loqr9YLtCglMqJHBaRjt0ZxZvN53iV+IEMzEz+XLr1gVtmFN6dGb5AaOpq InXLADrspLii+9+p9tp9MLx2eA99iv4o4enJVqpUu9H4i9RFqYaPwqxpLQwrOYFSED wJY6aWXr/2s9YSL2rUtjXIQIkA6vJ/Jj0ZWXA30dnCpb/+FCR2mvP1DyeqY2hKHI3l pCf28trEGl27w== Original-Received: from pastel (76-10-182-129.dsl.teksavvy.com [76.10.182.129]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 8959A120458; Fri, 20 Sep 2019 09:45:13 -0400 (EDT) In-Reply-To: <5ba04bf6-ed74-a18e-9074-5aa481ec3669@yandex.ru> (Dmitry Gutov's message of "Fri, 20 Sep 2019 16:28:07 +0300") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 132.204.25.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:240185 Archived-At: > It could work by detecting a "congestion" before the event happens (by > seeing that events fire up very quickly, so the queue must fill up > soon). That wouldn't be 100% reliable, though. That's right: it wouldn't be 100% reliable. I don't think we want to go that way. We could ask for inotify or other backends to send us a special event when other events were dropped, but IIRC currently we don't get that info and inferring it from outside is just too ugly to consider. Stefan