sjohannes

What tool or program would you recommend for learning touch typing on Linux?

I don't have a particular recommendation, but in addition to local applications, there are also websites that you can try. The keyword you want to search for is "typing tutor", e.g. on Debian.

For someone whose native language isn’t English, would you recommend learning on their native keyboard layout or switching to the US QWERTY layout for programming purposes?

For programming, the most important thing is that you can type the full set of characters present on US-QWERTY without too much acrobatics, because programming languages tend to use all/most of them.

Other than that it's just down to your preference and comfort. I don't recommend putting stock on any hype related to typing speed.

I've tried two different setups for Hangul input.

The first combination (GNOME+X11+IBus) just worked—it was trivial to setup from the GNOME Control Center and there were no issues that I could find. Last time I tried this was around a year ago but it had been working for years before that.

The second combination (Plasma+Wayland+IBus) barely worked: I could enter characters but couldn't add space or other symbols between characters, and settings were all over the place and would randomly stop working. Last tested ten minutes ago.

I've heard people getting better results on Plasma+Wayland+Fcitx5 but it's not something I've tried.

Do languages that use non-Latin alphabets (Asian, Cyrillic, Greek, Hebrew) have upper and lower case letters?

Greek has upper and lower case. From mathematics/physics you may have come across e.g. the ones for sigma (Σ, σ). Cyrillic also has them; most look the same between the upper & lower case variants, just bigger/smaller (Л, л), but there are some that differ (А, а).

I don't think most Asian scripts have letter cases. Javanese script does have upper case but only for a small subset of letters and they are generally not used anymore.

What about serif or sans-serif?

Cyrillic and Greek, yes. There are also equivalents to the serif and sans-serif typefaces in Chinese, Japanese, and Korean typography.

How do they show emphasis?

On the Web, boldface (but not italics) is very commonly used across various writing systems. Obviously no all caps for those without capital letters.

I don't think the reason was technical. Firefox has supported WebM (a subset of Matroska) for 11 years, and whatever code they had probably would have been enough for most Matroska files, assuming the codecs are also supported.

However, Matroska itself was only officially standardised last October despite being in use all these years. That was probably what convinced them to add support.

Their blog has regular updates regarding Exchange support, if you're interested.

It doesn't launch the new binary at all. When the current process wants to create a new process, instead of doing fork+exec (which launches the new binary and wreaks havoc because versions now don't match), it simply tells the ForkServer (a different process running the old binary) to fork (split) itself.

Chromium also does this; they call their equivalent to ForkServer the zygote process and this article explains it really well.

All external links from news.itsfoss.com articles have that ref parameter added. For example, see the links in this article about the Danish ministry that is switching to LibreOffice.

Edit: This is apparently something that the CMS they use, Ghost, does by default.

They're switching their main repository from Mercurial to Git. Mozilla started using Mercurial before Git became de facto standard, but I imagine these days learning Mercurial is seen as an unnecessary obstacle for new contributors, hence the current switch.

As for why GitHub specifically, it's because that's where the rest of Mozilla's projects already are. They have been using GitHub for a long time (14 years or more), with thousands of repositories there. It's why Rust and Servo are on GitHub, for example.

Edit: See https://glandium.org/blog/?p=4346 for more thorough/accurate info.

I don't think that works, because the command substitution in "$(…).txt" runs immediately in the current shell.

Aside from that, find -exec doesn't use a shell to run its command, which means $(…) won't work without an explicit sh call.

I believe the right command in this style that will work is:

find /my/mp3dir -type f -iname '*.mp3' -exec sh -c \
  'test -f "${0%.mp3}.txt" && mp3splt -A "${0%.mp3}.txt" "$0"' \
  '{}' ';'

However, I would recommend the for f in *.mp3-style solution instead, as to me it's more readable. (The Bash/Zsh recursive glob (**) syntax can be used if subdirectories are involved.)