darcs

Issue 242 Long comments (Windows)

Title Long comments (Windows)
Priority not-our-bug Status resolved
Milestone Resolved in
Superseder Nosy List darcs-devel, dmitry.kurochkin, gfour, kowey, thorkilnaur, tommy
Assigned To
Topics

Created on 2006-08-12.14:01:45 by gfour, last changed 2009-08-27.13:47:54 by admin.

Files
File name Uploaded Type Edit Remove
darcs kowey, 2006-08-12.14:16:02 text/plain
Messages
msg899 (view) Author: gfour Date: 2006-08-12.14:01:41
Hello,

Congratulations for Darcs, it is very useful and stable. I am using it 
on Windows XP and it fails to launch an external editor for long comments:

Do you want to add a long comment? [yn]
darcs: vi: runProcess: does not exist (No such file or directory)

Sometimes it leaves a lock file (_darcs/lock) behind that has to be 
removed for darcs to run again.
Setting DARCS_EDITOR or changing shell (MSYS/cmd.exe) doesn't seem to 
correct the problem.

I am using the latest Darcs .exe build (1.08):
$ darcs --exact-version
darcs compiled on Jun 16 2006, at 13:00:32
# configured Fri Jun 16 12:59:52 USMST 2006
./configure --disable-mmap

Context:

[TAG 1.0.8
Tommy Pettersson <ptp@lysator.liu.se>**20060616160213]

Thank you
-- 
Giorgos
msg900 (view) Author: kowey Date: 2006-08-12.14:16:07
Hi,

On Sat, Aug 12, 2006 at 14:01:45 +0000, Giorgos Fourtounis wrote:
> Congratulations for Darcs, it is very useful and stable. I am using it 
> on Windows XP and it fails to launch an external editor for long comments:
> 
> Do you want to add a long comment? [yn]
> darcs: vi: runProcess: does not exist (No such file or directory)

I suspect this is a duplicate of issue51.  Are you using Cygwin?

If so, try maybe replacing your darcs script with the attached.
The only difference is that it exports the PATH, which supposedly,
Cygwin detects and inserts into the Windows system path.  Alternately,
you could edit the Windows path yourself, which likely involves
clicking around in the Control Panel.
Attachments
msg901 (view) Author: gfour Date: 2006-08-12.14:44:10
Eric Kow wrote:

Thank you for your feedback, in fact it was caused by bad 
runProcess(MSYS?) behavior (I am not using cygwin):

'vi' is a symlink to 'vim' but since symlinks in windows do not exist in 
their UNIX form, it seems that runProcess can't run them.

The solution is to set DARCS_EDITOR  to the full path of an editor - 
emacs (windows port) works OK, (vim.exe (MSYS version) runs but still 
can't see the console correctly, but this has nothing to do with Darcs).
msg902 (view) Author: kowey Date: 2006-08-12.14:58:24
Good deal.  Marking not-our-bug/resolved.
History
Date User Action Args
2006-08-12 14:01:45gfourcreate
2006-08-12 14:16:07koweysetfiles: + darcs
status: unread -> unknown
messages: + msg900
nosy: + kowey
2006-08-12 14:44:13gfoursetnosy: droundy, tommy, kowey, gfour
messages: + msg901
2006-08-12 14:58:27koweysetstatus: unknown -> resolved
nosy: droundy, tommy, kowey, gfour
messages: + msg902
2009-08-06 17:38:06adminsetnosy: + markstos, jast, Serware, dmitry.kurochkin, darcs-devel, zooko, dagit, mornfall, simon, beschmi, thorkilnaur, - droundy, gfour
2009-08-06 20:51:23adminsetnosy: - beschmi
2009-08-10 21:54:33adminsetnosy: + gfour, - markstos, darcs-devel, zooko, jast, dagit, Serware, mornfall
2009-08-25 17:51:44adminsetnosy: + darcs-devel, - simon
2009-08-27 13:47:54adminsetnosy: tommy, kowey, darcs-devel, gfour, thorkilnaur, dmitry.kurochkin