From: "jonathan.kinred at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug documentation/25186] New: Vim ftplugin creates conflicting autocmd group
Date: Mon, 11 Nov 2019 08:05:00 -0000 [thread overview]
Message-ID: <bug-25186-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=25186
Bug ID: 25186
Summary: Vim ftplugin creates conflicting autocmd group
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: documentation
Assignee: systemtap at sourceware dot org
Reporter: jonathan.kinred at gmail dot com
Target Milestone: ---
There's a long standing bug in the provided Vim plugin which breaks the
expected case insensitive behaviour of Vim's autocmd event's.
There is a Stack Exchange description of the problem here:
https://vi.stackexchange.com/questions/5546/why-doesnt-vim-work-with-lowercase-event-names/5731#5731
By using the autocmd group name "filetype", which has the same name as an
autocmd "event", subsequent use of case insensitive events will try to allocate
the command to the group created in the systemtap Vim plugin.
I discovered this when installing the "Development Libraries" group on Fedora
31 which includes the systemtap-devel package. After this, other unrelated Vim
plugins broke.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-11-11 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 8:05 jonathan.kinred at gmail dot com [this message]
2019-11-24 22:38 ` [Bug documentation/25186] " fche at redhat dot com
2019-11-25 2:34 ` jonathan.kinred at gmail dot com
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=bug-25186-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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).