From: Chong Yidong <cyd@stupidchicken.com>
To: Dan Nicolaescu <dann@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: vc-update for bzr etc.
Date: Wed, 24 Nov 2010 12:19:43 -0500 [thread overview]
Message-ID: <87lj4i1vww.fsf@stupidchicken.com> (raw)
In-Reply-To: <yxqvd3nzn2g.fsf@fencepost.gnu.org> (Dan Nicolaescu's message of "Tue, 23 Nov 2010 17:34:31 -0500")
Dan Nicolaescu <dann@gnu.org> writes:
>> The VC-dir buffer displays no indication while the merge/pull is
>> running. Afterwards, there is no sign that the operation has completed,
>> other than an echo area message (easily overwritten by other Emacs
>> commands) and some changes in file status (easily overlooked).
>>
>> So it seems like there needs to be some kind of status message display
>> in the VC-dir buffer, showing (at least) the most recent VCS operation
>> and its status. WDYT?
>
> In the buffer? The way pcl-cvs does it is a bad idea, I am completely
> against it. Putting something in the modeline, like the rest of the
> vc asynchronous commands do would be better.
Stuff in the modeline is awfully easy to overlook. It doesn't really
address the feeling of "flimsiness" from doing an update/pull and seeing
no obvious response. How bout putting it in a header line?
If you could explain in more detail why you think putting a status
message in the buffer is a bad idea, that would make it easier to figure
out what the right thing is.
next prev parent reply other threads:[~2010-11-24 17:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 15:43 vc-update for bzr etc Chong Yidong
2010-11-21 17:00 ` Andreas Schwab
2010-11-21 17:09 ` Dan Nicolaescu
2010-11-21 17:33 ` Chong Yidong
2010-11-21 20:20 ` Stefan Monnier
2010-11-21 21:08 ` Chong Yidong
2010-11-22 2:04 ` Stefan Monnier
2010-11-22 4:31 ` Stephen J. Turnbull
2010-11-22 8:40 ` Thien-Thi Nguyen
2010-11-22 11:04 ` Stephen J. Turnbull
2010-11-22 14:39 ` Stefan Monnier
2010-11-22 17:29 ` Chong Yidong
2010-11-23 15:37 ` Stephen J. Turnbull
2010-11-23 16:20 ` Stefan Monnier
2010-11-22 4:35 ` Chong Yidong
2010-11-22 6:52 ` Dan Nicolaescu
2010-11-22 14:42 ` Stefan Monnier
2010-11-22 10:54 ` Eli Zaretskii
2010-11-22 14:41 ` Stefan Monnier
2010-11-23 1:40 ` Chong Yidong
2010-11-23 14:27 ` Stefan Monnier
2010-11-23 16:08 ` Chong Yidong
2010-11-23 17:03 ` Dan Nicolaescu
2010-11-23 17:02 ` Dan Nicolaescu
2010-11-23 19:29 ` Chong Yidong
2010-11-23 22:05 ` Stefan Monnier
2010-11-23 22:34 ` Dan Nicolaescu
2010-11-24 17:19 ` Chong Yidong [this message]
2010-11-22 16:57 ` Chong Yidong
2010-11-22 17:59 ` Eli Zaretskii
2010-11-21 19:03 ` Stefan Monnier
2010-11-21 19:34 ` Chong Yidong
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=87lj4i1vww.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=dann@gnu.org \
--cc=emacs-devel@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).