Fossil: Ticket Change Details

Changes to ticket 8c46da2079

By kkinnell on 2008-12-12 20:33:57. See also: artifact content, and ticket history

Change comment to "Problem only exists (for me) in Cygwin on Windows. I have vi installed in Cygwin, and `which' reports it to be: <verbatim> $ which vi /usr/bin/vi </verbatim> So, I manually set my fossil editor, using `fossil set editor /usr/bin/vi'. When I checkin, I get: <verbatim> $ fossil.exe ci Autosync: http://sentry:8080/ Bytes Cards Artifacts Deltas Send: 87 1 0 0 40The system cannot find the path specified. Received: 1794 40 0 0 /usr/bin/vi "C:/cygwin/home/User1/src/ci-comment-A97A91FD685A.txt" C:\cygwin\bin\fossil.exe: editor aborted </verbatim> The next to the last line seems to be the command that is `fork()'ed? If I copy and paste that line in, `vi' is launched with the normal checkin file, ("# Enter comments on this commit. Lines beginning with # are ignored"... etc) If I `fossil set editor notepad', notepad opens the file correctly. If I `fossil.exe set editor "C:\\Program\\ Files\\Vim\\vim70\\gvim.exe"', I get: <verbatim> $ fossil.exe ci Autosync: http://sentry:8080/ Bytes Cards Artifacts Deltas Send: 87 1 0 0 40'C:\Program\' is not recognized as an internal or external command, operable program or batch file. Received: 1794 40 0 0 C:\Program\ Files\Vim\vim70\gvim.exe "C:/cygwin/home/User1/src/ci-comment-C042442842F0.txt" C:\cygwin\bin\fossil.exe: editor aborted </verbatim> (I also tried with every combination of forward- and back-slashes, and quoting of the space character, with similar results.) <hr>anonymous claiming to be Kees Nuyt added on 2008-12-11 23:57:37: Are you sure the path is * C:\Program\ Files\Vim\vim70\gvim.exe ? Shouldn't that be * C:\Program Files\Vim\vim70\gvim.exe ? If you have a choice, you'd better install unix-like tools in directories outside the 'standard' Windows directories, for example * C:\bin\Vim\vim70\gvim.exe By the way, modern versions of MS Windows (XP, Vista) can handle forward slashes quite well internally. You will only get into trouble with the classic command line utilities, which still reserve the forward slash as the default 'option' character. <hr>kkinnell added on 2008-12-12 07:33:27: Another test it might good to run would be to try to checkin using the <code>-m "checkin comment"</code> option. At the very least it would save you from the evil clutches of vi. (Hehe. A little joke, not an invitation to the flame wars. I list Emacs as one of my Operating Systems skills on my resumé.) <hr>anonymous added on 2008-12-12 15:03:22: Shouldn't that be * C:\Program Files\Vim\vim70\gvim.exe ? Yes, I tried that first. I should have been more explicit than just saying "quoting of the space character". And I avoid using the <code>-m</code> option, because I often just do a checkin without a filename, so that all files that I have changed are checked in, without me knowing about it. At least when I use the superior editor vi, :^) the comment section tells me what files are being checked in. I probably need to change my workflow, I know, but old habits... It looks on the surface to be a problem with pathnames that have spaces in them?"