I just found that the same problem exists for import_keywords too - when I type import qual, the completion doesn't show up, and deleteting qual and typing it again causes it to show.

So, it seems to be a coding bug.

@arrowdodger Isn't there a line missing:

+ <context attribute="Pragma" lineEndContext="#pop" name="pragma">
+ <keyword attribute="Pragma" context="#stay" String="language_pragmas" />
+ <StringDetect attribute="Pragma" context="#pop" String="#-}"/> <------------------ This line ?
+ </context>

Also, is the lineEndContext #pop or should it rather be #stay?

Please clarify/confirm.

Also: could you provide us with a small demo code so that we can extend our unit test?

In D6087#117019, @dhaumann wrote:

Also: could you provide us with a small demo code so that we can extend our unit test?

The demo for added highlighting rule, or the problem with autocompletion?

Demo for the highlighting rule - I don't think I can say anything to the auto completion issue. I am pretty sure it is unrelated to your xml file.

In D6087#118963, @dhaumann wrote:

Demo for the highlighting rule - I don't think I can say anything to the auto completion issue. I am pretty sure it is unrelated to your xml file.

Sure. Pragmas have following form:

{-# blabla #-}

Specifically, pragmas that enable language extensions looks like

{-# LANGUAGE OverlappingInstances, BangPatterns #-}

As I've found today, pragmas can span onto multiple lines:

{-# LANGUAGE OverlappingInstances, 
             BangPatterns
#-}

So, can I push this?

I would say yes.
If you have some more time, you could add an auto-test for it.

Hmm, interesting, I would assume you need to update the ref given the input did change.