202 karma · joined October 10, 2017
Eglot: https://joaotavora.github.io/eglot/#Setting-Up-LSP-Servers
lsp-mode: https://emacs-lsp.github.io/lsp-mode/page/adding-new-languag...
Turning off the browser intergation means that the user may accidentally auto-type into the wrong website. Turning off auto-type means that external applications can see the password.
[1]: https://github.com/Squirrel/Squirrel.Windows/tree/develop/do...
[2]: https://github.com/electron/electron/blob/main/docs/api/auto...
Does kind feel like a translation of
> They've got company
Though I find it's more common for a negative space click to just move a page and not jump to the location, so maybe that's influenced me.
Edit: it would need context awareness too, which somewhat rules out espanso, otherwise space indentation will be difficult. abbrevs at least can be defined per mode, but ideally it would be based off the face (so it could work in comments or strings).
Since you are the one writing them, you can make them in a format that is easier for you than a random blog post (that you will not be able to find again).
That said, I do think it would be nice to have written down that 8/9 are commonly used as backwards/forwards. They are just not explicitly backward/forward buttons though.
I think it's more convention, as the applications are ultimately what are deciding to do with the mouse button. There's nothing to say that they could not put a context menu on the left click.
https://www.x.org/releases/current/doc/man/man4/mousedrv.4.x...
"""
Option "ButtonMapping" "N1 N2 [...]"
Specifies how physical mouse buttons are mapped to logical buttons. Physical button 1 is mapped to logical button N1, physical button 2 to N2, and so forth. This enables the use of physical buttons that are obscured by ZAxisMapping. Default: "1 2 3 8 9 10 ...".
"""
Does https://learn.microsoft.com/en-us/powershell/module/microsof... do the trick?
> A massive UI overhaul (but without breaking features) is almost definitely a major version bump
as I think effect of UI changes tends to be underestimated. Just because v1 & v2 both have a button to frobnicate doesn't mean that they are equal. If v1 had a big large frobnicator in the main screen, and v2 buried it in a menu, you could say that no feature was broken, but the user interaction is very different.
That sort of change often gets rolled into a minor/patch bump, but it does break workflows. However if every change like that bumped the major version, it would be noise. There would be no way to judge the scale of the changes from v9 to v23 vs v14 to v16.
I'm not sure if the spirit of the law of SemVer applies here though. The type of change is not important, only how much has changed. Bugs can be features.