DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 754BE3896C2A
MIME-Version: 1.0
Date: Mon, 7 Dec 2020 13:06:15 -0500
Message-ID: <CADZZWXp-KUVXbkCE3bk2pusyAVS+yTbuPYs6k9+kt4aFZkWTow@mail.gmail.com>
Subject: Possible vim bug
To: cygwin AT cygwin DOT com
From: Eric Connor via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Eric Connor <eacmacro AT gmail DOT com>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>
Content-Transfer-Encoding: 8bit

Hello,


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 this command has been returning
“shell returned 127” error.


Today, I tested whether this command would work on a server (with a version
of mlos), and found that it worked.


The version of vim on my server is considerably older than my Cygwin
version:


Server: 7.4

Local: 8.2


Is there a way to either back-rev vim further (if an old install repo
existed, that would be ideal), or someone review what was updated to make
vim not happy with the column command?


I also compared both versions of the column command, and they were the same
on both my server *and* my local workstion...thus my conclusion that this
seems to be a vim-related matter.


I was successful in back-reving to 8.1, simply because I had the previous
setup file for Cygwin, but older versions are a bit more difficult to
locate...and I'm doubtful that going back much further wouldn't cause
damage to my current setup.


Thank you,


Eric Connor
--
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