public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Gary Johnson <garyjohn@spocom.com>
To: cygwin@cygwin.com
Subject: Re: cygwin update, gvim 8.2. file type plugin, perl script error
Date: Tue, 19 Jul 2022 15:02:00 -0700	[thread overview]
Message-ID: <20220719220200.GG12539@phoenix> (raw)
In-Reply-To: <ad97a21591b04f289f154fdab2b5472f@analog.com>

On 2022-07-19, Kutty, Rejeesh wrote:
> Hi,
> 
> I recently ran the installer and it updated vim to 8.2
> 
> :version
> VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Feb 13 2022 22:00:24)
> Included patches: 1-4372
> 
> 
> Now when I open a perl script, I get the following message:
> 
> Command terminated
> Error detected while processing BufRead Autocommands for "*.pl"..function dist#ft#FTpl[10]..FileType
> Autocommands for "*"..function <SNR>11_LoadFTPlugin[18]..script /usr/share/vim/vim82/ftplugin/perl.
> vim[57]..BufRead Autocommands for "*.pl"..function dist#ft#FTpl[10]..FileType Autocommands for "*"..
> function <SNR>11_LoadFTPlugin[18]..script /usr/share/vim/vim82/ftplugin/perl.vim:
> line   50:
> E484: Can't open file /tmp/vveXImd/0
> Press ENTER or type command to continue
> 
> 
> And all syntax is lost.
> 
> This only happens with perl-scripts.
> 
> I opened Verilog/SystemVerilog/Shell/CPP/C/TCL files, and all these opened without problems.
> 
> Not sure if I should ask this in the vim/github help, thought I will start here.

I tried the following:

    $ /usr/bin/vim -N -u NONE -i NONE -c 'syntax on' -c 'e /usr/share/perl5/5.32/perl5db.pl'

where the perl file is one I thought you might have on your system
and vim is the current Cygwin package version, 8.2.4372.  I don't
get any error messages.

If that works for you, then there seems to be something in your Vim
configuration, e.g., your vimrc, that's causing the problem, but
I haven't given a whole lot of thought to what that might be.

As for where to ask about the problem, this is probably the right
place to start and where the best group of folks is to figure out
whether it's a Cygwin problem, a Vim problem, or a configuration
problem.

Regards,
Gary


      reply	other threads:[~2022-07-19 22:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 19:13 Kutty, Rejeesh
2022-07-19 22:02 ` Gary Johnson [this message]

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=20220719220200.GG12539@phoenix \
    --to=garyjohn@spocom.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).