I'm completely baffled how the developers can add such bugs to a stable, decades-old product. Regardless of whether the bugs get fixed, it's shaken my confidence that I can trust JOE not to screw up my work. (Even 3.x JOE gets into screwed-up states and crashes from time to time; I trust 4.x JOE even less. Even the "save often" mantra I'm cautious about, since I don't want to save data from a screwed-up state. That's worse than straight-up crashing.)
This is the best way to influence the development direction and we certainly do fix issues.
Thanks for all your work developing and maintaining JOE. My apologies for such a negative earlier post; I would not get so easily frustrated if I did not rely on JOE every day :)
The best "protection" I've seen in this space is to log all changes to the edited document, through a simple (and therefore easy to prove correct) code path. The only editor I've ever seen do this was a Xilinx schematic editor. The editor crashed all the time, but I never lost work, since on restart, the editor simply replayed what it had in its log. (This was fun to watch!) Of course this method isn't foolproof, but it went a long way making me feel confident my work wouldn't be lost.
I love love love the interface, which keeps me on it, but I've been bitten enough to lose trust that I won't get bitten in the future.
Obviously if I had a real snag with it I would start with bug reports and if that didn't get the problem sorted, then I would either get my wallet out and hire a programmer or fix it myself.
Found it here (noticed this link was submitted to HN in the past):
Edit: Seems that i was still using an older version, and said behavior has changed in more recent versions.
If you use Ctrl-K Q, then it works the way you expect. Notice that it says "Hit Ctrl-K Q to exit or Ctrl-K H for help" when you first start the editor. I added this beginning with version 4.2 for this very reason.
Also, if you try "jpico" JOE further emulates nano (pico is nano's predecessor).
I always thought the verbs were obviously better. Better the quicker you're reading the dialog, and most users don't bother reading it all.
To be clear with what I mean:
1. Do you want to save your data before exiting?
[Yes] [No] [Cancel]
2. Do you want to save your data before exiting?
[Save] [Discard] [Cancel]
I think GUIs took so long coming around because of the command line.
Maybe you have a .joerc file in your home directory with the old bindings.
A lot of what I do is under version control, but not everything is, and a 3-character "revert buffer" command makes more sense to me than a longer VCS command that will also discard changes that might already be present in the on-disk version of the file.
It just strikes me as a feature where I'd have to rebuild my basic assumptions of how an editor works, without the incentive of a worthwhile improvement to the workflow.
Easy stuff takes a small amount of knowledge, but more advanced features make the editor worthwhile for long-term use.
In my opinion an editor for system administration should try to show as much information as possible by default and horizontal scrolling is an opposite of that.
I'm a bit surprised to see it still is around. I eventually switched to vi, since it was reliably available on most systems.
The hex editor is reasonably nifty too.
(Also, in this case: Joe is a classic, well-known piece of software.)
Supposedly it's better now??
As of a few weeks ago, we also now scan for malware in case third party developers are adding their own adware: https://sourceforge.net/blog/sourceforge-now-scans-all-proje...
EDIT: relevant announcement from January 2016: https://sourceforge.net/blog/sourceforge-acquisition-and-fut...
It's hard to think of a domain name with a worse reputation in tech circles.
I'm glad to see it's still going. Freshmeat/Freecode is now a time capsule sadly.