~proycon

Eindhoven, the Netherlands

https://proycon.anaproy.nl

  • 🐧 FOSS software enthusiast
  • 🎓 Research Sofware Engineer, Natural Language Processing
  • 🐍 Python, 🌊 C, C++, 🦀 Rust, 🐚 Shell
  • 🔐 Privacy and Security
  • 📱 Sxmo co-maintainer
  • 🏡 Home automation
  • 🌍 Language enthusiast

See my homepage at https://proycon.anaproy.nl for further details and contact info.

~proycon/public-inbox

Last active 10 months ago
View more

Recent activity

Re: [PATCH sxmo-utils] sys menu: include an entry for the WM menu 3 days ago

From Maarten van Gompel to ~mil/sxmo-devel

Thanks! I agree it makes sense to have this in the top-level menu, so
I applied it now.

-- 

Maarten van Gompel

Re: [PATCH sxmo-utils 01/11] apps: add Chatty 3 days ago

From Maarten van Gompel to ~mil/sxmo-devel

Thanks! This entire patch series has been applied now!

Re: [PATCH sxmo-utils] sxmo_hook_tailtextlog.sh: fix timezone parsing a month ago

From Maarten van Gompel to ~mil/sxmo-devel

Thanks, nice catch! Applied now.

Re: [PATCH wvkbd] Make font selection scheme specific a month ago

From Maarten van Gompel to ~mil/sxmo-devel

Thanks! Even though we don't use this, I think this is a nice
unobtrusive feature that allows the user more customisation. I have
applied it now.

In the past, we had issues with some multichar keycap labels being too big
for a key when increasing the font size, this might offer a way out of
such a problem by setting a different scheme for certain keys.

-- 

Maarten van Gompel (proycon)

web: https://proycon.anaproy.nl
gpg: 0x39FE11201A31555C

Re: [PATCH] Add support for square keys a month ago

From Maarten van Gompel to ~mil/sxmo-devel

Marked as rejected for now

Re: [PATCH] add " " BODY to dunstify a month ago

From Maarten van Gompel to ~mil/sxmo-devel

> Ok, I'll see what can be done at the amazfish side to fix this problem.

Great, hopefully there's an easy solution on their side. Marking this as rejected in the meantime.

Re: [wvkbd] Layout files instead of hardcoding a month ago

From Maarten van Gompel to ~mil/sxmo-devel

> Aren <aren@peacevolution.org> wrote:
> > It keeps the code simple because we can reuse the parser for the c
> > compiler to parse our layout files. The c compiler also provides type
> > checking to make sure you give it a valid config file for free, which
> > actually makes testing layout file easier.

Indeed, it also makes things faster at runtime because no files need to
be read and parsed; everything is compiled in.

> Then can wvkbd to be engineered in a fashion which has its layout files
> separately, and while it compiles, it would hardcode the availlable
> config files into it as it does now?

In theory, yes, but I don't see much added value in such extra

Re: [wvkbd] Return to last used locale from layout Special a month ago

From Maarten van Gompel to ~mil/sxmo-devel

> When icon keyboard is pressed *with "shift" key* from a language layout
> it could open layout "Special" instead of layout "Full".

The 'Special' layout is the symbol layout, it's usually the second
layout *but this is configurable using the `-l` or `--landscape-layers`
parameters*. 

The keyboard key will by definition take you to the next layout in this
list. Shift + keyboard key will be definition take you to the previous
layout in the list. Pressing Cmp + keyboard key will show the Index of
layouts for switching to any (even those not in -l or
--landscape-layers). Pressing Abc/Абв or similar will take you back to
the previous *alphabetic* layout (so not counting things like the
Special layout).

Re: wvkbd (Arabic, Farsi, Greek, Hebrew) (was Re: wvkbd) a month ago

From Maarten van Gompel to ~mil/sxmo-devel

Hi Schimon,

> This email was intended for Maarten, but after observing issues with
> othre layouts, I've decided to send this to the mailing list.

Thanks for the testing of the layouts. The mailing list is indeed the
proper place for this. I guess the layouts are used by few
people so it's good to iron out the bugs that are undoubtedly still in
there!

> Hebrew
> ------
>
> 2) Shift

Re: [PATCH] add " " BODY to dunstify a month ago

From Maarten van Gompel to ~mil/sxmo-devel

This feels a bit patchy and I'm not sure this is something that should
be patched on our side. According to the spec
(https://specifications.freedesktop.org/notification-spec/notification-spec-latest.html#command-notify),
the body is explicitly optional.

I don't know anything about harbour-amazfish, but I guess that's what
relays the notifications to your smartwatch? Then maybe that's the
better place to more elegantly solve this?

-- 

Maarten van Gompel (proycon)

web: https://proycon.anaproy.nl