From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: Eric Connor <eacmacro@gmail.com>
Subject: Re: Possible vim bug
Date: Tue, 8 Dec 2020 06:07:48 -0700 [thread overview]
Message-ID: <5f939f35-fdd5-740d-d9b4-06ffdf0ac26a@SystematicSw.ab.ca> (raw)
In-Reply-To: <CADZZWXp-KUVXbkCE3bk2pusyAVS+yTbuPYs6k9+kt4aFZkWTow@mail.gmail.com>
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.]
next prev parent reply other threads:[~2020-12-08 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 18:06 Eric Connor
2020-12-07 21:57 ` Gary Johnson
2020-12-08 3:25 ` Kevin Schnitzius
2020-12-08 13:07 ` Brian Inglis [this message]
2020-12-08 19:04 ` Eric Connor
2020-12-08 19:37 ` Brian Inglis
2020-12-08 20:41 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5f939f35-fdd5-740d-d9b4-06ffdf0ac26a@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
--cc=eacmacro@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).