codemonk
I switched from ISO to ANSI a few month ago. I touch type and I need German umlauts. Just as a background. This required me to find a layout that supports umlauts. I went with EurKEY. Overall, switching was easy. I do need a larger AltGr for umlauts but overall, switching was no big deal. I do like the shape of the return key on ANSI and that there are fewer keys right to my right pinky (on the home row). Typing umlauts is slightly less convenient, especially when capitalized, but not by much. Switching between ISO and ANSI and at the same time German layout and EurKEY is easy for me. Side note: I switched for the same reason (keycaps) and for writing code.
I prefer to keep tooling for that at a minimum. Therefore I use git only. My approach is taken from here: https://www.atlassian.com/git/tutorials/dotfiles
The only difference: My git alias is dotfiles not config. I find that to be less confusing. Additionally, I source system-specific configs, where appropriate. These are not stored in dotfiles. There is a small todo section in my readme.
I am working on an alternative to dmenu. My goal for it is to be fully configurable via a toml file. Most importantly it shall be able to toggle between types of entries (desktop entries, /usr/bin) on the fly. As of now, it is a less mature version of j4-dmenu-desktop and progress is slow. But it works as my daily driver on i3wn, both on my work VM and my personal laptop. So I can live with slow progress.
Technically, font healing is a neat idea. It fails for text that does not meat its requirements, i.e. two ‘m’ next to each other. Depending on the characters around them, this might create two different ‘m’.
This is unavoidable, of course. The only solution are proportional fonts. So font healing is a nice idea. It creates a more consistent spacing at the price of less consistent glyphs. Whether one likes this compromise, is a matter of taste. I personally lean towards consistent glyphs, but I did not try it for an extended period.
Interesting. Thanks for sharing. I started with WYSIWYG and did not like editing with proportional fonts. Things do not align, the cursor jumps around and movements have variable distances. But I much prefer looking at beautifully typesetted proportional font (e.g. with LaTeX). While I think, monospaced font are nice for editing, they are okayish to look at.
Thanks for the link. I will look into it and maybe try proportional for coding once more. Another idea I really like are almost proportional fonts. Read about these fonts a few month ago. So far I haven’t tried them.
Maybe ‘failing’ is too strong. What I mean is that in situations like the one I showed, texture healing cannot solve the problem of uneven texture. Not that they claimed it does. It just eases the problem. I like to know the trade-offs. When does it provide an improvement and when not? What tensions does that create?
From a users point of view, I do not know if it ‘fails’ or not. I totally agree with you. Maybe the I would find to distinct ‘m’ glyphs annoying, maybe not. And example emphasizes the ‘problem’. Maybe, I woukd even notice while coding or writing. To know that, I need to try. I just like to know the trade-offs in advance.
At work and for hobby projects. At work I am looking at using Rust for safety-critical systems. As a hobby I am building a dmenu alternative. It is a fun project and I have a menu that satisfied my wishlist.
