From: "João Távora" <joaotavora@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 32986@debbugs.gnu.org
Subject: bug#32986: 27.0.50; unexpected delay in while-no-input + accept-process-output
Date: Wed, 12 Dec 2018 21:42:20 +0000 [thread overview]
Message-ID: <CALDnm52iZ65mCbGBb2aM3t7ty6S1E3EtS7GSdiFemvPQPPmRug@mail.gmail.com> (raw)
In-Reply-To: <401dbba4-8c00-07f7-ee0a-62fe4b59cc12@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]
Indeed, I developed this for `company-capf`-based backends.
I still haven't ported it to jsonrpc.el tho (I think, will check...)
I've been meaning to ask you: in the long run, do you consider
separating company's frontend logic completely so that a simpler
mode non-company completion frontend can be integrated with
emacs (one that would use company-capf exclusively)?
João
On Tue, Dec 11, 2018 at 6:09 PM Dmitry Gutov <dgutov@yandex.ru> wrote:
> On 15.10.2018 1:08, João Távora wrote:
>
> > (joaot/time
> > (catch 'done
> > (progn (make-process :name "test"
> > :filter (lambda (proc string)
> > (message "Hey %s just got %s" proc
> string)
> > (throw 'done nil))
> > :command '("sh" "-c" "sleep 2 && echo bla"))
> > (while (sit-for 30))))) ; Took 02.011 seconds and returned
> nil
>
> It's an interesting alternative to Company's async backend interface,
> where we have a similar piece of code waiting until either completions
> are returned or the user types something (in company--fetch-candidates).
>
> Which of course makes sense, given that CAPF has no async calling
> convention.
>
--
João Távora
[-- Attachment #2: Type: text/html, Size: 2033 bytes --]
next prev parent reply other threads:[~2018-12-12 21:42 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 [this message]
2018-12-12 23:51 ` Dmitry Gutov
2018-12-13 23:14 ` Dmitry Gutov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALDnm52iZ65mCbGBb2aM3t7ty6S1E3EtS7GSdiFemvPQPPmRug@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=32986@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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.