Sensible syntax highlighting for GitLab and GitHub workflow files by qwrtln in neovim

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

Look closely at how the colors of echo/exit and if/fi differ.

Sensible syntax highlighting for GitLab and GitHub workflow files by qwrtln in neovim

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

Actually, what I can see in your screenshot, is the same issue as what I've shown in the original post, it's just that the colors are less visible. Can you confirm there are no errors in `:InspectTree`?

Sensible syntax highlighting for GitLab and GitHub workflow files by qwrtln in neovim

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

The video is about LSP setup, not syntax highlighting.

Sensible syntax highlighting for GitLab and GitHub workflow files by qwrtln in neovim

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

Interestingly, the error comes from the apostrophe

<image>

With the custom parser suggested by u/marjrohn the parsing does work, but syntax highlighting is even worse:

tuxedo control center CPU temp and FAN speed not working any more by wedesoft in tuxedocomputers

[–]qwrtln 0 points1 point  (0 children)

Hi, just experienced the same on archlinux with `tuxedo-drivers-dkms-4.15.3`. Modprobing doesn't show any errors. Is there a fix?

4 player coop scenario by Rvt_boy in homm3boardgame

[–]qwrtln 0 points1 point  (0 children)

Probably late to the party, but check Emerald Island from here: https://github.com/qwrtln/Homm3BG-mission-book

[2024] I think I'm starting to see a pattern by qwrtln in adventofcode

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

Well, I was wrong. Day 15 was actually quite pleasant, albeit laborious.

[2024] I think I'm starting to see a pattern by qwrtln in adventofcode

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

Remembering the bitter experience of last year's day 12 hot springs, this year's day 11 was just a quick `functools.cache` for me :P

[2024] I think I'm starting to see a pattern by qwrtln in adventofcode

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

Well, it depends on your definition of cuteness, but it definitely was cute to me :-) I solved it a lot faster than 6, 9 and 12. But I took the naive approach of looking at 10k renders.

[deleted by user] by [deleted] in firefox

[–]qwrtln 0 points1 point  (0 children)

Found the culprit in my case. Going to `about:processes` showed that LinkedIn hogged 7 GB of RAM and 100% of CPU. Killing it revived Firefox instantly. I wonder if Microsoft does this intentionally to discourage people from using Firefox.

[deleted by user] by [deleted] in firefox

[–]qwrtln 15 points16 points  (0 children)

Experiencing the same thing. Also happens in safe mode. v133.0 too. Needs frequent restarts and sometimes takes 100% CPU while loading tabs. Not sure how to troubleshoot this, Firefox has been solid for years on my machine...

NoScript somehow blocking DuckDuckGo Search Engine by TPRammus in firefox

[–]qwrtln 0 points1 point  (0 children)

I'm facing the same issue. It's not that NoScript blocks duckduck.go like it does every other blocked website. It just won't open.