From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#32986: 27.0.50; unexpected delay in while-no-input + accept-process-output Date: Fri, 14 Dec 2018 01:14:20 +0200 Message-ID: <04f65cc9-f4c5-0a91-3368-99e3c8a22645@yandex.ru> References: <83sh1gzdey.fsf@gnu.org> <83in2cyymt.fsf@gnu.org> <83h8hvzw70.fsf@gnu.org> <83d0sjyxio.fsf@gnu.org> <87bm7wxjtt.fsf@gmail.com> <401dbba4-8c00-07f7-ee0a-62fe4b59cc12@yandex.ru> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1544742788 6016 195.159.176.226 (13 Dec 2018 23:13:08 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 13 Dec 2018 23:13:08 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:64.0) Gecko/20100101 Thunderbird/64.0 Cc: 32986@debbugs.gnu.org To: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Dec 14 00:13:03 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gXaAB-0001Sd-EV for geb-bug-gnu-emacs@m.gmane.org; Fri, 14 Dec 2018 00:13:03 +0100 Original-Received: from localhost ([::1]:57360 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gXaCH-0003oj-SR for geb-bug-gnu-emacs@m.gmane.org; Thu, 13 Dec 2018 18:15:13 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50825) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gXaCA-0003oN-Hf for bug-gnu-emacs@gnu.org; Thu, 13 Dec 2018 18:15:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gXaC6-0007Rk-OQ for bug-gnu-emacs@gnu.org; Thu, 13 Dec 2018 18:15:06 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:42799) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gXaC6-0007QZ-Gg for bug-gnu-emacs@gnu.org; Thu, 13 Dec 2018 18:15:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gXaC6-0002fy-6G for bug-gnu-emacs@gnu.org; Thu, 13 Dec 2018 18:15:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 13 Dec 2018 23:15:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32986 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 32986-submit@debbugs.gnu.org id=B32986.154474287110236 (code B ref 32986); Thu, 13 Dec 2018 23:15:02 +0000 Original-Received: (at 32986) by debbugs.gnu.org; 13 Dec 2018 23:14:31 +0000 Original-Received: from localhost ([127.0.0.1]:47057 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gXaBb-0002f2-9S for submit@debbugs.gnu.org; Thu, 13 Dec 2018 18:14:31 -0500 Original-Received: from mail-wr1-f42.google.com ([209.85.221.42]:33954) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gXaBa-0002eq-7h for 32986@debbugs.gnu.org; Thu, 13 Dec 2018 18:14:30 -0500 Original-Received: by mail-wr1-f42.google.com with SMTP id j2so3702152wrw.1 for <32986@debbugs.gnu.org>; Thu, 13 Dec 2018 15:14:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Alo4xNzYehab1ppwDbuIp989RqzzK9oeIV1JXt5CT5o=; b=sr7FKxK2je07VXz2eFBSVt3WA72w9HyfPhjC4BoKf0VtzgSYWAE52nYUPSjXs6mEzz ms7Lhfo0L8XGlcfBP+4eumAAqlGIT1IGqyIzVZlH9y1V15GsvMYHaI72hYIaz+v13AEu fjNVRT97iVpgwA8R4oZ0kZBHDjsZmGVmNJtVR9fy3x54jSifbyciraA2APasF6l/iiRn s5Ac0ybtCYKhmQ1y8JwQAKVdk/n+2W/GAGA1qyQFXFs80Y+j4lC9h9fELkckWQBW6kvG GL0L4e9g8e4AwTm0X9o5YYJRiYqGL5rUowTvfRqeFdrm8arMAeZ6PZnvjZxctdbMkIYQ WoPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Alo4xNzYehab1ppwDbuIp989RqzzK9oeIV1JXt5CT5o=; b=Hi/XFsB3yk34YRqWQL9BbpRSYFtGLlxaBgKzHC/3R2jpsAUe58P6kaxPohPk6SYorm RSHqJI+Ivn0CQeGv0fdZtseKkwCHVsshR3wA2wkHKv6t+efwDWJeYpbLHNJseGFRZ3nA fg6F0InHN2viq5DwWf5pACNjvLQd2Ggtiacenw74N7H22C6pk65/pq93U3X6N6Jb5FA1 B4ZCaryMeBTpc3N7XfMOUesFmMVR026inJXDx7SVab8LDmRX/eJDJAoKq/BrWIJu/fI5 JaLMIkLoC5vmiWngsxu7xuMs7JvXFQW0aeixp3lgClj0FL5nsd5b9FEDXfaNfHNkofn7 +JFQ== X-Gm-Message-State: AA+aEWY4XKs+/JJ1LH4bL5K4qVV4xkdzxDVO4sSt5KPAWl7gydYkYWwd AyUos9zUv8AT25dQcI9HDaD85r34 X-Google-Smtp-Source: AFSGD/W9/T4kCr/gFw2jbvxje7AH5ru5P8FL/MoFWrFuX7JyxGm5AIM8ecbB2LxenxR+b+V4/j0p8g== X-Received: by 2002:a5d:4e82:: with SMTP id e2mr562960wru.291.1544742864145; Thu, 13 Dec 2018 15:14:24 -0800 (PST) Original-Received: from [192.168.1.3] ([185.105.174.23]) by smtp.googlemail.com with ESMTPSA id b12sm2059814wrt.17.2018.12.13.15.14.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Dec 2018 15:14:22 -0800 (PST) In-Reply-To: Content-Language: en-US X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 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.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:153424 Archived-At: On 12.12.2018 23:42, João Távora wrote: > Indeed, I developed this for `company-capf`-based backends. I imagine the chief drawback of this approach is if the user would try to "group" several backends like this, Company style. CAPF has no handy way to do this, but we could add a macro in the future, and anyway, it's already possible to do this by means of function composition. It would be handy if, when we get to this point, several completion tables like this could fetch their completions simultaneously. Just something to think about, for the future. In the meantime, LSP style with a smart server and one backend working with it is probably good enough for >90% users anyway.