[kate] [Bug 416338] LSP configuration for Go (golang)

2020-11-13 Thread Wouter Van Hemel
https://bugs.kde.org/show_bug.cgi?id=416338

Wouter Van Hemel  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---
Version|19.12.1 |20.08.3

--- Comment #4 from Wouter Van Hemel  ---
This report is still valid as of 2020-11-13 with Kate 20.08.3.

As mentioned in its repo, the Sourcegraph LSP server is deprecated and should
be switched to the official Go LSP server.

It is true however that the official Go LSP server is taking quite some time to
reach a stable version.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 406109] New: Run on save (auto-format hook)

2019-04-01 Thread Wouter Van Hemel
https://bugs.kde.org/show_bug.cgi?id=406109

Bug ID: 406109
   Summary: Run on save (auto-format hook)
   Product: kate
   Version: 18.12.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: wouter-...@publica.duodecim.org
  Target Milestone: ---

It would be nice to be able to run an auto-formatter on save for several
languages. I don't think there's a way to execute something as a hook when
saving a file. This hook should probably be a property of the "file type" and
Kate should avoid "file has changed on disk" warnings but re-read the file
automatically if such a hook has been set.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 416338] New: LSP configuration for Go (golang)

2020-01-16 Thread Wouter Van Hemel
https://bugs.kde.org/show_bug.cgi?id=416338

Bug ID: 416338
   Summary: LSP configuration for Go (golang)
   Product: kate
   Version: 19.12.1
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: wouter-...@publica.duodecim.org
  Target Milestone: ---

Created attachment 125171
  --> https://bugs.kde.org/attachment.cgi?id=125171&action=edit
LSP configuration file with modified Go settings

The LSP (Sourcegraph) client Kate currently uses for Go is deprecated; Go has
an official client in its tools repository that's used by most editors now.

See also the README for the Sourcegraph server:
https://github.com/sourcegraph/go-langserver

Link to the official LSP server, named gopls:
https://github.com/golang/tools/tree/master/gopls

I've changed the server for Go in the settings.json file. I also had to enable
some workspace root configuration for the LSP server to work correctly.

Here are the settings I've got now:

"go": {
"command": ["/home/wouter/.local/gobin/gopls"],
"commandDebug": ["/home/wouter/.local/gobin/gopls", "-debug"],
"rootIndicationFileNames": ["go.mod", "go.sum"],
"url": "https://github.com/golang/tools/tree/master/gopls";,
"highlightingModeRegex": "^Go$"
},


I will try to attach my modified settings file to this report in case that
would turn out to be helpful.

Thanks for working on LSP support!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 416338] LSP configuration for Go (golang)

2020-01-21 Thread Wouter Van Hemel
https://bugs.kde.org/show_bug.cgi?id=416338

--- Comment #2 from Wouter Van Hemel  ---
Gopls is the one used in govim and VSCode though; but they have some
auto-update mechanism for updating gopls versions.

You've got a point about distributions having to catch up. I like to keep my
own tools up to date, but I guess a lot of people would be disappointed if it
were not to work out of the box.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 416530] New: Terminal mouse movement tracking for hover

2020-01-21 Thread Wouter Van Hemel
https://bugs.kde.org/show_bug.cgi?id=416530

Bug ID: 416530
   Summary: Terminal mouse movement tracking for hover
   Product: konsole
   Version: 19.12.1
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: emulation
  Assignee: konsole-de...@kde.org
  Reporter: wouter-...@publica.duodecim.org
  Target Milestone: ---

Recent versions of Vim have text balloons that can show information on
mouse-over. These balloons should work in non-graphical terminals, too, using
the following settings:

set mouse=a
set ttymouse=sgr

set updatetime=1500
set balloondelay=300
set ballooneval
set balloonevalterm

However, this functionality doesn't seem to be working in Konsolepart-based
terminal emulators like Konsole and Yakuake.

STEPS TO REPRODUCE
1. Enable govim or any other vim extension that uses balloon pop-ups;
2. Open some source code;
3. Hover a keyword.

OBSERVED RESULT
On mouse-over, nothing happens in konsole or yakuake; no balloon appears.
Keyboard shortcuts do show the text balloon with information, so the problem is
with vim not noticing the mouse pointer is located over a keyword. Mouse
movements do not seem to be detected; basic mouse functionality such as clicks
and selection work fine, though.

EXPECTED RESULT
I expect that when moving the mouse pointer over a keyword, vim triggers a text
balloon to be shown. This functionality works by default in other terminals,
e.g. Alacritty.

My guess is that the terminal emulation code doesn't report mouse movements to
vim, either because it's not supported or because the terminfo entry isn't
complete. Alternatively, I could have somehow managed to mess up the settings
so Konsole would have disabled some terminal functionality.

ADDITIONAL INFORMATION

In short: no vim text balloons on mouse-over in Konsole while they show up in
other terminal applications.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 389683] New: Document preview plugin hijacks keyboard shortcuts

2018-01-31 Thread Wouter Van Hemel
https://bugs.kde.org/show_bug.cgi?id=389683

Bug ID: 389683
   Summary: Document preview plugin hijacks keyboard shortcuts
   Product: kate
   Version: 17.12.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plugin-preview
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: wouter-...@publica.duodecim.org
CC: kosse...@kde.org
  Target Milestone: ---

Hello,

I'm trying to use the new document preview to check Markdown output. The plugin
hijacks a lot of keybindings – such as ctrl-s – so Kate returns an error about
duplicate keyboard bindings ("ambiguous shortcut detected") when the preview
window is open.

I understand the problem is caused by some sort of Okular part running inside
Kate adding its own keybindings, but I'm not sure if it is possible to disable
the keybindings this kpart adds or even better to check the focus of the mouse
and only apply the embedded part's bindings if it has active focus.

I like the functionality of this plugin though, it's very helpful when writing
documentation alongside code.

(Kate 17.12.1 on Arch Linux)

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-ktexteditor] [Bug 398758] New: Syntax highlighting doesn't use chosen theme (default style broken)

2018-09-17 Thread Wouter Van Hemel
https://bugs.kde.org/show_bug.cgi?id=398758

Bug ID: 398758
   Summary: Syntax highlighting doesn't use chosen theme (default
style broken)
   Product: frameworks-ktexteditor
   Version: 5.50.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: wouter-...@publica.duodecim.org
  Target Milestone: ---

Hello,

Since the last update of Frameworks to 5.50.0, Kate and Kwrite ignore most of
the chosen theme's highlighting colours.

I use the Solarized (dark) theme as default and since the update, apart for the
background, most colours seem to come from somewhere else.

It seems the default colours are never set to the selected "Default scheme for
kate".

I can go to the "Highlighting Text Styles" tab and click the "Use Default
Style" checkbox for each type and each language, but that's silly.

Is this a known problem?

-- 
You are receiving this mail because:
You are watching all bug changes.