You're viewing a comment by libdave and its responses.
You're viewing a comment by libdave and its responses.
I am being sponsored by Syntress! They bought me an amazing dedicated server to run catonmat on. If you're looking web services, I highly recommend the Syntress guys!
I am being sponsored by A-Writer! If you ever need help with essay writing, look no further than A-Writer! They will help you with your writing in as quickly as 3 hours!
I love to read science books. They make my day and I get ideas for awesome blog posts, such as Busy Beaver, On Functors, Recursive Regular Expressions and many others.
Take a look at my
Amazon wish list, if you're curious about what I have planned reading next, and want to surprise me. :)
If you are interested in advertising on catonmat.net, contact me.
Free tools for coding on Vietstarsoft.com.
Programming homework help.


One of my favorites: to edit any env variable
print -s "PATH=$PATH"
then edit the last command (zsh with vi keybindings): ESC-
Comment Responses
Almost forgot the follow up function to make it easier:
foo()
{
eval "print -s ${1?no variable}=\'\$$1\'"
}
then do this:
X='xyzzy plugh'
foo X
then edit your history
Hmm.. Can you explain this a bit more? I don't understand it.
What he's doing is first he sets PATH to itself (eval PATH=$PATH), which leaves him with something like
PATH=/usr/local/bin:/usr/bin:/usr/sbin:/bin:/sbin
in his history. Then he just uses the editor to modify this and run it again, thus setting PATH to the modified value.
Reply To This Comment