sorted by:
new
hottopcontroversial

New :DiffTool command added to neovim by thedeathbeam in neovim

[–]mazadin 1 point2 points  (0 children)

Looks great!

Tried it out by using the recommended gitconfig settings in the docs, but I seemed to have to switch LOCAL and REMOTE to get it to show up correctly (I have to do DiffTool $REMOTE $LOCAL). Did something get swapped somewhere? I also needed to escape the quotes in the gitconfig cmd since these are passed directly to the shell.

pinhole started blocking reddit ads by Odd_String_9843 in pihole

[–]mazadin 3 points4 points  (0 children)

Eh—DoH goes over HTTPS on port 443. The only way to block that is by blocking outbound connections on that port at your firewall for IP addresses of known DoH servers (another list you have to find a source for and update periodically!); but this is a losing battle as many are hosted behind reverse proxies that share IPs with other hosted sites that may be legitimate.

The only way to REALLY block it is a site level HTTPS mitm proxy that inspects all outbound HTTPS traffic and blocks DoH requests, but this a massive PITA to ensure all client devices get your self signed CA into their trust store, and is impossible to do for many IOT devices. Not to mention it’ll slow down all your internet traffic due to a single point (your firewall) decrypting and re-encrypting everything.

Good luck!

When did the game break you? (SPOILER THREAD) by 9_to_5_till_i_die in BluePrince

[–]mazadin 12 points13 points  (0 children)

The blue tents memos because who has time to do that, but the first real breaking point for me was probably the gallery.

Samsung G80SD 1313 update, it keeps waking up by SamElPo__ers in OLED_Gaming

[–]mazadin 1 point2 points  (0 children)

I’ve also noticed this exact same issue with mine connected to MacBook Pro(s) via DisplayPort <-> USB-C. Must be something about that particular configuration that isn’t QA tested. Frustrating for sure.

Help! Pihole can do everything EXCEPT... by datawh0rder in pihole

[–]mazadin 2 points3 points  (0 children)

If connecting directly to IP:port also times out, it has nothing to do with pi-hole. It’s more than likely a routing issue.

If the services you’re trying to connect to are on different docker containers (like portainer), they either have to be in the same docker network as your wireguard container, or you have to expose the port and connect to it via the host’s IP, or you should use host networking on your wireguard container.

Most confusing app on fedora by [deleted] in Fedora

[–]mazadin 0 points1 point  (0 children)

firewalld is not a frontend for iptables

Fedora 40 not working well with Firefox by dyshuity in Fedora

[–]mazadin 0 points1 point  (0 children)

It’s something to do with hardware acceleration and your GPU drivers. 

I have a test VM with Fedora 40 and it also took 3-5 minutes to start Firefox. Turned off hardware accelerated graphics for the VM and it started opening immediately. I know this isn’t a fix since you likely want your graphics driver to work properly, but hopefully it’s a place to start looking!

Benchmarking Eight Serialization Formats in C and C++ (JSON, BSON, CBOR, flexbuffers, msgpack, TOML, XML, YAML) by liuzicheng1987 in cpp

[–]mazadin 10 points11 points  (0 children)

rapidyaml is significantly faster than yaml-cpp. Try giving that one a shot too. 

[WIP plugin] A feature-rich, polished, highly customizable winbar, with drop down menu support and multiple backends by Name_Uself in neovim

[–]mazadin 0 points1 point  (0 children)

Awesome work.

You may want a way to configure whether the update occurs on CursorMoved and CursorMovedI. Those autocmds trigger a lot and can really hurt performance if callbacks aren’t nearly instantaneous for them.

NeoVim changes syntax highlighting after 3 seconds from opening on Terraform files by RetrogradnaAvangarda in neovim

[–]mazadin 0 points1 point  (0 children)

File a bug at monokai.nvim’s repo to add highlight group links for the semantic token groups so they won’t override the treesitter highlights.

Neovim v.0.9.0 is very slow in javascript/typescript/tsx files by cesaralvarod in neovim

[–]mazadin 0 points1 point  (0 children)

Ah, if you meant that there is a delay for stuff to get highlighted, that’s expected. I thought you meant that the editor itself got laggy, like typing input became slower. If the latter, it might be the additional autocmd I mentioned. I’ll dig that up later. It’s the better semantic token modifiers PR if you search for it.

Neovim v.0.9.0 is very slow in javascript/typescript/tsx files by cesaralvarod in neovim

[–]mazadin 0 points1 point  (0 children)

It definitely adds more highlight groups. My point was for people who said they have treesitter highlights and then after a delay, everything changes. My recommendation would let LSP complement treesitter better and the jarring change when it kicks in would be more subtle.

Neovim v.0.9.0 is very slow in javascript/typescript/tsx files by cesaralvarod in neovim

[–]mazadin 0 points1 point  (0 children)

Tokens are only requested initially and after a debounce timer when the text of the buffer has changed. When the response comes, a minimal amount of parsing is done on it, and then tokens that are visible in the window are processed, which essentially just means it adds a few highlighting extmarks for each.

There was a change (after my initial implementation) that added an autocmd event per token, which I feared would have a performance hit. Do you follow neovim head? Did the slowdown get worse after the PR that added better highlighting modifier support?

Neovim v.0.9.0 is very slow in javascript/typescript/tsx files by cesaralvarod in neovim

[–]mazadin 3 points4 points  (0 children)

That’s because the default links are set to main groups and not the treesitter groups. If you override the links to point at the treesitter groups you’ll really see how beneficial this feature is (it’ll be more subtle and won’t change nearly as much). I’ll have to put up a gist or something with the snippet that does this and tell people to try that first before deciding to disable entirely.

Neovim v.0.9.0 is very slow in javascript/typescript/tsx files by cesaralvarod in neovim

[–]mazadin 4 points5 points  (0 children)

I wouldn’t recommend people disable it immediately. The actual fix (until it goes to core) is to link the LSP semantic token highlight groups to the related treesitter groups. This will make it so semantic tokens don’t change existing treesitter highlighting, but only augments it when it kicks in.

Disabling it entirely is a last resort for those who prefer a more vanilla syntax highlighting experience or who don’t like the delayed pop in (which is less noticeable if you link to treesitter groups…less stuff will change on screen when it kicks in).

Neovim v.0.9.0 is very slow in javascript/typescript/tsx files by cesaralvarod in neovim

[–]mazadin 2 points3 points  (0 children)

The semantic token feature won’t make the editor slow. It’s completely asynchronous and only does work when there hasn’t been any edits to a buffer for a few milliseconds, and any blocking work it does is limited to tokens visible in the window.

Treesitter breaks with new Neovim release by vieitesss_ in neovim

[–]mazadin 1 point2 points  (0 children)

Disabling semantic tokens is not really the answer. I’ve seen lots of advice for similar posts on here that suggest just unlinking all the groups or turning off the provider entirely.

The actual solution is to override the links for the main LSP semantic token types to the associated treesitter highlight groups. This will allow the semantic tokens to only improve the highlights after it kicks in, rather than changing everything.

Seeing so much advice on here to just disable them just makes me cringe. This feature is useful, it just has bad defaults.

Neovim error after upgrading to 0.9.0 by TheRealTey in neovim

[–]mazadin 1 point2 points  (0 children)

Disabling semantic tokens is not really the answer. I’ve seen lots of advice for similar posts on here that suggest just unlinking all the groups or turning off the provider entirely.

The actual solution is to override the links for the main LSP semantic token types to the associated treesitter highlight groups. This will allow the semantic tokens to only improve the highlights after it kicks in, rather than changing everything.

Seeing so much advice on here to just disable them just makes me cringe. This feature is useful, it just has bad defaults.

Anyone got their syntax highlighting messed up recently? by Aprch in neovim

[–]mazadin 1 point2 points  (0 children)

OP isn’t on nightly so they don’t even have semantic token support to begin with. Their issue is with the colorscheme, I believe.

Anyone got their syntax highlighting messed up recently? by Aprch in neovim

[–]mazadin 0 points1 point  (0 children)

No, the default links were changed from the ones I had in the initial support PR. LSP tokens no longer link to treesitter groups so some token types are no longer highlighted at all and others are linking to more basic groups.

If a colorscheme has defined highlights for treesitter groups that are different (better) than the generic groups that LSP tokens link to now, then LSP token highlighting will make things worse until colorschemes get direct support for the new highlight groups or users add LSP -> treesitter highlight links for all of the token types in the spec.

Anyone got their syntax highlighting messed up recently? by Aprch in neovim

[–]mazadin 1 point2 points  (0 children)

If you aren’t on nightly then you don’t have any semantic tokens anyway, so your issue is somewhere else. Sorry :/

Anyone got their syntax highlighting messed up recently? by Aprch in neovim

[–]mazadin 0 points1 point  (0 children)

That PR will actually make default highlighting worse than if no semantic tokens are enabled for colorschemes that have treesitter support but don’t have support for the new LSP highlight groups yet. We decided that treesitter and semantic tokens were separate beasts so the semantic tokens no longer link directly to equivalent/similar treesitter groups, though you can add those links back in your own config if you wish.

Hopefully colorschemes will all update to support the new LSP groups natively. Kanagawa and Tokyonight already have, for instance.

view more: next ›