From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#41423: 27.0.91; eshell file completion in tramp dir is slow (3 minutes) [regression on pretest] Date: Wed, 02 Sep 2020 19:52:34 +0000 Message-ID: References: <87mu2d7hka.fsf@gmx.de> Reply-To: Gregory Heytings Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23445"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Alpine 2.22 (NEB 394 2020-01-19) Cc: Tim Vaughan , rrandresf@gmail.com, Michael Albinus , 41423@debbugs.gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Sep 02 21:53:11 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kDYog-0005ze-W4 for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 02 Sep 2020 21:53:10 +0200 Original-Received: from localhost ([::1]:59238 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kDYof-00080y-Sp for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 02 Sep 2020 15:53:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55886) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kDYoY-00080D-RP for bug-gnu-emacs@gnu.org; Wed, 02 Sep 2020 15:53:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49193) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kDYoY-0004tP-J5 for bug-gnu-emacs@gnu.org; Wed, 02 Sep 2020 15:53:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kDYoY-0007zc-GJ for bug-gnu-emacs@gnu.org; Wed, 02 Sep 2020 15:53:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 02 Sep 2020 19:53:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 41423 X-GNU-PR-Package: emacs Original-Received: via spool by 41423-submit@debbugs.gnu.org id=B41423.159907636530702 (code B ref 41423); Wed, 02 Sep 2020 19:53:02 +0000 Original-Received: (at 41423) by debbugs.gnu.org; 2 Sep 2020 19:52:45 +0000 Original-Received: from localhost ([127.0.0.1]:60739 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kDYoH-0007z8-2l for submit@debbugs.gnu.org; Wed, 02 Sep 2020 15:52:45 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:64122) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kDYoC-0007yt-4p for 41423@debbugs.gnu.org; Wed, 02 Sep 2020 15:52:43 -0400 Original-Received: from sdf.org (IDENT:ghe@faeroes.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 082JqcS2017817 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Wed, 2 Sep 2020 19:52:38 GMT Original-Received: (from ghe@localhost) by sdf.org (8.15.2/8.12.8/Submit) id 082Jql5Q009651; Wed, 2 Sep 2020 19:52:47 GMT In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:186955 Archived-At: > >> What is still missing IMO is a general description/documentation of the >> various parts of the completion mechanisms (completion-at-point, >> completion-in-region, pcomplete, pcomplete-completion-at-point, >> comint-completion-at-point, icomplete, ...) in Emacs behave and >> interact. I was completely lost when I started working on this bug, >> things are a bit clearer now, but still not very clear. > > I find it hard to write such things because I'm too familiar with it to > know what's non-obvious. Maybe you could try writing something that > you'd have found useful, and then we can collaboratively improve it? > Based on the time I already spent on this bug, I guess writing something like this will require a substantial amount of work, but if you are willing to help me, I'm willing to do that.