this has been a problem for quite a few versions of joe, but I just
rembered now, sorry. Perhaps something to fix for 2.9.9.
When I call joe with a few filenames using "xargs", joe opens a host of
frames and then ... exits. Too many frames perhaps?
I do something like this:
$ find . -type f -name \*.c | xargs joe
A file "DEADJOE" is created with the contents:
*** Modified files in JOE when it aborted on Mon Oct 29 17:07:31 2001
*** JOE was aborted because the terminal closed
I'm attaching the output of "truss" (as joe.truss), which is somewhat
an equivilant of "strace" on Solaris. I can't actually see any reason
between opening the last file, printing the status line, and then
writing "DEADJOE". Hmm.
Now, the funny thing is: If I call joe directly with the same set of
arguments, everything's fine!
$ joe `find -type f -name \*.c`
(Except for one thing: I hold Ctrl-C pressed, and the last file then
mucks up the display. Oh well, minor stuff.)
Well, it seems joe doesn't like xargs at all:
$ echo usearch.c | xargs joe
Same phenomenon! Actually, xargs should call joe with the same stdin
and stdout, without a pipe. It's just a tool for calling joe with
arguments. What's up?
(There's a truss output for this attached as well, because it's
shorter, joe.truss.02 .)
Anybody for investigations?
Shall I post the bug to sourceforge.net?
> $ echo usearch.c | xargs joe
Neither works on Linux. Must be a bug (feature?) of xargs, independently
from joe. You should leave the stdin of joe free from any utilities,
connected right to your terminal.