From: Dan Nicolaescu <dann@ics.uci.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 5291@debbugs.gnu.org
Subject: bug#5291: 23.1.91; "bzr status" FAILED
Date: Sat, 2 Jan 2010 14:17:30 -0800 (PST) [thread overview]
Message-ID: <201001022217.o02MHUE3013455@godzilla.ics.uci.edu> (raw)
In-Reply-To: <837hs0dw32.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 02 Jan 2010 23:40:33 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> > Date: Sat, 2 Jan 2010 12:47:00 -0800 (PST)
> > From: Dan Nicolaescu <dann@ics.uci.edu>
> > Cc: 5291@debbugs.gnu.org
> >
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> > > I have set up Emacs to be the EDITOR for bzr via emacsclient (yes, I'm
> > > invoking bzr from the command line). That works, but every time I
> > > commit a file to upstream, Emacs bitches with the following message in
> > > *Messages*:
> > >
> > > vc-do-command: Running bzr status bzr_log.uuzkwa...FAILED (status 3)
> >
> > Do you get a backtrace if you set debug-on-error?
>
> Yes, see below.
>
> AFAICT, it shouldn't even try to run "bzr status" on this file, since
> it's a temporary file used by bzr for the commit message. But if it
> somehow must run "bzr status", then it shouldn't signal an error when
> it predictably fails. But maybe I'm missing something.
>
> Debugger entered--Lisp error: (error "Running bzr status bzr_log.ahvp69...FAILED (status 3)")
> signal(error ("Running bzr status bzr_log.ahvp69...FAILED (status 3)"))
> error("Running %s...FAILED (%s)" "bzr status bzr_log.ahvp69" "status 3")
> vc-do-command(t 0 "bzr" "d:/gnu/bzr/emacs/trunk/bzr_log.ahvp69" "status")
> apply(vc-do-command t 0 "bzr" "d:/gnu/bzr/emacs/trunk/bzr_log.ahvp69" "status" nil)
> vc-bzr-command("status" t 0 "d:/gnu/bzr/emacs/trunk/bzr_log.ahvp69")
> vc-bzr-status("d:/gnu/bzr/emacs/trunk/bzr_log.ahvp69")
> vc-bzr-state("d:/gnu/bzr/emacs/trunk/bzr_log.ahvp69")
> vc-bzr-state-heuristic("d:/gnu/bzr/emacs/trunk/bzr_log.ahvp69")
> vc-bzr-registered("d:/gnu/bzr/emacs/trunk/bzr_log.ahvp69")
> apply(vc-bzr-registered "d:/gnu/bzr/emacs/trunk/bzr_log.ahvp69")
> vc-call-backend(Bzr registered "d:/gnu/bzr/emacs/trunk/bzr_log.ahvp69")
> #[(b) "\302\b\303 #\205\x14\304 \305\b#\205\x14\306\307\310\"\207" [b file vc-call-backend registered vc-file-setprop vc-backend throw found t] 4](Bzr)
> mapc(#[(b) "\302\b\303 #\205\x14\304 \305\b#\205\x14\306\307\310\"\207" [b file vc-call-backend registered vc-file-setprop vc-backend throw found t] 4] (RCS CVS SVN SCCS Bzr Git Hg Mtn Arch))
> byte-code("\303\b\304\"\x19\305\306 \203\x11 \307=\203\x15\n\202\x18 \nB\"\210)\310\b\304\307#\210\311\207" [file backend vc-handled-backends vc-file-getprop vc-backend mapc #[(b) "\302\b\303 #\205\x14\304 \305\b#\205\x14\306\307\310\"\207" [b file vc-call-backend registered vc-file-setprop vc-backend throw found t] 4] none vc-file-setprop nil] 4)
> vc-registered("d:/gnu/bzr/emacs/trunk/bzr_log.ahvp69")
> vc-backend("d:/gnu/bzr/emacs/trunk/bzr_log.ahvp69")
> vc-after-save()
> basic-save-buffer()
> save-buffer(1)
> call-interactively(save-buffer nil nil)
Strange.
What exactly creates the d:/gnu/bzr/emacs/trunk/bzr_log.ahvp69 file?
Is your TEMP set to d:/gnu/bzr/emacs/trunk/ ?
I think that if you change:
(vc-bzr-command "status" t 0 file)
to:
(vc-bzr-command "status" t 3 file)
in vc-bzr-status
it should work, but I am not 100% sure that's TRTD.
next prev parent reply other threads:[~2010-01-02 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83637baejr.fsf@gnu.org>
2010-01-02 17:43 ` bug#5291: 23.1.91; "bzr status" FAILED Eli Zaretskii
2010-01-02 20:47 ` Dan Nicolaescu
2010-01-02 21:40 ` Eli Zaretskii
2010-01-02 21:56 ` Lennart Borgman
2010-01-02 22:17 ` Dan Nicolaescu [this message]
2010-01-03 4:09 ` Eli Zaretskii
2010-01-03 18:39 ` Eli Zaretskii
2010-01-03 20:10 ` Dan Nicolaescu
2010-01-09 8:07 ` bug#5291: marked as done (23.1.91; "bzr status" FAILED) Emacs bug Tracking System
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=201001022217.o02MHUE3013455@godzilla.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=5291@debbugs.gnu.org \
--cc=eliz@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).