The JED Programmer's Editor (2017)(jedsoft.org)
jedsoft.org
The JED Programmer's Editor (2017)
http://www.jedsoft.org/jed/
30 comments
Somewhere around 1994, I used to dial into the university's terminal server using a Wyse 370 and a 9600 baud modem. (Note, this was not PPP or SLIP providing TCP/IP. You had to type the atdt modem commands directly...) This particular terminal had 64 colors as an extension to the VT100 command sequences. I sent an email to John E Davis asking if he'd be willing to add support for my one off color capability, and he did! Super nice guy, and JED was one of the first things I compiled on every new Unix account I got for several years after that. I was very happy with very colorful source code.
I remember JED! When I started out on Linux in 1997 (coming from DOS/Windows) I was forced to choose an editor. There was Pico which was specific to the `pine` e-mailer (this was before nano), and of course vi and emacs.
I didn't want to invest the time to learn vi or emacs so I used JED for a while, and it served me well. But coming from DOS, JED still had a bit of a learning curve. I figured if I was going to pick up a totally foreign editor, I should probably just bite the bullet and learn vi or emacs.
I settled on vi(m) eventually and never looked back. JED helped me make the transition though.
There was also an editor JOE which had Turbo C keybindings. That would have been a great fit for DOS heads like me but I learned about it too late. The ship had sailed. (it's just as well -- I now have vim muscle memory, which is far more useful)
I didn't want to invest the time to learn vi or emacs so I used JED for a while, and it served me well. But coming from DOS, JED still had a bit of a learning curve. I figured if I was going to pick up a totally foreign editor, I should probably just bite the bullet and learn vi or emacs.
I settled on vi(m) eventually and never looked back. JED helped me make the transition though.
There was also an editor JOE which had Turbo C keybindings. That would have been a great fit for DOS heads like me but I learned about it too late. The ship had sailed. (it's just as well -- I now have vim muscle memory, which is far more useful)
Having a strong Turbo Pascal background, with liberal use of EDIT.COM as my "IDE" for Turbo Assembler, joe was a welcome replacement dir vi when I really started getting into Linux back in the 90s. I still have it loaded on a couple of boxes today. The key bindings are so familiar and "comfortable".
But have you tried Jed?
Joe is still around, and actually quite usable/performant. If it's invoked as "jstar", it gets even closer to WordStar/TurboPascal keybindings. It can also do "jmacs" which has Emacs keybindings, the default "joe" configuration being something in between.
Does syntax highlighting, incremental search, regexes, and all that pretty fast.
If we're talking old DOS editors, JED actually has a quite decent BRIEF emulation.
Does syntax highlighting, incremental search, regexes, and all that pretty fast.
If we're talking old DOS editors, JED actually has a quite decent BRIEF emulation.
> old DOS editors.
PC-Write key bindings are out there too..
PC-Write key bindings are out there too..
Jed is amazing, I use it daily.
I still have on by backburner to learn how to actually customize it, but I make do with the standard configuration most of the time.
What I like about it.
- Wordstar-like interface (file menu, etc)
- fast
- 100% sane user experience, with program options that I can wrap my head around. Minimum of arcane stuff.
- Emacs-lisp compatible (somehow, I don't know, I just see that it's there)
- Multi platform!
Anybody here have any .config files published to Git/lab/hub where I can look for some ideas for customizing Jed?
EDIT: I guess the website contains all the resources I need to learn more about customizing the program.
I still have on by backburner to learn how to actually customize it, but I make do with the standard configuration most of the time.
What I like about it.
- Wordstar-like interface (file menu, etc)
- fast
- 100% sane user experience, with program options that I can wrap my head around. Minimum of arcane stuff.
- Emacs-lisp compatible (somehow, I don't know, I just see that it's there)
- Multi platform!
Anybody here have any .config files published to Git/lab/hub where I can look for some ideas for customizing Jed?
EDIT: I guess the website contains all the resources I need to learn more about customizing the program.
Looks like a borland IDE!
https://www.jedsoft.org/images/jed1.png
I don't use JED but I do use `most` from time to time, as a replacement for the `less` pager. I like the keybindings better. Apparently, it is implemented with S-Lang too.
https://www.jedsoft.org/most/docs.html
https://www.jedsoft.org/images/jed1.png
I don't use JED but I do use `most` from time to time, as a replacement for the `less` pager. I like the keybindings better. Apparently, it is implemented with S-Lang too.
https://www.jedsoft.org/most/docs.html
SLRN used to be be a pretty popular newsreader implemented with S-Lang, never mind that S-Lang, sans the language part, was a quite common alternative to ncurses as a terminal interface.
The language itself is... interesting. C-like, but with some array-based constructs and quite a large amount of backwards compatibility -- there's a "_for" statement and default arguments are weird, as they're not mentioned in the prototype, but just done in the main body. It's a bit like Perl, but without the logic.
The language itself is... interesting. C-like, but with some array-based constructs and quite a large amount of backwards compatibility -- there's a "_for" statement and default arguments are weird, as they're not mentioned in the prototype, but just done in the main body. It's a bit like Perl, but without the logic.
Oh, I do miss slrn. Even now I still get spam to `slrn` email addresses from usenet spammers.
Well, it's more like a weird mix of Emacs and old borland/ms IDE's. The menubar is great (and Emacs should just look like that by default, IMO), but overall it's missing useful cues like scrollbars and titlebars. The minibuffer-like area at the bottom looks a bit weird, whereas it could easily be reskinned as an "expanded" status bar, for consistency with the classic TUI/GUI look.
I used to work at a very small network engineering shop where JED was the primary terminal editor used (mainly because it was the CTO's flavor of choice). It's lightweight and easy to learn with Emacs keybindings, but I'd never use it for doing anything more than quick edits and scripting.
These days, though, an editor not providing Vim emulation pretty much counts it out for me
These days, though, an editor not providing Vim emulation pretty much counts it out for me
Wikipedia entry:
JED is a text editor that makes extensive use of the S-Lang library. It is highly cross-platform compatible; JED runs on Windows and all flavors on Linux and Unix. Older versions are available for DOS. It is also very lightweight (meaning very parsimonious in its use of system resources), which makes it an ideal editor for older systems, embedded systems, etc. JED's Emacs mode is one of the most faithful emulations available.
https://en.wikipedia.org/wiki/JED_(text_editor)
JED is a text editor that makes extensive use of the S-Lang library. It is highly cross-platform compatible; JED runs on Windows and all flavors on Linux and Unix. Older versions are available for DOS. It is also very lightweight (meaning very parsimonious in its use of system resources), which makes it an ideal editor for older systems, embedded systems, etc. JED's Emacs mode is one of the most faithful emulations available.
https://en.wikipedia.org/wiki/JED_(text_editor)
I used to use lightweight editors on small systems like vi (not vim, the smaller vi).
But when I discovered emacs tramp mode, I sort of got away from that.
emacs comes with tramp mode built-in and allows you to edit a file on even very small embedded devices using only ssh.
I think it might work on telnet or other protocols, but I've never tried them.
for example
or
But when I discovered emacs tramp mode, I sort of got away from that.
emacs comes with tramp mode built-in and allows you to edit a file on even very small embedded devices using only ssh.
I think it might work on telnet or other protocols, but I've never tried them.
for example
emacs /ssh:foo:/etc/bar.cfg
or
emacs /ssh:user@host:.profileThe thing which I wish was easy is having ssh pass enough things forward (and backward) that you can ssh somewhere, run emacsclient on a file and have that file show up (via tramp) in your emacs.
It’s just about possible but hard and hacks and not really supported by ssh.
It’s just about possible but hard and hacks and not really supported by ssh.
The syntax for tramp-mode is on the arcane side.
I mostly use emacs /ssh:ab:.bashrc which I think compares favorably with
my .ssh/config contains a "Host ab" section for particulars about logging into the machine.
Although you have a point. For instance there is a weird bug or two in tramp mode, like (absolute-file-p "/ssh:ab:.bashrc") erroneously returns t
ssh ab
emacs .bashrc
my .ssh/config contains a "Host ab" section for particulars about logging into the machine.
Although you have a point. For instance there is a weird bug or two in tramp mode, like (absolute-file-p "/ssh:ab:.bashrc") erroneously returns t
What's arcane in /[protocol]:[login]@[machine]:[path to remote file]?
I've been using Jed as my primary editor for the past 20 years.
Originally because it was faster than Emacs while providing the same experience.
Then because I loved how its automatic indentation works ("tab" properly indents the current line), and I still can hardly use an editor that doesn't behave in a similar way.
Finally, the language extensions are written in ("slang") is great. It feels familiar, is readable and is easy to pickup, unlike Emacs Lisp.
Jed and Piknik are the two first things I install on any new computer.
Today, in order to write Rust code, I use VSCode, but for everything else, Jed remains my go to editor.
Originally because it was faster than Emacs while providing the same experience.
Then because I loved how its automatic indentation works ("tab" properly indents the current line), and I still can hardly use an editor that doesn't behave in a similar way.
Finally, the language extensions are written in ("slang") is great. It feels familiar, is readable and is easy to pickup, unlike Emacs Lisp.
Jed and Piknik are the two first things I install on any new computer.
Today, in order to write Rust code, I use VSCode, but for everything else, Jed remains my go to editor.
> Extensible in the C-like S-Lang language making the editor completely customizable.
I wonder if this is like Emacs level customizable or just regular editor customizable.
I wonder if this is like Emacs level customizable or just regular editor customizable.
Interesting* fact: the "Lynx Style Sheets" highlighting was originally done using S-Lang. Dunno if it's been extended to ncurses since.
Used JED in the 90s to 00s until nano became a default lightweight editor. Was a lot faster to start for small edits than Emacs. Really liked the editor.
The thing with emacs is that you normally wouldn’t “start for small edits.” Rather, you’d start it early in the morning and close it late at night (if ever).
(Not to be confused with jEdit.)
That's a blast from the past; I remember using this in the 90s as a programming editor for the HP100lx pocket computer (a 186 running MS-DOS5). Quite zippy even on that limited hardware.
It was my go to for a long time for editing over ssh. I eventually broke down and learned enough vi to get by, but jed has zero learning curve and syntax highlighted everything without installing packages
Jed was the first editor I really like back on slacklinux something or other. I learned vim and never... No wait, I love evil emacs :)
I used jed as my lightweight alternative to Emacs for a very long time. I stopped doing so a year or two ago and now just emacs.