From: Glenn Morris <rgm@gnu.org>
To: Deniz Dogan <deniz@dogan.se>
Cc: 11230@debbugs.gnu.org
Subject: bug#11230: 24.1.50; VC doesn't handle internal errors?
Date: Thu, 12 Apr 2012 20:21:50 -0400 [thread overview]
Message-ID: <bbpqbco50h.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <4F8726EE.1040209@dogan.se> (Deniz Dogan's message of "Thu, 12 Apr 2012 21:03:10 +0200")
Deniz Dogan wrote:
>> Maybe Emacs should test that the option works, not just that it is
>> present. I don't know; it's a slightly more expensive test. (Make a temp
>> repo, check status, delete it.)
>
> I am not that familiar with VC or Bazaar, but is it really necessary
> to do all of that? Couldn't we simply check the return code from
> every Bazaar command and act depending on the result of that?
We're talking at cross purposes. I was talking about setting the default
value of vc-bzr-status-switches more rigorously.
The vc-bzr-status command cannot return an error, because it is invoked
all the time, on simply visiting a file in a bzr-controlled directory.
So an error here might make it impossible to edit a file; or even to
build Emacs [1]. The best Emacs can do is convert the error to a message
and report it, which is what it does already. I vaguely recall that it's
a design decision of vc-dir that it puts any error in the actual vc-dir
buffer. A multi-line backtrace from a crashing external program is not a
typical expected case.
[1] http://lists.gnu.org/archive/html/help-gnu-emacs/2012-04/msg00145.html
next prev parent reply other threads:[~2012-04-13 0:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 17:40 bug#11230: 24.1.50; VC doesn't handle internal errors? Deniz Dogan
2012-04-12 17:44 ` Glenn Morris
2012-04-12 17:53 ` Deniz Dogan
2012-04-12 17:56 ` Glenn Morris
2012-04-12 17:58 ` Deniz Dogan
2012-04-12 18:08 ` Glenn Morris
2012-04-12 18:15 ` Deniz Dogan
2012-04-12 19:00 ` Glenn Morris
2012-04-12 19:03 ` Deniz Dogan
2012-04-13 0:21 ` Glenn Morris [this message]
2012-04-12 19:12 ` Eli Zaretskii
2012-05-13 13:52 ` Christoph Scholtes
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=bbpqbco50h.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=11230@debbugs.gnu.org \
--cc=deniz@dogan.se \
/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).