all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Speeding up Flymake in emacs-lisp-mode
Date: Fri, 2 Nov 2018 12:34:23 +0000	[thread overview]
Message-ID: <CALDnm53P2P2_ozeJT9QqyG0otmtbuHCKeFe=P68bj4HO1EhA=A@mail.gmail.com> (raw)
In-Reply-To: <CAM-tV-82uqbm76_J7TQ99r5D+EU715hmcy5wyorocygk8CKkoQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 999 bytes --]

On Fri, Nov 2, 2018 at 12:26 PM Noam Postavsky <npostavs@gmail.com> wrote:

> On Fri, 2 Nov 2018 at 07:55, João Távora <joaotavora@gmail.com> wrote:
>
> > It'd probably be better if only one process was launched and asked
> > (perhaps using server.el) to compile the files.
>
> Alternate idea: keep running a single compilation per Emac subprocess,
> but tell it what to compile by sending to stdin instead of command
> line args. That way, the process startup can happen asynchronously,
> and when you want to compile something you can arrange to have a
> subprocess ready and waiting for input.
>

Thanks.

First, I was under the impression that stdin/stdout for emacs was
not easy. Glad to hear it isn't, but how do I read from stdin?

Are you suggesting I keep a pool of ready to invoke emacsen
and discard them once they become "dirty"?

What do you mean by asynchronous process startup? Isn't that
a "stop-the-world" operation however it is invoked?

João Távora

[-- Attachment #2: Type: text/html, Size: 1551 bytes --]

  reply	other threads:[~2018-11-02 12:34 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 [this message]
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
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='CALDnm53P2P2_ozeJT9QqyG0otmtbuHCKeFe=P68bj4HO1EhA=A@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=npostavs@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 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.