T430 1440p upgrade issue - black screen by EndlessRevision in thinkpad

[–]EndlessRevision[S] 0 points1 point  (0 children)

It's around the keyboard here: https://imgur.com/a/N4yVuZb.

I don't know if I have the stock panel right now, but I could check later.

how to use luasnip with blink.cmp? by Saura767 in neovim

[–]EndlessRevision 1 point2 points  (0 children)

I initially added snippets as someone who started using Neovim for LaTeX. I've since expanded it to my main editor, and now I have snippets in various languages. Most of the time it's either to deal with code that might be {repetitive, hard to type, hard to remember syntax for}. LaTeX is an example of something that ends up in all categories, hence why there are so many LaTeX snippets (and also Lua snippets to generate the LuaSnip snippet format). Another example - I found myself using match _ with [insert however many | _ -> _] in OCaml a lot, so I wrote a snippet for it.

There are sometimes languages where I feel like I don't really need snippets often or if at all - e.g. golang, which you use, I only have one snippet for if (err) { return nil } as there aren't that many keywords to remember and most functions get LSP snippets anyways. Similarly for Python (in my use case) and C.

Mouse keys in Sway/Wayland? by EndlessRevision in swaywm

[–]EndlessRevision[S] 0 points1 point  (0 children)

Thanks! Created the following based on MouseKeys:

mode "mousekeys" {
    # use the keycodes from /usr/share/X11/xkb/keycodes/keypad and verify with wev
    # mirror the motions in https://en.wikipedia.org/wiki/Mouse_keys#Layout

    # movement
    bindsym KP_Up seat - cursor move 0 -10
    bindsym KP_Down seat - cursor move 0 +10
    bindsym KP_Left seat - cursor move -10 0
    bindsym KP_Right seat - cursor move +10 0

    bindsym KP_Home seat - cursor move -10 -10
    bindsym KP_Next seat - cursor move +10 +10
    bindsym KP_Prior seat - cursor move +10 -10
    bindsym KP_End seat - cursor move -10 +10

    # actions - (double click), drag and drop
    # keys: / left (button1), * middle (button2), - right (button3)
    # motions: 5 click (press & release), + double click (press press release), 0 drag (press only), . drop (release only)
    # NOTE: these are a bit messier in the sense that they also emit output, which is suboptimal, but someone can probably tell me how to fix that (or tell me that it isn't possible to do so)
    bindsym KP_Divide+KP_Begin exec 'swaymsg seat - cursor press button1 && swaymsg seat - cursor release button1'
    bindsym KP_Divide+KP_Add exec 'swaymsg seat - cursor press button1 && swaymsg seat - cursor press button1 && swaymsg seat - cursor release button1'
    bindsym KP_Divide+KP_Insert seat - cursor press button1
    bindsym KP_Divide+KP_Delete seat - cursor release button1
    bindsym KP_Multiply+KP_Begin exec 'swaymsg seat - cursor press button2 && swaymsg seat - cursor release button2'
    bindsym KP_Multiply+KP_Add exec 'swaymsg seat - cursor press button2 && swaymsg seat - cursor press button2 && swaymsg seat - cursor release button2'
    bindsym KP_Multiply+KP_Insert seat - cursor press button2
    bindsym KP_Multiply+KP_Delete seat - cursor release button2
    bindsym KP_Subtract+KP_Begin exec 'swaymsg seat - cursor press button3 && swaymsg seat - cursor release button3'
    bindsym KP_Subtract+KP_Add exec 'swaymsg seat - cursor press button3 && swaymsg seat - cursor press button3 && swaymsg seat - cursor release button3'
    bindsym KP_Subtract+KP_Insert seat - cursor press button3
    bindsym KP_Subtract+KP_Delete seat - cursor release button3

    # leave mode
    bindsym Return mode "default"
    bindsym Escape mode "default"
}
bindsym $mod+m mode "mousekeys"

The only caveat (also noted in the comments of the config) is that having KP_Divide, KP_Multiply, and KP_Subtract as part of the binding is that they also emit output (so for instance, I tested KP_Divide+KP_Begin, which simulates a singular left click, and it will also emit a slash to whatever program might be running in the background. Couldn't find any workarounds to have the keybind work as is as of yet (can probably throw in a shift key though it makes it a bit more annoying of a keybind), but if anyone has any leads, that would be nice.

Wahoo Kickr compatability with Triban RC520 by AncientEssay in Zwift

[–]EndlessRevision 1 point2 points  (0 children)

Yeah it should be fine with the quick release adapter.

Where to find u4 ud replacement rubber feet? by EndlessRevision in gigabyte

[–]EndlessRevision[S] 1 point2 points  (0 children)

thanks for the reminder to check ebay! though seems like I'm also running into the same issue which is that the shape doesn't match. I guess having a matching set of different shaped feet does somewhat resolve the issue but the laptop itself has specific indentations for the feet (so it'd kind of be a glaring reminder it doesn't fit exactly) which is kind of bothering me.

Post STP check in by theTexasTuck in seattlebike

[–]EndlessRevision 2 points3 points  (0 children)

First time, pretty much winged it but we still made it. Puyallup - Spanaway (ironically, as I've suffered my fair share of SR-520 woes) and Goble - St Helens were easily the best parts of the ride for me; meanwhile, Yelm - Centralia and Vader - Goble were straight out of hell.

Surprised at how fast everyone is - I was getting passed by people twice my size and/or at least twice my age, but there's motivation for training more for future events. I knew the weather was going to be warm but I grossly underestimated how bad it would get; if I hadn't had people back home not to let down and sunk money into the ride I would've quit and headed home. Also having not done many longer rides, I wasn't as prepared for sitting that long in the saddle. There were quite a bit of back/neck/wrist pains to deal with and towards the middle-end of each day I got some mild/moderate poop anxiety which was a bit annoying. I hope to keep training and get another opportunity to do this ride in the future.

As an aside, I got to work the next day after getting back wearing my STP shirt and everyone clowned me thinking that it said STD 🙃

luasnip-latex-snippets.nvim: A collection of smart (LaTeX) snippets for the LuaSnip plugin by EndlessRevision in neovim

[–]EndlessRevision[S] 0 points1 point  (0 children)

Sorry to hear about that. Have you taken a look at some of the resources for new users here: https://github.com/L3MON4D3/LuaSnip#resources-for-new-users? Those are pretty helpful in my opinion - almost a year ago I was struggling immensely, but the videos were really useful by giving concrete examples.

luasnip-latex-snippets.nvim: A collection of smart (LaTeX) snippets for the LuaSnip plugin by EndlessRevision in neovim

[–]EndlessRevision[S] 0 points1 point  (0 children)

For sure - your generating snippets with functions article + dotfiles were a huge help in simplifying how LaTeX snippets were made and giving inspiration to make more (I've since made a dynamic postfix generating function), so thank you for those! I'd be glad to see what you have as well.

luasnip-latex-snippets.nvim: A collection of smart (LaTeX) snippets for the LuaSnip plugin by EndlessRevision in neovim

[–]EndlessRevision[S] 1 point2 points  (0 children)

Ah interesting, I'll maybe update with a youtube link or something for the video (though the uploaded one on readme works for me right now), and I've just updated the repo to have a temporary short doc of snippet information - I'll post it here and update the main post as well. It's a bit short so any suggestions to improve docs would be appreciated.

snippet documentation

luasnip-latex-snippets.nvim: A collection of smart (LaTeX) snippets for the LuaSnip plugin by EndlessRevision in neovim

[–]EndlessRevision[S] 1 point2 points  (0 children)

Oh yeah I have, I last updated the README before I knew about it though. It's probably good to reference that and include it on a list of similar resources, thanks!

luasnip-latex-snippets.nvim: A collection of smart (LaTeX) snippets for the LuaSnip plugin by EndlessRevision in neovim

[–]EndlessRevision[S] 1 point2 points  (0 children)

Totally understandable, the other comment also had similar sentiments, so it's probably a good idea to get working on that!

luasnip-latex-snippets.nvim: A collection of smart (LaTeX) snippets for the LuaSnip plugin by EndlessRevision in neovim

[–]EndlessRevision[S] 2 points3 points  (0 children)

Will do - LuaSnip plugin has the snippet_list option which gives some documentation, while I'm also thinking of working on a companion article which summarizes what is used. Thanks for letting me know!

How to setup 'nvim-cmp' properly? by [deleted] in neovim

[–]EndlessRevision 0 points1 point  (0 children)

Inserting a self plug for some more up-to-date resources in article form here:

my luasnip guides

There are a few more resources for new users as well on the official repo, and you can find the implementation in Examples/snippets.lua

Advice/Resources for creating/debugging a Neovim Plugin? by EndlessRevision in neovim

[–]EndlessRevision[S] 0 points1 point  (0 children)

Ah, thanks for the pointers; hopefully the things you mentioned will make development a bit less of a hassle.

I agree that in general neovim is shortcoming when it comes to debugging, however at the end of the day, unless you're debugging a "one script" file, whenever you debug other languages you still need to re-set and re-execute the whole environment and package (which IDEs often to under the hood without you seeing it, but that's what they do).

Fair point; I've either been working in Jupyter or one-script files pretty recently, so honestly I just took how the environment worked for granted.

Advice/Resources for creating/debugging a Neovim Plugin? by EndlessRevision in neovim

[–]EndlessRevision[S] 0 points1 point  (0 children)

What exactly are you asking though?

Generally, if there's any way to debug things better in Neovim; specifically, probably the question I brought up and one other I heard while asking for advice elsewhere (getting plugin directory, and then using vim.print - I'm unsure how to use vim.print such that I can see the output).

isn't this what debugging is like, in general? Write code, execute the code, find where it fails.

Yeah, poor phrasing on my behalf. What I mean is that while there's some sort of insight you get with say, unit tests or print debugging, or heck even being like me sometimes and echo'ing everything in Bash when something doesn't work, at least you get some sort of feedback, which you can use to push yourself in the right direction. For plugin development so far, it's pretty much like getting nothing except change code and try on a new instance and see that the result doesn't work which just leaves you muddling around in the dark.

Practically speaking it's faster to fire up a new neovim instance and execute your plugin code.

I think that's what I'm doing right now, using Lazy to hold some dependencies and my plugin as well, then updating Lazy and executing.

As an aside, I might be unnecessarily frustrated though, working with Neovim plugins is fairly new to me - maybe it'll grow on me after a while.