>> And not with any non-cygwin program. bzr is in python, rather than an
>> executable/binary file. The combination of native Emacs and cygwin is
>> very common.
cgf> I sure love bold assertions with no supporting facts.
cgf> Here's my counter to that: No it isn't.
Have it which eve
cgf> On Wed, Sep 10, 2008 at 04:27:30PM +0200, Phillip Lord wrote:
>> The cygwin package of bzr works only within cygwin bash. This is not true
>> to cvs or svn which work outside; for example, within a dos shell, "bzr"
>> gives "No such program"
The cygwin package of bzr works only within cygwin bash. This is not
true to cvs or svn which work outside; for example, within a dos shell,
"bzr" gives "No such program" errors.
Likewise, cygwin bzr doesn't work properly with Emacs vc-bzr.el --
again, with no such program errors.
The reason f
>>>>> "PL" == Phillip Lord <[EMAIL PROTECTED]> writes:
PL> I am getting some confusing behaviour from cygwin that I don't
PL> understand. Essentially, UNC files names appear to be behaving
PL> very differently between the console and when
I am getting some confusing behaviour from cygwin that I don't
understand. Essentially, UNC files names appear to be behaving very
differently between the console and when sshing into the machine.
I have the following set up (--> means a symlink)
~/mnt/webpages --> //homepages/with/unc/na
5 matches
Mail list logo
