From: Dan Nicolaescu <dann@ics.uci.edu>
To: Tom Tromey <tromey@redhat.com>
Cc: emacs-devel@gnu.org, Thien-Thi Nguyen <ttn@gnuvola.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: vc-*-root finctions
Date: Thu, 21 Feb 2008 12:06:10 -0800 [thread overview]
Message-ID: <200802212006.m1LK6AUN024939@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <m3k5ky169o.fsf@fleche.redhat.com> (Tom Tromey's message of "Thu, 21 Feb 2008 12:03:31 -0700")
Tom Tromey <tromey@redhat.com> writes:
> >>>>> "Dan" == Dan Nicolaescu <dann@ics.uci.edu> writes:
>
> >> To support asynchronous behavior well, we wish to keep the user informed,
> >> i.e, updating some visible status at the asynchronous boundaries (twice).
>
> Dan> Huh? Please explain this.
>
> He is saying that when you start an async command, you want to give
> the user some indication is has started; and then when the command
> finishes, Emacs should give an indication that it has finished.
>
> That seems fairly uncontroversial to me.
Agreed. That's why I said that the patch needs to be split up....
Using the mode-line (like all the vc-commands do now) seems like a good
idea.
> However, I think the most likely cause of "flickering" would be the
> pcvs-like in-buffer notification, which got nixed.
Printing the exact command run for doing was considered unnecessary, but
maybe printing some other status message could be helpful...
next prev parent reply other threads:[~2008-02-21 20:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 22:06 vc-*-root finctions Stefan Monnier
2008-02-20 11:12 ` Thien-Thi Nguyen
2008-02-20 17:21 ` Stefan Monnier
2008-02-20 18:21 ` Thien-Thi Nguyen
2008-02-20 18:50 ` Dan Nicolaescu
2008-02-21 15:33 ` Thien-Thi Nguyen
2008-02-21 18:35 ` Dan Nicolaescu
2008-02-21 19:03 ` Tom Tromey
2008-02-21 20:06 ` Dan Nicolaescu [this message]
2008-02-21 19:33 ` Stefan Monnier
2008-02-21 19:01 ` Tom Tromey
2008-02-21 20:01 ` Dan Nicolaescu
2008-02-21 19:50 ` Dan Nicolaescu
2008-02-22 14:41 ` Thien-Thi Nguyen
2008-02-22 15:42 ` Dan Nicolaescu
2008-02-22 17:34 ` Thien-Thi Nguyen
2008-02-22 19:02 ` Dan Nicolaescu
2008-02-22 2:42 ` Mike Mattie
2008-02-20 19:20 ` Stefan Monnier
2008-02-21 15:36 ` Thien-Thi Nguyen
2008-02-21 16:16 ` Stefan Monnier
2008-02-22 14:54 ` Thien-Thi Nguyen
2008-02-22 16:50 ` 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
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=200802212006.m1LK6AUN024939@sallyv1.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=tromey@redhat.com \
--cc=ttn@gnuvola.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).