Package: darcs
Version: 1.0.2-1
Followup-For: Bug #305883

I have set $EDITOR, $DARCS_EDITOR, and $VISUAL to /usr/bin/vi, 
which on my machine is a symlink to /etc/alternatives/vi, 
which is a symlink to /usr/bin/nvi, yet darcs still fails to 
edit a long comment. I have nano, but I don't have emacs.

A sample session.

$ mkdir bugtest
$ cd bugtest
$ touch foo
$ darcs init
$ ls
_darcs foo
$ darcs add foo
$ darcs record
Darcs needs to know what name (conventionally an email address) to use as the
patch author, e.g. 'Fred Bloggs <[EMAIL PROTECTED]>'.  If you provide one
now it will be stored in the file '_darcs/prefs/author' and used as a default
in the future.  To change your preferred author address, simply delete or edit
this file.

What is your email address? William S <[EMAIL PROTECTED]>
addfile ./foo
Shall I record this patch? (1/1) [ynWsfqadjk], or ? for help:  y
What is the patch name? test
Do you want to add a long comment? [yn] y
sh: line 1: emacs: command not found
sh: line 1: emacs: command not found
Received SIGHUP or SIGTERM
Finished recording patch 'test'
$

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-386lmznofb
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages darcs depends on:
ii  libc6                  2.3.2.ds1-22      GNU C Library: Shared libraries an
ii  libcurl3               7.13.2-2          Multi-protocol file transfer libra
ii  libgmp3                4.1.4-6           Multiprecision arithmetic library
ii  libidn11               0.5.13-1.0        GNU libidn library, implementation
ii  libncurses5            5.4-4             Shared libraries for terminal hand
ii  libreadline4           4.3-11            GNU readline and history libraries
ii  libssl0.9.7            0.9.7e-3          SSL shared libraries
ii  zlib1g                 1:1.2.2-4.sarge.1 compression library - runtime

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to