From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.spocom.com (mail.spocom.com [206.63.224.240]) by sourceware.org (Postfix) with ESMTP id 315253896828 for ; Mon, 7 Dec 2020 21:58:59 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 315253896828 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=spocom.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=garyjohn@spocom.com DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; d=spocom.com; s=mail; h=received:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-type:content-disposition :content-transfer-encoding:in-reply-to:x-operating-system :user-agent; b=jBurHeEPEL4Cg/6c/bxetwYfFcmh4VOVoOfJ8lQYBYM5wmVXwzjtBSOx6EjGC6iWu lLhcYja/aLOMfu0Udm9BA== Received: from localhost (174-31-100-164.spkn.qwest.net [174.31.100.164]) by mail.spocom.com with SMTP; Mon, 7 Dec 2020 13:58:38 -0800 Date: Mon, 7 Dec 2020 13:57:53 -0800 From: Gary Johnson To: cygwin@cygwin.com Subject: Re: Possible vim bug Message-ID: <20201207215753.GB3161@phoenix> Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: Linux 2.6.32-74-generic GNU/Linux User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham 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: Mon, 07 Dec 2020 21:59:01 -0000 On 2020-12-07, Eric Connor via Cygwin wrote: > 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. I just tried this on a fresh install of Cygwin on Windows 10 and it worked fine. $ vim -N -u NONE :r!ls -l 13 more lines :%!column -t 14 lines filtered :echo v:shell_error 0 I assumed that the asterisks in your example command were some sort of formatting artifact. In the shell I ran "cygcheck -cd" and found the following versions: cygwin 3.1.7-1 vim 8.2.0486-1 vim-common 8.2.0486-1 vim-doc 8.2.0486-1 vim-minimal 8.2.0486-1 util-linux 2.33.1-2 bash 4.4.12-3 Util-linux is the package containing column. So I don't see a bug at all. Regards, Gary