From: Dan Nicolaescu <dann@gnu.org>
To: 895@debbugs.gnu.org
Cc: larsi@gnus.org
Subject: bug#895: slow processing of process output
Date: Wed, 06 Jul 2011 11:32:57 -0400 [thread overview]
Message-ID: <yxqaacrmnkm.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m3liwk86q9.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 30 Jun 2011 03:10:06 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Markus Triska <markus.triska@gmx.at> writes:
>
>> I can reproduce the problem on OSX, and could significantly improve the
>> running time by setting process-connection-type to nil before doing the
>> rgrep. Let rgrep.el consist of:
>>
>> (grep-compute-defaults)
>> (setq process-connection-type nil)
>> (rgrep "emacs" "*.el" "~/emacs/lisp/")
>>
>> (while (process-status "grep")
>> (sit-for 0.1))
>
> I've now bound `process-connection-type' to nil in `rgrep' for Emacs 24.
This might solve the specific `rgrep' case, but that was only a specific
easy to reproduce example.
Processing process output is slow for other things too.
For example compare the time to run
make bootstrap
when using M-x compile
vs doing it in an xterm.
next prev parent reply other threads:[~2011-07-06 15:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 14:33 bug#895: slow processing of process output Markus Triska
2011-06-30 1:10 ` Lars Magne Ingebrigtsen
2011-07-06 15:07 ` Stefan Monnier
2011-07-06 15:51 ` Lars Magne Ingebrigtsen
2011-07-06 15:57 ` Lars Magne Ingebrigtsen
2011-07-06 17:58 ` Drew Adams
2011-07-06 18:50 ` Lars Magne Ingebrigtsen
2011-07-06 19:15 ` Stefan Monnier
2011-07-06 15:32 ` Dan Nicolaescu [this message]
2011-07-06 19:17 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2008-09-05 15:43 Dan Nicolaescu
2008-10-02 9:29 ` Dan Nicolaescu
2016-01-08 1:24 ` Richard Copley
2016-01-08 9:30 ` Eli Zaretskii
2016-01-08 9:53 ` Alexis
2016-01-08 10:00 ` Eli Zaretskii
2016-01-08 10:07 ` Dmitry Gutov
2016-01-08 10:54 ` Eli Zaretskii
2016-01-08 1:26 ` Richard Copley
2016-06-05 1:51 ` Noam Postavsky
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=yxqaacrmnkm.fsf@fencepost.gnu.org \
--to=dann@gnu.org \
--cc=895@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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).