unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: "Tim Van Holder" <tim.vanholder@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: 23.0.60; new vc-status interface: no more multi-file commits?
Date: Mon, 14 Apr 2008 02:13:32 -0700	[thread overview]
Message-ID: <200804140913.m3E9DWW1029500@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <d69e7f6a0804111156h3fcb0a7fv20222217ab8cbb6e@mail.gmail.com> (Tim Van Holder's message of "Fri, 11 Apr 2008 20:56:26 +0200")

"Tim Van Holder" <tim.vanholder@gmail.com> writes:

  > On Fri, Apr 11, 2008 at 6:13 PM, Dan Nicolaescu <dann@ics.uci.edu> wrote:
  > > "Tim Van Holder" <tim.vanholder@gmail.com> writes:
  > >   > On top of that, the retrieving of the status info uses a
  > >   > background process; in the case of the tree I was using (a gcc
  > >   > checkout), that process is quite slow, and there did not seem to be an
  > >   > obvious way to cancel it. C-g did nothing (since it's a background
  > >   > process), and when it finished after I had killed the vc-status buffer
  > >   > I received a 'selecting deleted buffer' error.
  > >
  > >  C-c C-c kills the update process (second to last menu entry).
  > 
  > I didn't notice that.
  > Would be nice if the background task could check that its buffer was
  > still alive when updating it, so that it would silently abort if the
  > (overly impatient) user killed it (or, alternatively, kill the process
  > if the buffer is killed).

Thanks, that sound like a good idea.  Now the update process is killed
when the VC status buffer is killed.




      reply	other threads:[~2008-04-14  9:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11 15:42 23.0.60; new vc-status interface: no more multi-file commits? Tim Van Holder
2008-04-11 16:13 ` Dan Nicolaescu
2008-04-11 18:56   ` Tim Van Holder
2008-04-14  9:13     ` Dan Nicolaescu [this message]

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=200804140913.m3E9DWW1029500@sallyv1.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=tim.vanholder@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 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).