unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: "João Távora" <joaotavora@gmail.com>
Cc: 32986@debbugs.gnu.org
Subject: bug#32986: 27.0.50; unexpected delay in while-no-input + accept-process-output
Date: Fri, 14 Dec 2018 01:14:20 +0200	[thread overview]
Message-ID: <04f65cc9-f4c5-0a91-3368-99e3c8a22645@yandex.ru> (raw)
In-Reply-To: <CALDnm52iZ65mCbGBb2aM3t7ty6S1E3EtS7GSdiFemvPQPPmRug@mail.gmail.com>

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.





  parent reply	other threads:[~2018-12-13 23:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08 10:48 bug#32986: 27.0.50; unexpected delay in while-no-input + accept-process-output João Távora
2018-10-08 15:05 ` Eli Zaretskii
2018-10-08 20:06   ` João Távora
2018-10-08 20:25     ` Eli Zaretskii
2018-10-08 20:39       ` João Távora
2018-10-09  2:32         ` Eli Zaretskii
2018-10-09  8:47           ` João Távora
2018-10-09 15:01             ` Eli Zaretskii
2018-10-14 22:08               ` João Távora
2018-10-15 15:03                 ` Eli Zaretskii
2018-10-15 15:50                   ` João Távora
2018-12-11 18:09                 ` Dmitry Gutov
2018-12-12 21:42                   ` João Távora
2018-12-12 23:51                     ` Dmitry Gutov
2018-12-13 23:14                     ` Dmitry Gutov [this message]
2020-09-11 16:22   ` 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

  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=04f65cc9-f4c5-0a91-3368-99e3c8a22645@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=32986@debbugs.gnu.org \
    --cc=joaotavora@gmail.com \
    /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).