monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Monotone-devel] Unexpected Behavior


From: Nathaniel Smith
Subject: Re: [Monotone-devel] Unexpected Behavior
Date: Mon, 11 Sep 2006 16:05:56 -0700
User-agent: Mutt/1.5.13 (2006-08-11)

On Mon, Sep 11, 2006 at 03:39:43PM -0700, Rob Schoening wrote:
>    When I was setting up ViewMTN last week (thanks to the helpful posts with
>    revisions/patches needed to work with 0.29)  I noticed something
>    unexpected.
> 
>    When I ran "mtn update -r" to switch my workspace to a particular
>    revision, it seemed to be sourcing one of the project files (mtn.py) and
>    then complained about the syntax of the file which prevented the update
>    operation from completing.  It was as if " mtn.py" was being loaded as
>    some kind of hook.
> 
>    It was easy enough to work around by descending into a sub-directory and
>    run "mtn update -r" from there since mtn.py was not present.
> 
>    Does anyone know if this is a feature or a bug?

If monotone is reading a file 'mtn.py' out of the current working
directory and trying to execute it, then that is definitely a bug, but
it seems like a... really unlikely one.

Need more details to tell what's going on.  Possibly you're on a
system that searches the current directory for executables, and
searches for executables with extra extensions appended?  (E.g., I
think you can tell windows to treat foo.py files like foo.exe files,
i.e., both executable by running "foo".)

-- Nathaniel

-- 
So let us espouse a less contested notion of truth and falsehood, even
if it is philosophically debatable (if we listen to philosophers, we
must debate everything, and there would be no end to the discussion).
  -- Serendipities, Umberto Eco




reply via email to

[Prev in Thread] Current Thread [Next in Thread]