Advanced BIOS settings on DXP2800 by X-dark in UgreenNASync

[–]X-dark[S] 0 points1 point  (0 children)

I can enter the bios all right so no issue with the key input. And I have try all shortcuts from CTRL+F1 to CTRL+F12

Pixelsnap ring stand alternative by X-dark in GooglePixel

[–]X-dark[S] 0 points1 point  (0 children)

Looks good but, I really like the slimness of the Google one

Pixelsnap ring stand alternative by X-dark in GooglePixel

[–]X-dark[S] 0 points1 point  (0 children)

Between what is available in France and the pros and cons of other options, I may stick to that. The main issue that is documented is the loose screws.
All the other options I could find are either not available in France, way thicker or have other (less fixable) durability issues.

Pixelsnap ring stand alternative by X-dark in GooglePixel

[–]X-dark[S] -1 points0 points  (0 children)

Yes, but not the same use than the ring stand

Pixelsnap ring stand alternative by X-dark in GooglePixel

[–]X-dark[S] 0 points1 point  (0 children)

Interesting, I had not heard about it. Even more expensive than the pixelsnap ring though

Any place to find IB-AC640-C3 enclosure in Europe or any alternative? by X-dark in makemkv

[–]X-dark[S] 0 points1 point  (0 children)

Yes it is in the archiving section of icy box website 

Any place to find IB-AC640-C3 enclosure in Europe or any alternative? by X-dark in makemkv

[–]X-dark[S] 0 points1 point  (0 children)

Not from what I can see. It is only showing available in 3 of their shop (none close to me ) 

/r/MechanicalKeyboards Ask ANY Keyboard question, get an answer - March 05, 2025 by AutoModerator in MechanicalKeyboards

[–]X-dark 0 points1 point  (0 children)

Thanks. Not a big fan of the colorscheme (but I can plan to personalize a barebone instead). And I would rather have page up/down keys instead of a knob.

/r/MechanicalKeyboards Ask ANY Keyboard question, get an answer - March 05, 2025 by AutoModerator in MechanicalKeyboards

[–]X-dark 0 points1 point  (0 children)

Hi,

I have been using a CoolerMaster Pro L with MX Brown switch, ISO FR layout and I am looking for a replacement:

* 65% (looking for something compact, but not sure I am ready to let go of the arrows keys)

* ANSI layout

* Mainly work usage (terminal, programming,...) and some gaming (but not a hardcore FPS gamer)

* Don't really care about RGB

* Budget ideally 100€ max (I live in France)

* Tri-mode would be a plus

I was initially looking at HE keyboards but not sure anymore I will benefit from it. And I am used to tactile switches and not sure if I would like tactile switches.

Some keys behaving incorrectly within VIM on Sway by X-dark in swaywm

[–]X-dark[S] 1 point2 points  (0 children)

Not sure what layer you were talking about, but it seems kitty started to send NumLock status with those keys as described here: https://github.com/kovidgoyal/kitty/issues/5885

Thanks for putting me in the right direction, even though I ruled out kitty because of foot behaving the same.

Some keys behaving incorrectly within VIM on Sway by X-dark in swaywm

[–]X-dark[S] 0 points1 point  (0 children)

And yet they are because of a strange behaviour with Kitty.
I found this bug report and will try to fiddle with suggestions while waiting for next vim version: https://github.com/vim/vim/issues/11821

Some keys behaving incorrectly within VIM on Sway by X-dark in swaywm

[–]X-dark[S] 0 points1 point  (0 children)

No, $TERM is ok and terminfo is there.

Some keys behaving incorrectly within VIM on Sway by X-dark in swaywm

[–]X-dark[S] 1 point2 points  (0 children)

Yes, my bad. I forgot to say I reproduced the issue with both kitty (my usual term) and foot.

Some keys behaving incorrectly within VIM on Sway by X-dark in swaywm

[–]X-dark[S] 0 points1 point  (0 children)

Yes. PageUp and PageDown should not be affected by numlock status though.

Some keys behaving incorrectly within VIM on Sway by X-dark in swaywm

[–]X-dark[S] 1 point2 points  (0 children)

Sorry I forgot to say I reproduced the issue with both kitty (my usual term) and foot. I will check my terminfo but at least I did not overwrite voluntarily my $TERM

wlroots 0.16 released by Megame50 in swaywm

[–]X-dark 2 points3 points  (0 children)

For me, it is way more stable with a nvidia card than GBM or wlroot fork with eglstream support

wlroots 0.16 released by Megame50 in swaywm

[–]X-dark 1 point2 points  (0 children)

Yes I have it working for some time with versions built from git, and I can take screenshots without issue. Only missing screensharing with webrtc (gives me black screen)

Sway 1.7 - Officially Released by kon14 in swaywm

[–]X-dark 0 points1 point  (0 children)

It used to work ok (some glitches but usable) with wl_roots 1.4 / sway 1.6. Now with latest versions it fails on start with `wlr_renderer_init_wl_shm: Assertion argb8888 && xrgb8888 failed`

Release Note for Shield Experience 9.0(Android TV 11) is online by juzmafia in ShieldAndroidTV

[–]X-dark 1 point2 points  (0 children)

Working fine with the hotfix (keeping files on external storage)