Thanks for the reply Mark! I tried setting the comspec to 4nt.exe and
it didn't appear to fix the issue. I did notice that by default,
comspec is set to 4nt when you're running from within 4nt. I'm
running Unicode build 126, 5.00U. I'll keep digging..
Also, if you can, what directories do you have svn and 4nt installed
in? I'm curious to see if either install path has spaces contained
within it. Thanks.
On Tue, 22 Jun 2004 23:16:22 -0400, Mark Watts <mwatts3@stny.rr.com> wrote:
>
> Hi Ben,
> I am also a 4NT user and I have been using subversion on WinXP Pro for
> months, perhaps more than a year and I don't have the problem you describe.
> I am running the Unicode build: 4NT 5.00U Build 106. One thing that is a
> bit unusual that I have done that 'might' affect things, is that I have
> changed the 'comspec' environment variable to point to the 4NT exe instead
> of cmd.exe. This meaning that when most well written programs open a
> command prompt I get 4NT instead of cmd.exe. I don't know that this
> difference would cause what you are seeing.
>
> I also use the environment variable SVN_EDITOR to set my editor. Currently
> it is
> SVN_EDITOR=NOTEPAD.EXE
>
> HTH,
> Mark
>
>
> > -----Original Message-----
> > From: Ben Lowery [mailto:blowery@gmail.com]
> > Sent: Tuesday, June 22, 2004 22:29
> > To: users@subversion.tigris.org
> > Subject: using svn on windows inside 4NT
> >
> > Greetings,
> >
> > I just started using subversion (client on windows xp) and I
> > quickly ran into a bit of a snag. My preferred command shell
> > is 4NT (from http://www.jpsoft.com), and svn doesn't seem to
> > play nice with it when attempting to shell out to the editor
> > for commit messages. To illustrate, if I run:
> >
> > set svn_editor=notepad
> > svn commit
> >
> > Another shell instance starts up. Once I exit that instance,
> > the following is printed to the terminal window:
> >
> > svn: Commit failed (details follow):
> > svn: system('notepad svn-commit.tmp') returned 2
> >
> > As workarounds, I've found that the standard cmd.exe shell on
> > windows works just fine. The "svn commit" fires up notepad
> > and I'm able to enter in my little commit message.
> > Additionally, I can use --message="foo" to enter in a message
> > from my 4NT shell. It's just annoying that spawning the
> > editor doesn't seem to work from within 4NT. I've also tried
> > quoting the name of the editor ( set svn_editor="notepad" )
> > and using a different editor ( set svn_editor=emacs ).
> > Nothing really seems to help; I just get the same error message.
> >
> > Now, all this said, I have no idea if this is a bug in 4NT or
> > a bug in how subversion spawns the editor. I would wager
> > it's more an issue with 4NT. 4NT is complaining that it's
> > getting an unknown command (
> > 4NT: Unknown command "C:\Program" ) when the spawn happens,
> > so maybe the tmp file lives in \Program Files\ someplace and
> > the argument needs to be surrounded in quotes to make 4NT
> > happy? I'm unsure.
> >
> > Anyway, I'm curious if any other windows users are using 4NT,
> > and if so, have they run into this problem. I know I'm
> > probably in a minority of a minority here, but I thought I'd
> > give it a shot. :)
> >
> > Thanks for any help,
> >
> > --b
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: users-help@subversion.tigris.org
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 23 05:58:00 2004