fonts in kate

[Ralf Mardorf]

On Mon, 14 Jun 2021 20:43:38 -0700, rikona wrote:
>On Mon, 14 Jun 2021 22:26:04 +0200 Liam Proven wrote:
>> The thing that you must remember at all times is that while the Arch
>> wiki is superb at explaining what happens and why it happens and what
>> you can do, it is solely intended as a reference tool for Arch Linux.
>> Anything that it tells you about config files, or file locations, or
>> dependencies, or libraries, or whatever, may either not help you with
>> Ubuntu, may cause you to break your OS very badly, or may lead you up
>> a blind alley.  
>
>understood  - this is also true of non-arch sites too - older,
>different configs, etc may still not work on my box. 

The problem with askubuntu, stackexchange etc. is not just the date,
but also the need to chose between 25 threads treating the same subject
and within each thread just 1 out of 25 posts makes sense, while this
single post might either be for another Ubuntu release or another
distro. When taking a look at the Arch Wiki, you know that it's not
intended for Ubuntu, but you can be sure that it treats important
topics with compact and reliable information.

Related to some topics the Debian Wiki provides as compact and reliable
information as the Arch Wiki does. Since Debian is Ubuntu's upstream, it
could be a better source of information.

https://www.omgubuntu.co.uk/2020/04/ubuntu-20-04-fractional-scaling-support-setting
https://wiki.debian.org/MonitorDPI

Btw. regarding multiples of 2, even old CPUs without "real" mathematical
commands, such as the C64's 6502 (6510) provided to move bits by
commands. 

ASL 	Arithmetical Shift Left
LSR 	Logical Shift Right 
ROL 	ROtate Left
ROR 	ROtate Right

Once a value is stored to a register, those commands require minimal
clock cycles.

It's interesting that nowadays an overview doesn't mention how much
clock cycles the usage of a command does take, see
https://www.c64-wiki.de/wiki/Übersicht_6502-Assemblerbefehle .

That time I used a book mentioning the clock cycles by the overview of
the commands. When we (other as well as I) wrote software, we usually
were taking care to write routines taking less clock cycles.