[jed-users] "Fatal Error: Killed by signal 1."

[Michael Stillwell <mjs@xxxxxxxxx>]

I'm having problems when jed is invoked from other programs via the
EDITOR or VISUAL environment.

Often the symptom is that my terminal appears to completely lock up
(this happens, for example, when I do "git commit") but I just noticed
that I get an actual error message when using the "v" command in less,
or even if I execute a shell command via "!".

In more detail, if I run

less .bashrc

then execute the following command from within less (to run jed via a subshell)

!jed .bashrc

I get the error

***Fatal Error: Killed by signal 1.

jed version: 0.99.19/Unix
 Compiled with GNU C 4.2
S-Lang version: 2.3.0

jed compile-time options:
 +LINE_ATTRIBUTES +BUFFER_LOCAL_VARS +SAVE_NARROW +TTY_MENUS
 +EMACS_LOCKING +MULTICLICK +SUBPROCESSES +DFA_SYNTAX +ABBREVS
 +COLOR_COLUMNS +LINE_MARKS -GPM_MOUSE +IMPORT
CBuf: 0x7fea0940e750, CLine: 0x7fea0a020a50, Point 0
CLine: data: 0x7fea094060c0, len = 13, next: 0x7fea0a020a70, prev 0x0
Max_LineNum: 79, LineNum: 1
JWindow: 0x7fea097015f0, top: 0, rows: 43, buffer: 0x7fea0940e750

This reproduces 100% of the time on OS X, but never on Linux. I built
jed (and slang) myself, with pretty standard settings. I can do "!vim
.bashrc", etc.

The other thing that's slightly odd is that whilst I can run jed via
"bash -c jed" and "zsh -c jed", "fish -c jed" (fish is another shell)
gives the same error as above.





Michael
_______________________________________________
For list information, visit <http://jedsoft.org/jed/mailinglists.html>.