unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: 4137@debbugs.gnu.org
Subject: bug#4137: 23.1.50; vc-dir waits instead of error message
Date: Tue, 22 Dec 2020 07:51:53 +0100	[thread overview]
Message-ID: <87tuse8h9y.fsf@gnus.org> (raw)
In-Reply-To: <E1kra8S-0005hE-M0@fencepost.gnu.org> (Richard Stallman's message of "Tue, 22 Dec 2020 00:23:00 -0500")

Richard Stallman <rms@gnu.org> writes:

> That time I forgot to run ssh-add, so the basic vc commands should
> have failed.
>
> But vc-dir didn't report a failure.  Instead it created the buffer
> with no failure report, and then the buffer was nonresponsive to
> commands.
>
> The bug is that vc-dir did not fail when it should have failed.

Do you have a recipe for reproducing this, though?

I tried a session without an ssh agent, and I issued the `vc-update'
command, and I got an error buffer with the following data:

---
Running "git pull --stat"...
Permission denied, please try again.^M
Received disconnect from 209.51.188.201 port 22:2: Too many authentication fail\
ures for larsi^M
Disconnected from 209.51.188.201 port 22^M
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.


-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2020-12-22  6:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 14:21 bug#4137: 23.1.50; vc-dir waits instead of error message Richard Stallman
2019-10-01 13:13 ` Lars Ingebrigtsen
2020-08-20 18:40   ` Lars Ingebrigtsen
     [not found]     ` <E1kra8S-0005hE-M0@fencepost.gnu.org>
2020-12-22  6:51       ` Lars Ingebrigtsen [this message]
2020-12-23  4:27         ` Richard Stallman
2020-12-23  4:17     ` Richard Stallman

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=87tuse8h9y.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=4137@debbugs.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).