Martijn
Martijn
@webpro I could (kinda) reproduce this in `reveal.js`, so I created an issue upstream: https://github.com/hakimel/reveal.js/issues/3671
Is there any update on this? This would be very handy to change from powerline to starship
I just tried ShareX as a replacement for GreenShot and was suprised to see my screenshot on imgur. This is a big no no! It broke my trust and I...
I have the same behavior: NVIM v0.10.2 deno 2.1.4 peek.nvim: 5820d937d5414baea5f586dc2a3d912a74636e5b ```lua { "toppair/peek.nvim", event = { "VeryLazy" }, build = "deno task --quiet build:fast", keys = { { "md",...
It's probably best to create a PR for each for history (in case a bug has to be tracked down)
> (unbuf ECC) is new New memory can have bit errors, happened to me once and your symtoms sound familiar. Don't assume, verify with proof: memtest the new RAM.
I am still having the exact same problem ...
I've just found it, `nvim-treesitter` doesn't allow this: https://github.com/folke/lazy.nvim/issues/1917#issuecomment-2651644847 Perhaps this could be added to the documentation to watch for? I've spent hours trying to solve this problem
> I don't think we can do this until sway implements the equivalent of [i3/i3#5469](https://github.com/i3/i3/pull/5469) This has been merged, can this be revisited?
Oh, I misread! My apologies For sway it is https://github.com/swaywm/sway/pull/7961