unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Vitalie Spinu <spinuvit@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 13290@debbugs.gnu.org
Subject: bug#13290: 24.2.91; [PATCH] Comint can stall emacs with non-trivial input senders
Date: Thu, 03 Jan 2013 11:47:44 +0100	[thread overview]
Message-ID: <87ehi2k0fj.fsf@gmail.com> (raw)
In-Reply-To: <4xd2xmlq1s.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 03 Jan 2013 01:49:03 -0500")

  >> Glenn Morris <rgm@gnu.org>
  >> on Thu, 03 Jan 2013 01:49:03 -0500 wrote:

  > Vitalie Spinu wrote:
  >> The problem is that, occasionally, comint-input-sender might be a
  >> non-trivial function and could take care of process output itself.

  > Thanks for the report. Could you give an example of this happening in
  > practice?

Yes,  this was happening in ESS under some specific
conditions. Particularly when the user wants to evaluate the code
linewise, i.e. each line of code is echoed in the comint buffer, and
then the output is immediately inserted after that line.

This is implemented in comint-input-sender function, and it does nothing
else than just send input line by line and wait after each line for the
process output. Thus, after the execution of comint-input-sender there
was no process output left, and comint was waiting for nothing.

Cases like above, when both input and output should be manipulated, are
not easily implemented in comint-preoutput-filter-functions.

    Vitalie





  reply	other threads:[~2013-01-03 10:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-27 21:49 bug#13290: 24.2.91; [PATCH] Comint can stall emacs with non-trivial input senders Vitalie Spinu
2013-01-03  6:49 ` Glenn Morris
2013-01-03 10:47   ` Vitalie Spinu [this message]
2013-01-06 14:55     ` Vitalie Spinu
2013-01-07  1:07       ` Glenn Morris

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=87ehi2k0fj.fsf@gmail.com \
    --to=spinuvit@gmail.com \
    --cc=13290@debbugs.gnu.org \
    --cc=rgm@gnu.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).