Bug 1793475 - Improve yaml syntax highlight to handle colons in literal and folded blocks
Summary: Improve yaml syntax highlight to handle colons in literal and folded blocks
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: vim
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Leigh Griffin
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-21 12:37 UTC by Petr Šplíchal
Modified: 2020-06-16 12:03 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-06-16 12:03:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Šplíchal 2020-01-21 12:37:24 UTC
Description of problem:

Vim syntax highlight currently handles colons as special
characters inside literal and folded blocks and shows them as new
key value definition. The ':' inside a literal or a folded block
should be treated as a regular character.

Version-Release number of selected component (if applicable):
vim-common-8.2.109-1.fc31.x86_64

Steps to Reproduce:
$ cat example.yaml
description: |
    Multiline blocks using the literal (|) or folded (>) style can
    contain colons: Text before them should not be highlighted.

Actual results:
String 'contain colons' highlighted.

Expected results:
String 'contain colons' in regular color.

Additional info:
https://yaml-multiline.info/

Comment 1 Zdenek Dohnal 2020-01-21 15:19:33 UTC
Hi Petr,

I was able to reproduce the issue on my Fedora 30 (8.2.019).

The yaml.vim maintainer is Nikolai Pavlov, I'll send him email about the issue.

Comment 3 Ben Cotton 2020-02-11 17:21:52 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 4 Petr Šplíchal 2020-02-27 16:22:55 UTC
Has there been any update from Nikolai?

Comment 5 Zdenek Dohnal 2020-02-28 05:34:50 UTC
Unfortunately I haven't got any update from Nikolai yet - I'll file the issue on upstream.

Comment 6 Petr Šplíchal 2020-06-16 11:37:20 UTC
Has there been any update from upstream?

Comment 7 Zdenek Dohnal 2020-06-16 12:03:34 UTC
Hi Petr,

I'm sorry I didn't file the issue on upstream at the time - but here it is now https://groups.google.com/forum/#!topic/vim_dev/lmRynxHb95w .

I would say it is not a critical issue, so I'm closing the issue as UPSTREAM.


Note You need to log in before you can comment on or make changes to this bug.