 | | Re: Any cygwin32 users out there? —Susan Hoover
| | | | (...) Erm, did you ever get a "yes" from anyone? We're using cygwin32 here at work, but beyond setting it up once and then running stuff in it every day, I don't know much about configuring it. Do you remember what questions you had, 10 months ago? (...) (25 years ago, 5-May-00, to lugnet.off-topic.geek)
| | | | | | | | | | Re: Any cygwin32 users out there? —Jeremy H. Sproat
| | | | | (...) Actually, you have the honor of being the first to reply! :-, (...) Yeah. And they still stand. :-, Mainly, I was trying to figure out how to get Bash to recognize my .inputrc; specifically, how to get Bash to set editing-mode to vi. IOW, I (...) (25 years ago, 5-May-00, to lugnet.off-topic.geek)
| | | | | | | | | | | | Re: Any cygwin32 users out there? —Susan Hoover
| | | | | (...) Wow, you're right. I just tried all combinations of locations of .inputrc [c:\, c:\bash, c:\users\default] with all combinations of stuff in .inputrc ["set editing-mode vi"[1], "set vi-editing-mode"[2], "set vi-editing-mode on", "set (...) (25 years ago, 5-May-00, to lugnet.off-topic.geek)
| | | | | | | | | | | | Re: Any cygwin32 users out there? —Jeremy H. Sproat
| | | | | (...) D'oh! 'Scuse me while I yank out more of my hair... :-, It's pretty much in the past now; I've given up on Cygwin. I discovered that MKS Toolkit offers a *lot* of POSIX command-line functionality that we needed on our project, and I never (...) (25 years ago, 5-May-00, to lugnet.off-topic.geek)
| | | | | | |
