It seems that the hostname is considered as a tag name.
By checking the file runtime/syntax/messages.vim, I found it is easy to fix.
diff --git a/runtime/syntax/messages.vim b/runtime/syntax/messages.vim
index c22e4e8..59425fc 100644
--- a/runtime/syntax/messages.vim
+++ b/runtime/syntax/messages.vim
@@ -26,7 +26,7 @@ syn match messagesDateRFC3339 contained display '\d\{4}-\d\d-\d\d'
syn match messagesRFC3339T contained display '\cT'
\ nextgroup=messagesHourRFC3339
-syn match messagesHourRFC3339 contained display '\c\d\d:\d\d:\d\d\(\.\d\+\)\=\([+-]\d\d:\d\d\|Z\)'
+syn match messagesHourRFC3339 contained display '\c\d\d:\d\d:\d\d\(\.\d\+\)\=\([+-]\d\d:\d\d\|Z\)\s*'
\ nextgroup=messagesHost
syn match messagesHost contained display '\S*\s*'
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, .
please contact the syntax script maintainer and discuss the issue with him. Thanks.
It's been more than 4 years; I think the maintainer did not reply.
As suggested by the OP, this patch fixes the issue:
diff --git a/runtime/syntax/messages.vim b/runtime/syntax/messages.vim
index c22e4e8d0..59425fca5 100644
--- a/runtime/syntax/messages.vim +++ b/runtime/syntax/messages.vim @@ -26,7 +26,7 @@ syn match messagesDateRFC3339 contained display '\d\{4}-\d\d-\d\d' syn match messagesRFC3339T contained display '\cT' \ nextgroup=messagesHourRFC3339 -syn match messagesHourRFC3339 contained display '\c\d\d:\d\d:\d\d\(\.\d\+\)\=\([+-]\d\d:\d\d\|Z\)' +syn match messagesHourRFC3339 contained display '\c\d\d:\d\d:\d\d\(\.\d\+\)\=\([+-]\d\d:\d\d\|Z\)\s*' \ nextgroup=messagesHost syn match messagesHost contained display '\S*\s*'
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
I'll include that change.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Closed #946.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.