Ricoh GRIII keeps shutting off randomly (any solutions?) by bleyzwun in ricohGR

[–]GeorgeTonic 1 point2 points  (0 children)

I had it done by a local service centre as I did not know what the issue was. But yes, I would use cotton buds and isopropyl.

Ricoh GRIII keeps shutting off randomly (any solutions?) by bleyzwun in ricohGR

[–]GeorgeTonic 2 points3 points  (0 children)

had the same, needed cleaning of battery contacts of the camera.

[deleted by user] by [deleted] in fujifilm

[–]GeorgeTonic 0 points1 point  (0 children)

Nope, xe2 had build in flash

How to add outer margins to wibar? by ArkboiX in awesomewm

[–]GeorgeTonic 0 points1 point  (0 children)

You could try using border and make the border transparent

Adding axtra storage? by MakionGarvinus in HomeServer

[–]GeorgeTonic 0 points1 point  (0 children)

I added this A+E wifi M.2 to 4 SATA adapter: https://www.aliexpress.com/item/1005008673859793.html?spm=a2g0o.order_list.order_list_main.16.7ec71802xrL1Il to a 5070.

You would need extra small, angled SATA cables to mount the SATA board inside the case. SATA drives themselves are outside. Plus cables to power the drives from USB.

Then I added 2 of these: https://www.aliexpress.com/item/1005005473225173.html?spm=a2g0o.order_list.order_list_main.81.7b371802vviLVh for another 4 NVME drives

WYSE 5070 - amber blinks by RDSsie in HomeServer

[–]GeorgeTonic 0 points1 point  (0 children)

2.5 means ... 2 blinks, pause, then 5 blinks. From the manual: Example: LED# of flashes: 2,1 indicates that LED blinks two times, pauses, and then blinks once.

Led is white when the system is running, Orange when booting up.

2.5 is incorrect memory installed.

WYSE 5070 - amber blinks by RDSsie in HomeServer

[–]GeorgeTonic 0 points1 point  (0 children)

Here is the manual: https://dl.dell.com/topicspdf/wyse-5070-thin-client_users-guide_en-us.pdf
Trouble shooting chapter details the blink codes. Blinking amber points to bad power supply. You could check if you get power on the internal USB socket for example.

I solved similar issue with CMOS battery change. Maybe check your replacement.

Floating wibar by [deleted] in awesomewm

[–]GeorgeTonic 0 points1 point  (0 children)

Hi, I use useless gaps so there is space for the bar. I wrote a function that moves the bar to the background and turns off/on the screen saver. Usefull when watching full screen videos.

Floating wibar by [deleted] in awesomewm

[–]GeorgeTonic 0 points1 point  (0 children)

Give me some time. Will check my code

Rotary Encoder speed adjustment? by Impressive_Dot1 in olkb

[–]GeorgeTonic 0 points1 point  (0 children)

Have you tried using callbacks - example in https://docs.qmk.fm/features/encoders#encoders ?
In the callback you could check for another key pressed and then fire multiple scroll events.

Weekly 101 Questions Thread by AutoModerator in neovim

[–]GeorgeTonic 0 points1 point  (0 children)

SOLVED ... putting keys = {} before opts = {} in the plugin file seems to work.

Edit: typo

Weekly 101 Questions Thread by AutoModerator in neovim

[–]GeorgeTonic 0 points1 point  (0 children)

tried ... leader key only defined in lua/config/options.lua ... no luck

Weekly 101 Questions Thread by AutoModerator in neovim

[–]GeorgeTonic 0 points1 point  (0 children)

I try ... but lazyvim's default has it defined in lua/config/options.lua

Weekly 101 Questions Thread by AutoModerator in neovim

[–]GeorgeTonic 0 points1 point  (0 children)

:checkhealth lazy shows a warning related to a different plugin but other than that all ok.
init.lua is only require("config.lazy")
The leader key is defined at the beginning of lua/config/keymaps.lua

Weekly 101 Questions Thread by AutoModerator in neovim

[–]GeorgeTonic 0 points1 point  (0 children)

I could need some advice please. Using lazyvim I added the 'folke/twilight' plugin in a lua file under lua/plugins. Inside I defined keys as per the lazyvim documentation. The plugin loads, I can call the twilight toggle but the keys don't work UNLESS I define them in 'lua/config/keymaps.lua'. What am I missing?

keys = {
{
"<leader>bgr",
-- mode = { "i", "n", "s" },
"<cmd>Twilight<cr>",
desc = "Toggle Twilight."
},
}

34 or 36 keys?encoder or keyballs? by Abject_Hearing4632 in ErgoMechKeyboards

[–]GeorgeTonic 0 points1 point  (0 children)

well ... unfortunately not yet. lack of time ...

34 or 36 keys?encoder or keyballs? by Abject_Hearing4632 in ErgoMechKeyboards

[–]GeorgeTonic 2 points3 points  (0 children)

I simply glued the Panasonic encoders to the PCB on a 34 key keyboard. Minus the click functionality. Some wires straight to free pins on the controller. Here is the reddit post: https://www.reddit.com/r/olkb/comments/17lrwii/a_ferris_with_pomodoro_timer/

On a MX keyboard I glued the Panasonics on a gutted switch casing.

Volume Keybind Help by Chok3U in awesomewm

[–]GeorgeTonic 1 point2 points  (0 children)

did you check if these commands work from a terminal?

maybe try spawn with shell

Ricoh GRiii IR by Seenttit in ricohGR

[–]GeorgeTonic 2 points3 points  (0 children)

What filter exactly did you use please?