From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.12]) by sourceware.org (Postfix) with ESMTPS id 4AA2C3861026 for ; Tue, 8 Dec 2020 13:07:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 4AA2C3861026 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=brian.inglis@systematicsw.ab.ca Received: from [192.168.1.104] ([24.64.172.44]) by shaw.ca with ESMTP id mciakAW4RtdldmcibkvvBm; Tue, 08 Dec 2020 06:07:50 -0700 X-Authority-Analysis: v=2.4 cv=INe8tijG c=1 sm=1 tr=0 ts=5fcf7aa6 a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17 a=IkcTkHD0fZMA:10 a=uYT-Tk0qkVT609LjNaIA:9 a=QEXdDO2ut3YA:10 Reply-To: cygwin@cygwin.com To: cygwin@cygwin.com References: From: Brian Inglis Organization: Systematic Software Cc: Eric Connor Subject: Re: Possible vim bug Message-ID: <5f939f35-fdd5-740d-d9b4-06ffdf0ac26a@SystematicSw.ab.ca> Date: Tue, 8 Dec 2020 06:07:48 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-CA Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4xfCaX/9nbqy25AMqlsf0Mb0GxrosW8HQJaQFnMl8E11c+knD4dxTUyWlAyHfGZptpqnoYJeOHrA6bpwOMAYPe7GZ6Fyk89ZBWvgIfhCv7W2OcjrooxI2E Xs0une9GtzRQxA55T9tF5fAFHb4haDdLvWlG9ngWVk9UQvz6inL7bh1dO793tcdT2rfHjBu1BFeFpnhaZGZRAAEKMUBrCVNJQErGxeOSoEBMURmCdrKYue7i X-Spam-Status: No, score=-6.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Dec 2020 13:07:52 -0000 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 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. Probably little to do with vim, mostly to do with either Cygwin Setup or PATH, so check the below and your PATH, your PATH within vim, and your Cygwin Setup logs: $ uname -srvmo CYGWIN_NT-10.0 3.1.7(0.340/5/3) 2020-08-22 17:48 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 Status util-linux 2.33.1-2 OK $ which vim /usr/bin/vim $ cygcheck -c vim Cygwin Package Information Package Version Status vim 8.2.0486-1 OK $ echo $PATH $ vim +'echo $PATH' $ vim +'!which column' /usr/bin/column Press ENTER or type command to continue $ l /var/log/setup.log* /var/log/setup.log /var/log/setup.log.full and it may be worthwhile rerunning Cygwin Setup to install any patched or upgraded packages and clean up any issues. If you see anything you don't understand, please post the above commands and output, plus any other commands and questionable output, and follow the problem reporting guidelines below (copy and trim large files if possible, and attach as text). -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.]