profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/rwols/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Raoul Wols rwols @CopernicaMarketingSoftware The Netherlands primef.actor

rwols/CMakeBuilder 25

Configure, build and test a CMake project right from within Sublime Text 3.

rwols/Clara 6

Semantic C++ code completion for Sublime Text 3

rwols/BetterSwitchHeaderImplementation 2

More exhaustive Switch File functionality for the C-family

rwols/SafeQueue 2

A naive implementation of a thread-safe queue for transporting data across threads

rwols/FutureConstrictor 1

Collection of classes to throttle/constrict the number of concurrent futures. Requires https://github.com/stlab/libraries.

rwols/gintonic 1

Yet another render engine

rwols/languageclient-clangd 1

Language Server Protocol support for Atom

rwols/MasterThesis 1

A McCord Functor for Alexandroff Categories

rwols/assimp 0

Official Open Asset Import Library Repository. Loads 40+ 3D file formats into one unified and clean data structure.

rwols/cereal 0

A C++11 library for serialization

issue commentsublimelsp/LSP

Unwanted splitting on dot of the setting keys

I think we can just check for the presence of a : or / character. Nobody uses those characters for their key (part), no?

rchl

comment created time in a day

issue commentsublimehq/sublime_text

Breaking a sublime-syntax which is extended causes incorrect scopes to be applied

Does clearing sublime.cache_path() work?

keith-hall

comment created time in 2 days

push eventsublimelsp/LSP

Rafał Chłodnicki

commit sha 62bb32a4c6e4de6f0fcfa5ae3d47c7634d4ff012

Support multiple patterns in file_watcher client configuration (#1859)

view details

Raoul Wols

commit sha 6743056454153a0a783eb1a77566528b2295ea97

Merge branch 'main' into fix/remove-filename-to-uri-calls

view details

push time in 2 days

delete branch sublimelsp/LSP

delete branch : fix/multiple-pattern-watcher

delete time in 2 days

push eventsublimelsp/LSP

Rafał Chłodnicki

commit sha 62bb32a4c6e4de6f0fcfa5ae3d47c7634d4ff012

Support multiple patterns in file_watcher client configuration (#1859)

view details

push time in 2 days

PR merged sublimelsp/LSP

Support multiple patterns in file_watcher client configuration

I've realized that supporting only one pattern doesn't allow to handle the use-case of eslint which needs three patterns that are not possible to handle with a single pattern and braces:

  • **/.eslintr{c.js,c.yaml,c.yml,c,c.json}
  • **/.eslintignore
  • **/package.json
+22 -19

0 comment

5 changed files

rchl

pr closed time in 2 days

PullRequestReviewEvent

issue commentsublimehq/sublime_text

Can't create a new plugin

It means you need to call view.run_command(“ snake_case_class_name”) when your text command class is named PascalCaseClassName.

Gabriel-p

comment created time in 3 days

issue commentsublimehq/sublime_text

Can't create a new plugin

The rule is that a PascalCaseClassName is translated to a snake_case_class_name when you want to invoke it. By the way, I would suggest following PEP8 for best readability.

Gabriel-p

comment created time in 3 days

issue commentsublimelsp/LSP

Suggestion for callback: on_post_initialize

I want to start a thread that will give an error dialog after 10 seconds if the server did not start properly.

You should leave that up to this package though. There's also no need to start a thread. You can use something like sublime.set_timeout(f, 10000) to run f after 10 seconds.

bostick

comment created time in 3 days

issue openedAmjadHD/sublime_one_theme

Text in update dialog could use padding

One theme:

https://cdn.discordapp.com/attachments/280102180189634562/891253475822948392/unknown.png

Default theme:

https://cdn.discordapp.com/attachments/280102180189634562/891265572422184980/unknown.png

created time in 3 days

issue commentsublimelsp/LSP

Suggestion for callback: on_post_initialize

Can’t you debug this at the server level catching the initialized notification from the client?

bostick

comment created time in 4 days

issue commentsublimelsp/LSP

Ruby Solargraph stuck on "mapping workspace" loop

In this client, and if I understand solargraph correctly, you should be able to set “logLevel”: “debug” in the “initializationOptions” dict.

jamesWalker55

comment created time in 4 days

release sublimelsp/LSP-OmniSharp

1.0.8

released time in 5 days

created tagsublimelsp/LSP-OmniSharp

tag1.0.8

Convenience plugin to install/update OmniSharp for LSP

created time in 5 days

pull request commentwbond/package_control_channel

Transfer WolframLanguage package to WolframResearch

Note that I have plans to switch to the python 3.8 runtime when package control libraries can run in 3.8: https://github.com/sublimelsp/LSP/issues/1389

when that happens, all helper packages must be upgraded to the py38 runtime as well.

bostick

comment created time in 6 days

pull request commentwbond/package_control_channel

Transfer WolframLanguage package to WolframResearch

On second though, I guess the ImportError catch will take care of that.

bostick

comment created time in 6 days

pull request commentwbond/package_control_channel

Transfer WolframLanguage package to WolframResearch

It should also require a minimum ST build version of 4000, seeing as you’re using constructs from LSP that are only available since that version.

bostick

comment created time in 6 days

PullRequestReviewEvent

Pull request review commentsublimelsp/LSP

Allow customizing diagnostics styles

 class Settings:     diagnostics_additional_delay_auto_complete_ms = None  # type: int     diagnostics_delay_ms = None  # type: int     diagnostics_gutter_marker = None  # type: str+    diagnostics_highlight_style = None  # type: Union[str, Dict[str, str]]

see https://mypy.readthedocs.io/en/stable/class_basics.html

iamkroot

comment created time in 7 days

Pull request review commentsublimelsp/LSP

Allow customizing diagnostics styles

 def diagnostics_tag_scope(self, tag: int) -> Optional[str]:         return None      def present_diagnostics_async(self) -> None:-        flags = 0 if userprefs().show_diagnostics_highlights else sublime.DRAW_NO_FILL | sublime.DRAW_NO_OUTLINE+        flags = userprefs().diagnostics_highlight_style_flags()  # for single lines+        multiline_flags = 0 if userprefs().show_multiline_diagnostics_highlights else sublime.DRAW_NO_FILL | sublime.DRAW_NO_OUTLINE

I don't get this show_multiline_diagnostics_highlights, do you also want to add the option to not render multiline diagnostics at all?

iamkroot

comment created time in 7 days

Pull request review commentsublimelsp/LSP

Allow customizing diagnostics styles

 class Settings:     diagnostics_additional_delay_auto_complete_ms = None  # type: int     diagnostics_delay_ms = None  # type: int     diagnostics_gutter_marker = None  # type: str+    diagnostics_highlight_style = None  # type: Union[str, Dict[str, str]]

It must remain None because from what I understand, this is the way to annotate class member variables in old versions of python.

iamkroot

comment created time in 7 days

Pull request review commentsublimelsp/LSP

Allow customizing diagnostics styles

               "markdownDescription": "Add an additional delay when the auto-complete widget is currently visible. Just like `\"diagnostics_delay_ms\"`, the unit is milliseconds. The total amount of delay would be `diagnostics_delay_ms + diagnostics_additional_delay_auto_complete_ms`."             },             "diagnostics_highlight_style": {-              "enum": [],-              "deprecationMessage": "Use \"show_diagnostics_highlights\" instead",+              "oneOf": [+                {+                  "enum": ["box", "underline", "stippled", "squiggly", ""],+                },+                {+                  "type": "object",+                  "properties": {+                    "error": {+                      "enum": ["box", "underline", "stippled", "squiggly", ""],+                      "default": "squiggly"+                    },+                    "warning": {+                      "enum": ["box", "underline", "stippled", "squiggly", ""],+                      "default": "squiggly"+                    },+                    "info": {+                      "enum": ["box", "underline", "stippled", "squiggly", ""],+                      "default": "stippled"+                    },+                    "hint": {+                      "enum": ["box", "underline", "stippled", "squiggly", ""],+                      "default": "stippled"+                    },+                  },+                  "additionalProperties": false+                }+              ],+              "default": {+                "error": "squiggly",+                "warning": "squiggly",+                "info": "stippled",+                "hint": "stippled"+              },+              "markdownDescription": "Highlight style of code diagnostics.\nCan be a string, or a mapping of string->string for severity-based styling.\nValid string values are `\"box\"`, `\"underline\"`, `\"stippled\"`, `\"squiggly\"` or the empty string (`\"\"`).\nWhen set to a valid string value, all severities will use that style.\nWhen set to the empty string (`\"\"`), no document highlighting is requested.\nDiagnostics which span multiple lines are always drawn with the `box` style (See `\"show_multiline_diagnostics_highlights\"`)."

This mentions "document highlighting is requested", but we're dealing with diagnostics, not document highlights.

iamkroot

comment created time in 7 days

PullRequestReviewEvent

Pull request review commentsublimelsp/LSP

Allow customizing diagnostics styles

 def document_highlight_style_region_flags(self) -> Tuple[int, int]:         else:             return sublime.DRAW_NO_FILL, sublime.DRAW_NO_FILL | sublime.DRAW_NO_OUTLINE | sublime.DRAW_SOLID_UNDERLINE +    @staticmethod+    def _style_str_to_flag(style_str: str) -> int:+        # This method could be a dict or lru_cache+        if style_str == "":+            return sublime.DRAW_NO_FILL | sublime.DRAW_NO_OUTLINE+        elif style_str == "box":+            return sublime.DRAW_NO_FILL+        elif style_str == "underline":+            return sublime.DRAW_NO_FILL | sublime.DRAW_NO_OUTLINE | sublime.DRAW_SOLID_UNDERLINE+        elif style_str == "stippled":+            return sublime.DRAW_NO_FILL | sublime.DRAW_NO_OUTLINE | sublime.DRAW_STIPPLED_UNDERLINE+        elif style_str == "squiggly":+            return sublime.DRAW_NO_FILL | sublime.DRAW_NO_OUTLINE | sublime.DRAW_SQUIGGLY_UNDERLINE+        else:+            return 0  # default styling++    def diagnostics_highlight_style_flags(self) -> List[int]:+        """Returns flags for highlighting diagnostics on single lines per severity"""+        if isinstance(self.diagnostics_highlight_style, str):+            # same style for all severity levels+            return [self._style_str_to_flag(self.diagnostics_highlight_style)] * 4+        elif isinstance(self.diagnostics_highlight_style, dict):+            flags = []+            for sev in ("error", "warning", "info", "hint"):+                user_style = self.diagnostics_highlight_style.get(sev)+                if user_style is None:  # user did not provide a style+                    flags.append(0)

How is the flag 0 rendered? Is 0 an appropriate default?

iamkroot

comment created time in 7 days

PullRequestReviewEvent

push eventsublimelsp/LSP

Raoul Wols

commit sha 57987062ea0bb9b25c65efcd47d5846d1778a3d6

Update client configuration docs

view details

Raoul Wols

commit sha b12404d5458ed55dcc50e55fd7d1c81196f62bcc

Fix inconsistency in indent adjustment behavior when completing There is a small inconsistency when we're dealing with a text edit and the text edit is not a snippet. In that case, if the new text of the completion contained newlines, the subsequent line would not be "auto-indented". Whereas with the three other possible cases, it would be auto-indented. That is because the other three cases use the "insert" and "insert_snippet" commands, whereas with this special case we were using the view.insert method.

view details

Raoul Wols

commit sha cd465638f9a112c61e943e75c1c09cdbe2d7570d

Advertise that we only do "adjust indentation" for completions Completions whose replacement text contains newlines will be auto-adjusted to the correct indentation level. There is no support for "as-is" style. This should give jdtls enough information to decide how to provide its multi-line completions.

view details

Raoul Wols

commit sha 95a7da52db00dd5d7254ed3f5fbb1365e4f80268

Make code lenses have the same behavior for both variants (#1825)

view details

Brenton Bostick

commit sha 7eb5367ce8409ae52a8630854c6560515f5ab357

Fix typo in release.py

view details

Raoul Wols

commit sha 8355aff6746afe2cd10e6dcb9cdd448e54519eca

Cut 1.9.0

view details

Rafał Chłodnicki

commit sha 8576d48017a7da96f0330397cfee26a0058cd9ac

Add AbstractPlugin.additional_formatting_options for tweaking formatting options (#1832)

view details

Rafal Chlodnicki

commit sha 08107b8950b71aa8970457d7edd6f69704e56915

Cut 1.10.0

view details

Evgeniy Andreev

commit sha 1a296f4e3c82d57eeb83b420ceb5b07a92570bfc

Add instructions for F#

view details

Evgeniy Andreev

commit sha 61b1058f8f337222f448c7567f7feb448320b905

Fix typo in F# instructions

view details

Raoul Wols

commit sha 8b9ae51885de8e165745792cf488c9333640f630

Revert "Always clear undo stack after a mutation on any panel (#1824)" This reverts commit c3075e979b3ced89ba2a4a4417f1f101157eaaf2.

view details

Raoul Wols

commit sha f08b63b5864faf04c489c3b49a49eb52a98d3e61

Cut 1.10.1

view details

Raoul Wols

commit sha 5144fcc9fb44fc8f6eedb1a2a7ff5c6e4baca7f5

Clear undo stack on every panel mutation (#1841)

view details

Predrag Nikolic

commit sha 05032066b709b8f5a1b953bd637dc56a16216ecf

document LSP-volar

view details

Предраг Николић

commit sha eafc5c5ce5ed1dfd2f0356438f528164b685f186

Docs add plugins (#1842) * document LSP-leo * document LSP-Bicep * document LSP-ltex-ls

view details

Предраг Николић

commit sha 0324d7f330a1ba181e3e60f9c43f066c3bf6396e

Send hover request to all sessions that supports hoverProvider (#1845) * using Promise.all * introduce MarkedString and MarkupContent types for readability

view details

Rafal Chlodnicki

commit sha 0153663813015100013bbe44e9903d81b0f1b0a5

Ensure the process is killed if it didn't exit within 1 second The logic seemed to be backwards. The poll() will return and exit code if the process has already exited and "None" otherwise. So we want to kill the process when the value is "None".

view details

jwortmann

commit sha df2b42af65b7a9d28294d7d0c9f089ff2b0d1362

Ensure lsp_save actually runs when context is active for keybinding (#1852)

view details

deathaxe

commit sha 3efac6deb2d3cee34b1ce1b3f01299d1c49591fb

Remove obsolete dependencies (#1853)

view details

Предраг Николић

commit sha 5b3204955cd669ff0bc3386adcc3021125f1ffe8

use config_name, because session.config.name can change

view details

push time in 7 days

create barnchsublimelsp/LSP-rust-analyzer

branch : chore/update-server

created branch time in 7 days

issue commentsublimelsp/LSP-json

Use `jsonc` for `buffer` schemes without a schema

This is from the "Parse package.json" command from LSP. It creates a temporary buffer.

image

rwols

comment created time in 7 days