From: Noam Postavsky <npostavs@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Speeding up Flymake in emacs-lisp-mode
Date: Fri, 2 Nov 2018 09:26:13 -0400 [thread overview]
Message-ID: <CAM-tV-_3tAKiJMX09i1rOvmcOtZG10THvX1LW8WJZWtQaHe8qg@mail.gmail.com> (raw)
In-Reply-To: <jwvtvkz7i18.fsf-monnier+gmane.emacs.devel@gnu.org>
On Fri, 2 Nov 2018 at 09:12, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>
> > 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.
Yup, (elisp) Batch Mode:
input that would normally come from the minibuffer is read from the
standard input descriptor.
> > Glad to hear it isn't, but how do I read from stdin?
>
> async.el does it with (read t), IIRC.
read-from-minibuffer should also work if non-sexp input is wanted.
>> What do you mean by asynchronous process startup? Isn't that
>> a "stop-the-world" operation however it is invoked?
The subprocess created by make-process (or start-process) doesn't
block the parent Emacs, it runs in parallel.
(benchmark
1 '(call-process (concat invocation-directory invocation-name)
nil nil nil "-Q" "--batch"))
;=> "Elapsed time: 0.185000s"
(benchmark 1 '(start-process
"emacs" nil (concat invocation-directory invocation-name)
"-Q" "--batch"))
;=> "Elapsed time: 0.031000s"
next prev parent reply other threads:[~2018-11-02 13:26 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 [this message]
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
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=CAM-tV-_3tAKiJMX09i1rOvmcOtZG10THvX1LW8WJZWtQaHe8qg@mail.gmail.com \
--to=npostavs@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.