Have you heard about this new "heartbleed" bug? It affects GNU/OpenBSD, and some other systems too.
You are welcome. Scared the heck out of me with the first try and it dumped out the admin password. Kinda makes me ill knowing it has been hanging out there for a years on the newer installs. Read today about some folks that have proof of full private key certs. Replacing them is yet another priority.
Today, I learned the difference between sed and ed.
Use ed for in-place edit of files.
Use sed for streaming edits across pipes.
It's entertaining to use ed for scripting edits of files.
(e.g. echo ',s/foo/bar/g;w;q' | tr \; '\012' | ed -e $file )
Next you can learn "ex", which is basically vi without the fullscreen. Sounds silly, but if you need to pipeline a bunch of commands you already know them.
sed and awk together are powerful shell scripting tools. Perl is for weenies.
I'm fortunate that I have been using vi(m) for a long time now, so a lot of those commands are actually fairly well ingrained in me. That, I've noticed, has helped me get through some of the complicated commands pretty well. They are relatively intuitive to me.
This said, I still have to look up a lot of stuff. I was originally trying to do all of this with sed instead of ed, but found that ed did the job I wanted far better.
I'd probably feel similarly about emacs. I used to love emacs, though, but vi really grew on me.
I still prefer nano. I can use (and most important: exit!) vi, but I never ever cared to learn any of its alledgedly beneficial features. I'd rather describe it as "I can defend myself against *nixes which lack nano and fore me to use vi". Heck, I even do not know how to do a search in it (probably involves the /). I like how vi highlites brackets, and some things about rows it does better than nano. It is also smarter when it comes to charset conversion.
I did all my work on this current layout of citadel and all my hacking and slashing in the source in nano. In fact, I edit most html in nano, there is syntax highlighting and it is enough most of the time. Still, I am willing to give Aptana Studio a try for the next layout rework.
I use nano also but only because my old boss used it and it was default. When I ssh to godaddy I have to use
Yes, I know about pico, but it is the systems you ssh into, that force you to use vi. QNAP NAS devices (maybe I forgot to check for pico there), such things. OSX features both, vi and nano. I like that.
Yeah, searches in vi involve using '/'. You can search backwards with '?' if I recall. And global search-and-replace involves using a colon command, like:
(% means, 'the entire document', s means 'search for text', 'search' is the term to find, 'replace' is term to change to 'search', and 'g' means 'look for other search terms to the end of the line').
Heh, did I get that right?
emacs can edit files via ssh.
today i've learned about http://www.lighttable.com/
(ok, its implemented in clojure, which basicaly is a lisp interpreter running in the java interpreter...)
I seem to remember someone perverse created a vi editor in emacs.
Lighttable web page insults the venerable 80-character TTY! How dare they!
(Actually I run all my terminals at 132x43 now. I wanted something bigger but I didn't just want to be ambiguous about it so I chose something that's at least a VESA mode. But I'm a nerd.)
It amuses me that someone implemented what appears to be telnet or ssh via web page, then made that available in Turnkey Linux through their Webmin interface.
Which might (maybe?) be an interesting idea for a distributable virtual machine for Citadel. Hmm...
"Weaponized Comic Sans": http://www.openbsd.org/papers/bsdcan14-libressl/mgp00025.html
part of a larger presentation on OpenBSD's vote-of-no-confidence in OpenSSL (a few years too late, but appreciated nonetheless)
skip to the good bits: