The premier conference for ed(1), the standard text editor. A bit snarky. Accessible at 300 baud. Masto: @ed1conf@bsd.network https://xitter.cf/t.co/9xThaFaYMH
Online
Joined January 2015
- Tweets5.8K
- Following13
- Followers2.1K
- Likes9.2K
ed(1) Conference retweeted
The first Unix editor "ed" by Ken Thompson was so primitive that it worked on line basis (not by moving the cursor like in modern editors). Most current day users couldn't use ed at all, even if given the full manual. I also remember struggling with this and went the Emacs way.
ed(1) Conference retweeted
If you use org-mode in VSCode, you should be using Emacs
If you use Doom or evil-mode in Emacs, you should be using Vim
If you use Command mode in Vim you should be using ed(1)
If you use ,p command in ed, you should be using a teletype
If you use a tty, umm,... you win?
ed(1) Conference retweeted
As an intern taking care of a UNIX machine, I had a hard time getting used to 'vi', but at least it was full screen. One day a support guy came to do some work and fired up the line oriented 'ed' editor on a huge config file. Probably the fastest text editing I've ever seen. 😳 – at Copenhagen, Denmark
ed(1) Conference retweeted
😂😂😂
But seriously... I didn't know how to edit files on UNIX. No internet so I had to check the many manuals on the shelf with everything from UNIX commands to MIPS assembler. I couldn't believe that I had to use ed but then I found vi. Never learned it properly though. – at Copenhagen, Denmark
ed(1) Conference retweeted
> Can you ed ed
Sure:
$ cd /usr/src/bin/ed/
$ ed main.c
> from ed?
Sure:
$ cd
$ ed
!ed /usr/src/bin/ed/main.c
31831
> and so forth?
Sure:
$ ed so.4th
20
p
.( Hello World!) CR
Green flags in a Man's text-editor
1. minimalist
2. supports regular expressions
3. outsources tasks to external specialized tools
4. doesn't consume gobs of RAM
5. doesn't require a GUI
6. runs on a hard-copy output device
7. unintrusive error messages
8. is the standard
The ed(1) ecosystem is unreal.
- You can write Python in ed(1)
- You can write Java in ed(1)
- You can write Shell scripts in ed(1)
- You can build Dockerfiles in ed(1)
- You can write Terraform in ed(1)
- You can manage Git from ed(1)
- You can edit YAML files in ed(1)
ed(1) Conference retweeted
i'm very thankful that there was an entire conference on ed. it even has an x account: @ed1conf. it was a shame that is happened in 2019. i only knew scratch back then.
ed(1) Conference retweeted
Reiz FreeBSD serverim Londonas datucentrā nobruka cietais disks. Atbrauca servisa meistars, nomainīt disku, bet bez /etc/fstab ieraksta nomaiņas, serveris nebūtu piešķīlies “multi user mode”. Pieejams tikai “ed”. Dabūju pa telefonu viņam diktēt “ed” komandas. O prieki! Izdevās.
ed(1) Conference retweeted
1/ I've written tons of code using `ed` , `ex` and `sed`. It's fantastic. It's all a matter of habit, platform and baud rate. Even though you'd expect someone like me to use 'vi' and 'vim', I prefer emacs if the platform and baud rate supports it.
ed(1) Conference retweeted
By the time I started using serial terminals I was already somewhat proficient in C, which is what I learned on a TTY in 1981.
I still used ed a lot, then a small version of emacs, before switching to vi. I've been using vim since 1992 when I started using Linux.
ALT One of the engagement photos of Taylor Swift and Travis Kelce, with Taylor labeled "ed(1)", her eyes closed leaning forehead-to-forehead with Travis who is labeled "stdin & stdout"
ed(1) Conference retweeted
Just use ed – the standard editor
Still the most efficient editor for teletype. @ed1conf
ed(1) Conference retweeted
Switch 100% to ed (the standard editor). Only read man pages. Throw away your phone.
ed(1) Conference retweeted
I was working on a switch that only had vi and no other text editor besides ed. The whole it department pushed the task on me because they did not know how to use anything other than nano. Even the networking guy. That's when I learned how useless government workers were.
