News for hackers. Stuff that matters.
Re:The Command-Line Office by 616c on Wednesday March 05, 2014 @01:27AM (#7345671)
I eventually want to make a GUI equivalent as I learn to program, and had some other ideas that you have inspired as I try to get back to programming.

THANK YOU! I love your tool and it is one of my favorite tools. I check your git for other cool stuff as I stumbled upon your stuff many times.

Question: would you want to add a parameter to escape non-aplhanumeric characters? It took me a while of playing to figure out how to get mutt to handle my very complex IMAP passwords.

For anyone who cares, I do it with sed.

set my_pass=`pass email/[email protected] | sed 's/[[:punct:]]/\\&/g'`

#

Re:The Command-Line Office by ygra on Wednesday March 05, 2014 @06:18AM (#7346366)
Random question (I have no clue of mutt or Unix shells (the code there looks like one)): But isn't that a problem of the receiving application? You can't really ask every single application that outputs text to sprout arguments to support every possible escaping that might be needed eventually. And whatever comes out of the `foo` part shouldn't be interpreted or parsed anyway, right?
Re:The Command-Line Office by aidenn0 on Thursday March 06, 2014 @02:54PM (#7356149)
how about

    set my_pass="`pass email/[email protected]`"
[edit] Looks like this is a muttrc line not a sh line. Sadly I don't think muttrc supports the far superior $() expansion..
Re:The Command-Line Office by 616c on Wednesday March 12, 2014 @06:35AM (#7384867)
I tried this and it does not work. And yes, mutt does not support $() escaping.