unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: maierh@rhea.maierh, spiegel@gnu.org, emacs-devel@gnu.org
Subject: Re: special-display-buffer-names and vc-diff displays wrong result
Date: Tue, 04 Oct 2005 14:50:49 -0400	[thread overview]
Message-ID: <E1EMrsH-0006r1-80@fencepost.gnu.org> (raw)
In-Reply-To: <jwv7jcu72z4.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 03 Oct 2005 16:43:07 -0400)

    > Also, wait_reading_process_output runs sentinels before it
    > reads output.  So if the signals arrive at the same time,
    > Emacs will run the sentinel first.

    If the sentinel happens to run first, is the output still processed
    afterwards or is it just discarded?

I think the output is still processed, but I am not certain.  It would
definitely be a bug if the output is lost when the termination signal
is handled first.  I think there is no such bug, since nobodyt is
reporting it.

    - it doesn't actually care whether there were diffs or not: the code is just
      trying to make sure that the buffer doesn't stay empty, leaving the user
      to wonder whether the command got frozen or just didn't produce
      any output.  So it also makes sense to check the buffer's emptiness.

The easiest way to do this is to program the sentinel to insert some
text at the end of the buffer.

  reply	other threads:[~2005-10-04 18:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051002055458.1473025A144@gaia.local>
2005-10-03  5:09 ` special-display-buffer-names and vc-diff displays wrong result Richard M. Stallman
2005-10-03 14:45   ` Stefan Monnier
2005-10-03 19:33     ` Richard M. Stallman
2005-10-03 20:43       ` Stefan Monnier
2005-10-04 18:50         ` Richard M. Stallman [this message]
2005-10-05  3:52   ` Harald Maier

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=E1EMrsH-0006r1-80@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=maierh@rhea.maierh \
    --cc=spiegel@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).