From: "João Távora" <joaotavora@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Speeding up Flymake in emacs-lisp-mode
Date: Fri, 02 Nov 2018 14:06:18 +0000 [thread overview]
Message-ID: <jjb1s8360bp.fsf@gmail.com> (raw)
In-Reply-To: <jwvtvkz7i18.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Fri, 02 Nov 2018 09:05:06 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> First, I was under the impression that stdin/stdout for emacs was
>> not easy.
>
> Usually it's not, but when running in batch mode it's not so bad.
>
>> Glad to hear it isn't, but how do I read from stdin?
>
> async.el does it with (read t), IIRC.
>
>> Are you suggesting I keep a pool of ready to invoke emacsen
>> and discard them once they become "dirty"?
>
> I think so, yes. I'd limit the pool to a single process.
Actually, now I think Noam was suggesting something else, which is
insulating slow process creation from the "main" emacs. And that indeed
requires just a single extra process.
> It should be easy to do directly within async.el.
> Basically, change async-start so that instead of
>
> (let ((proc (async-start-process ...)))
> (async--transmit-sexp proc ...))
>
> it does
>
> (let ((proc async--eager-process))
> (async--transmit-sexp proc ...)
> (setq async--eager-process (async-start-process ...)))
Yeah, but I don't see why I need to restart async--eager-process
(assuming that's what async-start-process does).
Is async.el in ELPA?
João
next prev parent reply other threads:[~2018-11-02 14:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 11:54 Speeding up Flymake in emacs-lisp-mode João Távora
2018-11-02 12:08 ` Stefan Monnier
2018-11-02 12:26 ` Noam Postavsky
2018-11-02 12:34 ` João Távora
2018-11-02 13:05 ` Stefan Monnier
2018-11-02 13:26 ` Noam Postavsky
2018-11-02 14:01 ` João Távora
2018-11-02 14:07 ` Noam Postavsky
2018-11-02 14:06 ` João Távora [this message]
2018-11-02 14:25 ` 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=jjb1s8360bp.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.