all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Phillip Lord <phillip.lord@newcastle.ac.uk>
Cc: bug-gnu-emacs@gnu.org, 927@emacsbugs.donarmstrong.com
Subject: bug#927: vc-bzr.el with cygwin bzr
Date: Tue, 09 Sep 2008 10:22:57 -0400	[thread overview]
Message-ID: <jwvmyihh03v.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <EMEW-k87Apice9530e8475d9d47319e7a7e303043f9-81ej3v6k46.fsf@newcastle.ac.uk> (Phillip Lord's message of "Mon, 08 Sep 2008 11:51:37 +0200")

> My hack is platform specific. A better solution would be, to modify
> vc-bzr-command to be either of the form "bzr-program-name" or '("python
> name" "bzr name"). vc-bzr-command would need to be modified to cope.
> There is couple of other places vc-bzr-command is used which would need
> changing also. 

A better solution would be to write a w32 wrapper for Bzr (an plain w32
executable that runs python with the bzr script), so that it does not
rely on cygwin's own handling of #!

After all, does Cygwin's bzr work with any other program that's not part
of Cygwin?  I'd guess not, which is why I think the problem is not
specific to Emacs.


        Stefan







  reply	other threads:[~2008-09-09 14:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08  9:51 bug#927: vc-bzr.el with cygwin bzr Phillip Lord
2008-09-09 14:22 ` Stefan Monnier [this message]
     [not found] ` <EMEW-k88FN4d513b6d9437cad00641ec17907dfd5b8-jwvmyihh03v.fsf-monnier+emacsbugreports@gnu.org>
2008-09-09 14:44   ` Phillip Lord
2008-09-09 17:22     ` Stefan Monnier
     [not found]     ` <EMEW-k88IMHa0452283789433ad2c459dd52d31d774-jwvsks9qlqs.fsf-monnier+emacsbugreports@gnu.org>
2008-09-10 14:33       ` Phillip Lord
2008-09-11 16:32       ` Phillip Lord

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=jwvmyihh03v.fsf-monnier+emacsbugreports@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=927@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=phillip.lord@newcastle.ac.uk \
    /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.