Re: Possible vim bug

Greetings, Eric Connor! > I'm not at liberty to share my path, due to the sensitivity of my position, > but it *does *include /usr/bin, and it's the second entry in the value. If I were you, I'd remove /usr/bin from $PATH. $ echo "$PATH" | sed -Ee 's/\:/\n/g;' $HOME/bin /usr/local/sbin /usr/sbin

Re: Possible vim bug

On 2020-12-08 12:04, Eric Connor via Cygwin wrote: *$uname -srvmo* CYGWIN_NT-10.0 3.0.5(0.338/5/3) 2019-03-31 11:17 x86_64 Cygwin *$which column* /usr/bin/column *$cygcheck -f /usr/bin/column* util-linux-2.33.1-2 *$cygcheck -c util-linux* Cygwin Package Information Package Version

Re: Possible vim bug

Thanks all, > *$uname -srvmo* > > CYGWIN_NT-10.0 3.0.5(0.338/5/3) 2019-03-31 11:17 x86_64 Cygwin > > *$which column* > > /usr/bin/column > > *$cygcheck -f /usr/bin/column* > > util-linux-2.33.1-2 > > *$cygcheck -c util-linux* > > Cygwin Package Information > > Package Version

[no subject]

Hi Get Outlook for iOS -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: Possible vim bug

On 2020-12-07 11:06, Eric Connor via Cygwin wrote: I have been experiencing an issue where I’m trying to format columns in vim using: :*%!column –t*, which had been working great. At some point I had to update Cygwin, and (not correlating it to a possible update issue, until recently) found that