I don't believe anything has changed in this respect between 2.2.0-3 and
2.3.0+dfsg-2.
The code for the latter version looks like this:
// Determine correct editor: .taskrc:editor $VISUAL $EDITOR vi
std::string editor = context.config.get (editor);
char* peditor = getenv (VISUAL);
if
hm. funny. It does seem to work indeed. I wonder what I did wrong.
Embarrasing...
$ env EDITOR=cowsay /usr/bin/task 1 edit
Launching 'cowsay task.21721.1.task' now...
sh: 1: cowsay: not found
Editing complete.
No edits were detected.
$
sorry for the noise.
** Changed in: task (Ubuntu)
Interesting. Seems to be a regression then.
env TASKDATA=/tmp/tasks EDITOR=cowsay task 1 edit
does not do what I expect with the 2.3.0 package:
➜ ~apt-cache policy taskwarrior
taskwarrior:
Installed: 2.3.0+dfsg-2
Candidate: 2.3.0+dfsg-2
Version table:
*** 2.3.0+dfsg-2 0
100
I can't reproduce it here:
$ apt-cache policy task
task:
Installed: 2.2.0-3
Candidate: 2.2.0-3
Version table:
*** 2.2.0-3 0
500 http://cz.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
100 /var/lib/dpkg/status
$ task add moo
Created task 1.
$ EDITOR=cowsay task
