From: Dan Nicolaescu <dann@ics.uci.edu>
To: rms@gnu.org
Cc: 2944@emacsbugs.donarmstrong.com
Subject: bug#2944: 23.0.91; vc-dir confusing at startup
Date: Thu, 9 Apr 2009 19:14:28 -0700 (PDT) [thread overview]
Message-ID: <200904100214.n3A2EScB010591@godzilla.ics.uci.edu> (raw)
In-Reply-To: <E1Ls2lI-0006dC-Sm@fencepost.gnu.org> (Richard M. Stallman's message of "Thu, 09 Apr 2009 18:30:20 -0400")
Richard M Stallman <rms@gnu.org> writes:
> I just ran vc-dir for the first time. It worked -- after a while.
> However, at first it displayed just a few lines of info
> about the overall VC handling of the directory. It seemed
> to be doing the wrong job.
>
> So I started to wonder if that were the wrong command.
> I looked at the doc string and it did not clarify the question.
> It says it "shows the VC status for DIR". The few lines
> that were displayed seemed to fit that description.
>
> Eventually the info on files did appear. But this is a bug anyway.
>
> I think the doc string should be fixed, and the buffer should
> start out containing explanatory text such as
> "The status of files is being computed
> and will be displayed here when that is done."
The problem with not showing something in VC buffer is a common one for
asynchronous VC commands (diff, log). The solution we have in emacs-23
for that is to add [Working...] on the modeline while such command is in
progress. Was that not obvious enough? Does the face for that message
need to stand out a bit more?
Please feel free to fix the doc string the way you want it.
next prev parent reply other threads:[~2009-04-10 2:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 22:30 bug#2944: 23.0.91; vc-dir confusing at startup Richard M Stallman
2009-04-10 2:14 ` Dan Nicolaescu [this message]
2009-04-10 14:26 ` Richard M Stallman
2009-04-11 15:20 ` Dan Nicolaescu
2009-04-11 15:30 ` Processed: " Emacs bug Tracking System
2021-08-27 3:19 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200904100214.n3A2EScB010591@godzilla.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=2944@emacsbugs.donarmstrong.com \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.