public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Connor <eacmacro@gmail.com>
To: cygwin@cygwin.com
Subject: Possible vim bug
Date: Mon, 7 Dec 2020 13:06:15 -0500	[thread overview]
Message-ID: <CADZZWXp-KUVXbkCE3bk2pusyAVS+yTbuPYs6k9+kt4aFZkWTow@mail.gmail.com> (raw)

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

             reply	other threads:[~2020-12-07 18:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07 18:06 Eric Connor [this message]
2020-12-07 21:57 ` Gary Johnson
2020-12-08  3:25 ` Kevin Schnitzius
2020-12-08 13:07 ` Brian Inglis
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=CADZZWXp-KUVXbkCE3bk2pusyAVS+yTbuPYs6k9+kt4aFZkWTow@mail.gmail.com \
    --to=eacmacro@gmail.com \
    --cc=cygwin@cygwin.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).