LSP plugin: Use language id instead of highlighting mode for server identification
ClosedPublic

Authored by cullmann on Aug 7 2019, 7:45 PM.

Details

Summary

Use the standardized language id in more places.

Why?

  • the LSP names are "standardized"
  • we can internally map different C++/... highlightings to the same canonical LSP lanuage id name

Diff Detail

Repository
R40 Kate
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
cullmann created this revision.Aug 7 2019, 7:45 PM
Restricted Application added a project: Kate. · View Herald TranscriptAug 7 2019, 7:45 PM
Restricted Application added a subscriber: kwrite-devel. · View Herald Transcript
cullmann requested review of this revision.Aug 7 2019, 7:45 PM

;=) I guess I missed to add any argument why we should do this

  1. the LSP names are "standardized"
  2. we can internally map different C++/... highlightings to the same canonical LSP lanuage id name
dhaumann accepted this revision.Aug 7 2019, 8:18 PM
dhaumann edited the summary of this revision. (Show Details)
dhaumann retitled this revision from use language id instead of highlighting mode for server identification to LSP plugin: Use language id instead of highlighting mode for server identification.
dhaumann added a subscriber: dhaumann.

That makes a lot of sense and is likely more robust for now.

This revision is now accepted and ready to land.Aug 7 2019, 8:20 PM

Let's wait what Mark says, it's anyways sleep time .P

mnauwelaerts accepted this revision.Aug 7 2019, 9:53 PM
This revision was automatically updated to reflect the committed changes.