Program "jupp" is unresponsive when invoked as "joe" .

[Valentin Quequet]

Hi, Dear reader!

I am using 64-bit Ubuntu Linux 13.04 on x86_64 arch (PC Laptop).

"${HOME}/.joerc" is a regular empty file with proper permissions ( 0664 ).

I used to use "joe" on a regular basis and this program was just on purpose for my needs, but recently (when?) it broke.

Now, when I type "joe" on commandline, the text editor is useless: not even a key press echoes on the screen. Not even able to C^K-Z or C^K-X or C^K-Q.

But if I run the program as "jupp" it functions just right.

I am using "jupp" version v3.1jupp24 (Ubuntu 13.04 program version 3.1.24-1).

I experience the trouble whichever the terminal emulator I use, and in a "/usr/bin/screen" session too, and even on the bare Linux console.

Is this intended behavior (a feature, not a bug of course), or could we suspect bad detection of terminal capabilities?

Why the hell does "jupp" functions just right while "joe" is out-of-order? Unmaintained code?

In hope my bug report will prove useful.

Kind regards,
Valentin QUEQUET

[Thorsten Glaser (mirabilos)]

Valentin Quequet dixit:

>"${HOME}/.joerc" is a regular empty file with proper permissions ( 0664
                               ^^^^^^^^^^

If the file is empty, no configuration is available. You need
to delete it or make it a copy of /etc/jupp/joerc (if you use
joe from joe-jupp) or /etc/joe/joerc (if you use joe from joe);
preferably delete it as the system-wide copy gets used then
instead.

>Now, when I type "joe" on commandline, the text editor is useless: not
>even a key press echoes on the screen. Not even able to C^K-Z or C^K-X
>or C^K-Q.

Yes, obviously: if you type joe it first looks for ~/.joerc then
for /etc/jupp/joerc - if one of those exists, it uses it and not
the other. The joerc file contains all information, such as key
bindings, menus, etc.

>In hope my bug report will prove useful.

I'm afraid this counts as "don't do that then" style user error.

bye,
//mirabilos
--
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh

[Valentin Quequet (valentin-quequet)]

Thanks for your fast answer.

Removing empty RC file $HOME/.joerc helped: joe works again.

I don't know how I got that empty RC file, and I mistakenly put the shame on the program itself.

Possibly, this has to do with original "Joe's Own Editor" I used before, who knows?

> I'm afraid this counts as "don't do that then" style user error.
Sure, sorry for the spurious bug report.

Kind regards,
Valentin QUEQUET

[Thorsten Glaser (mirabilos)]

OK, no problem. I'm glad I could help you nevertheless.