From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Novimir Pablant <mir@amicitas.com>
Cc: 3122@emacsbugs.donarmstrong.com
Subject: bug#3122: Error saving commit messages for bazaar (bzr).
Date: Sun, 26 Apr 2009 23:02:28 -0400 [thread overview]
Message-ID: <jwvr5zeu9ee.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <49F4E687.4010108@amicitas.com> (Novimir Pablant's message of "Sun, 26 Apr 2009 15:56:07 -0700")
> vc-bzr-registered: IO error reading
> c:/library/code/python/annotatex/releases/test/.bzr/checkout/dirstate:
> Permission denied
> Bazaar version 1.13
> Emacs version 22.3
Can you try and reproduce this bug with the Emacs-23 pretest?
Also, as far as I can tell, the code in vc-bzr.el (in Emacs-22.3 as
well as in the upcoming Emacs-23) checks (file-readable-p dirstate)
before reading the file, so could you check:
M-: (file-readable-p "c:/library/code/python/annotatex/releases/test/.bzr/checkout/dirstate") RET
to see if it indeed returns t rather than nil. And then try
M-: (insert-file-contents "c:/library/code/python/annotatex/releases/test/.bzr/checkout/dirstate") RET
to check that it indeed signals the error you're seeing.
If indeed, file-readable-p claims the file is readable, but
insert-file-contents signals a "permission denied", then the problem
seems to be in the C code (or even deeper such that there's no way for
Emacs to predict that insert-file-contents will signal an error).
Stefan
next prev parent reply other threads:[~2009-04-27 3:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 22:56 bug#3122: Error saving commit messages for bazaar (bzr) Novimir Pablant
2009-04-27 3:02 ` Stefan Monnier [this message]
2009-04-27 5:52 ` Novimir Pablant
2009-04-27 18:25 ` Eli Zaretskii
2009-04-29 5:58 ` Novimir Pablant
2009-04-29 7:06 ` Eli Zaretskii
2009-04-29 19:02 ` Novimir Pablant
2009-04-29 20:29 ` Stefan Monnier
2020-08-20 18:54 ` Lars Ingebrigtsen
2020-08-20 19:30 ` Eli Zaretskii
2020-08-20 19:43 ` 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=jwvr5zeu9ee.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=3122@emacsbugs.donarmstrong.com \
--cc=mir@amicitas.com \
/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.