3 ms·

Yeah, how could you hate on anyone who uses the standard text editor?[0] [0] https://www.gnu.org/fun/jokes/ed-msg.html https://www.gnu.org/fun/jokes/ed-msg.htm

Yeah, how could you hate on anyone who uses the standard text editor?[0] [0] https://www.gnu.org/fun/jokes/ed-msg.html https://www.gnu.org/fun/jokes/ed-msg.html

bear8642 5y ago
you joke, but ed is great if have tiny change to make given compiler output simply just to how fast it loads
- kstrauser 5y ago
  I got a local login on a machine so busted that I couldn't mount /usr, meaning I couldn't read /usr/share/terminfo, meaning no screen editors would work. I knew just enough ed that I was able to fix /etc/fstab and bring the system up. I wouldn't wanna use it every day, but it has its time and place.
  - donio 5y ago
    "busybox vi" is another option in these situations when that's available. It will happily run in a blank chroot. Everybody should know a little ed though, it's not that hard.
    - kstrauser 5y ago
      It was on a server that didn't have busybox installed. Also, can busybox vi work without access to termcap or terminfo?
  - yjftsjthsd-h 5y ago
    Honestly at that point, unless your fstab is really big, I'd just `cat /etc/fstab` and then `cat >/etc/fstab <<EOF` and very carefully retype it (I mean take a backup first of course).
    - kstrauser 5y ago
      sed is also a friend in these situations.
- cicero 5y ago
  I used to use ed when all I had was a single terminal screen/window and a compiler error message. Ed doesn't clear the screen, so you can still see the message. Vi or emacs would clear the error message away. Of course, in a multi-window situation, the compiler output is usually in one window or pane and the editor in another, so this is moot now.
xfer 5y ago
This is what i used to edit configurations in plan9 console if you don't have graphics support(over serial console) or to fix issues before starting rio. It is surprisingly pretty decent experience.

3 ms·

Yeah, how could you hate on anyone who uses the standard text editor?[0] [0] https://www.gnu.org/fun/jokes/ed-msg.html https://www.gnu.org/fun/jokes/ed-msg.htm

by blueblob 5y ago

Yeah, how could you hate on anyone who uses the standard text editor?[0] [0] https://www.gnu.org/fun/jokes/ed-msg.html https://www.gnu.org/fun/jokes/ed-msg.html

bear8642 5y ago
you joke, but ed is great if have tiny change to make given compiler output simply just to how fast it loads
- kstrauser 5y ago
  I got a local login on a machine so busted that I couldn't mount /usr, meaning I couldn't read /usr/share/terminfo, meaning no screen editors would work. I knew just enough ed that I was able to fix /etc/fstab and bring the system up. I wouldn't wanna use it every day, but it has its time and place.
  - donio 5y ago
    "busybox vi" is another option in these situations when that's available. It will happily run in a blank chroot. Everybody should know a little ed though, it's not that hard.
    - kstrauser 5y ago
      It was on a server that didn't have busybox installed. Also, can busybox vi work without access to termcap or terminfo?
  - yjftsjthsd-h 5y ago
    Honestly at that point, unless your fstab is really big, I'd just `cat /etc/fstab` and then `cat >/etc/fstab <<EOF` and very carefully retype it (I mean take a backup first of course).
    - kstrauser 5y ago
      sed is also a friend in these situations.
- cicero 5y ago
  I used to use ed when all I had was a single terminal screen/window and a compiler error message. Ed doesn't clear the screen, so you can still see the message. Vi or emacs would clear the error message away. Of course, in a multi-window situation, the compiler output is usually in one window or pane and the editor in another, so this is moot now.
xfer 5y ago
This is what i used to edit configurations in plan9 console if you don't have graphics support(over serial console) or to fix issues before starting rio. It is surprisingly pretty decent experience.