unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: emacs-devel@gnu.org
Date: Tue, 02 Dec 2014 10:42:12 +0100	[thread overview]
Message-ID: <87k32ajsln.fsf@fencepost.gnu.org> (raw)
In-Reply-To: m3y4qrf1ue.fsf@stories.gnus.org

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> "Eric S. Raymond" <esr@thyrsus.com> writes:
>
>> Lars Magne Ingebrigtsen <larsi@gnus.org>:
>>> > Now I need to try to figure out (a) why removing it broke things, and 
>>> > (b) why it disn't break anything where I coulse see it.  That is concerning.
>>> 
>>> It's because `(vc-bzr-file-name-relative "~/rmz.jpg")' returns nil for
>>> me.  What does it say for you?
>>
>> Same; nil.
>
> Well, looking at the code, `vc-bzr-state' calls `vc-bzr-status' first,
> which does `(regexp-quote (vc-bzr-file-name-relative file))', and if
> that function returns nil for you, then `regexp-quote' should signal an
> error, since that's not a valid input.
>
> So `(vc-bzr-state file)' should signal an error for you.  :-)
>
> Unless I'm totally misreading the code, which is, of course, possible.

Or he has everything under Git anyway so that his Emacs does not bother
checking for other version control system.

-- 
David Kastrup




  reply	other threads:[~2014-12-02  9:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20141201195401.3A72F3832EA@snark.thyrsus.com>
     [not found] ` <m37fyb16wd.fsf@stories.gnus.org>
     [not found]   ` <20141201202026.GA2794@thyrsus.com>
2014-12-01 20:30     ` emacs-devel@gnu.org Lars Magne Ingebrigtsen
2014-12-01 22:09       ` emacs-devel@gnu.org Eric S. Raymond
2014-12-01 22:21         ` emacs-devel@gnu.org Lars Magne Ingebrigtsen
2014-12-02  9:42           ` David Kastrup [this message]
2014-12-02 10:49             ` emacs-devel@gnu.org Andreas Schwab
2014-12-02 11:27               ` vc-bzr-state Ivan Shmakov
2004-04-22 10:03 emacs-devel@gnu.org Mallory furry

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=87k32ajsln.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=emacs-devel@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).