Make US International keyboard not put accents in all characters

I have Ubuntu 19.04 and I’m using the English US International keyboard layout because I want to use accented letters like á, ö, ã, etc. Everything works well, but maybe a little too well.

When I type ' + a, I get the character á, which is the expected behaviour. But when I type ' + s or ' + m then I get ś and ḿ respectively and I don’t want these characters.

If I type ' + s then I expect the layout to output 's instead of ś, or if I type ' + m then I expect the layout to output 'm instead of ḿ.

Before somebody says that I’m asking for something crazy because I want the keyboard layout to selectively put accents in some letters, but ignores the accent on other letters, I also use US International keyboard layout on macOS and on Windows computers and they both behave in the way that I expect: ' + a outputs á but ' + s outputs 's instead of ś.

Is it possible to have the same behaviour on Linux?

How can I add a new character to an existing keyboard?

I currently have the Greek (Polytonic) keyboard layout installed, and it works wonderfully for typing Ancient Greek.

However, I sometimes find myself needing to type the obscure letter digamma (capital Ϝ, lowercase ϝ), which isn’t available on this keyboard. Ideally I’d move the final sigma to the Q key, and put digamma on the W.

Is there an easy way to accomplish this? I found this page, but it warns me that it’s not updated for current versions of Ubuntu. Moreover, digamma is too obscure to be given a name in /usr/include/X11/keysymdef.h (though it does have suitable codepoints in Unicode), and I’m not sure what I’d have to recompile if I edited that file.

Keyboard shortcut to kill uWSGI process in mac terminal

WSGI app 0 (mountpoint='') ready in 5 seconds on interpreter 0x56549c79e7d0 pid: 12 (default app) uWSGI running as root, you can use --uid/--gid/--chroot options *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***  *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 12) spawned uWSGI worker 1 (pid: 20, cores: 1) 

The above is the output on my terminal after the docker run command to run a flask API. I can open another terminal and use docker exec command to test the endpoints. But, how can I kill the process running in the terminal of uWSGI process? Ctrl+Z, Ctrl+Q, Ctrl+X, Ctrl+C, Cmd+Q, Cmd+X, Cmd+Q, Cmd+X doesn’t work.

Also, please share if I am making any naive mistake here in the process?

Customization of LiveCDs Wallpaper, Keyboard Layout, Network adapter drivers and fix screen resolution

I followed instructions of https://help.ubuntu.com/community/LiveCDCustomization to customize my first LiveCD based on ubuntu-18.04.2-desktop-amd64.iso (note that all URI references point to chapters of that tutorial). After testing the result, I found some things where my customization seems not to have worked:

  1. Change the desktop background to custom PNG: Eventhough I added my wallpaper to /usr/share/backgrounds/ and modified /usr/share/gnome-background-properties/ubuntu-wallpapers.xml to point to my wallpaper instead of warty-final-ubuntu.png, the wallpaper is still the warty-final-ubuntu.png. The instructions say that I should modify some more files (see here) but I could not find those.

  2. Change the keyboard layout to QWERTZ: In the instructions there was a section about localization (see here). I couldn’t find /usr/lib/ubiquity/ubiquity/misc.py (probably since I uninstalled ubiquity before) to customize the layout.
    Am I required to have ubiquity installed in order to preset the keyboard layout? I uninstalled it since I plan to use the created LiveCD only as boot medium and not for installing Ubuntu to any computer.
    Furthermore, I did not follow the instructions regarding UEFI boot since I already failed executing the first command sed -i ‘6i loadfont /boot/grub/fonts/unicode.pf2’ boot/grub/grub.cfg .
    Am I required to execute the script to make my LiveCD work properly? What exactly am I customizing here?

  3. Inappropriate screen size: When testing the created ISO with VirtualBox, only a small 800×600 screen is displayed. When starting via the most recent Ubuntu LTS LiveCD, I do not encounter this fixed resolution.
    Is this also related to the CD customization and how can I investigate where this issue comes from?

  4. I skipped the complete Advanced Customization step. This step is not required at all if I don’t want to change anything here, right?

  5. Cleanup process: In the cleanup section, the manual says, after installing software, I should execute: rm /var/lib/dbus/machine-id and rm /sbin/initctl followed by dpkg-divert –rename –remove /sbin/initctl .
    Do I have to run these commands only if I installed new software or also when doing an apt upgrade (this may also install new packages, right?)?

  6. Find, install and test specific network drivers: Since my host system is not an Ubuntu OS, I did the customization in a VirtualBox Ubuntu Guest system. I know from the past, that the network adapter of my computer may not be recognized when booting the physical machine with an Ubuntu LiveCD.
    I’m just wondering how I can find out whether this problem is still present without burning the CD.
    Is it possible from VirtualBox, to delegate the network resource as-is to the guest system for testing whether I need additional drivers?
    And how can I find out which drivers I may need to install?
    As soon as I know what to install, can I just run apt install in the chroot environment to install the drivers as done in the APT section of the tutorial see here?

Since I’m not that familiar with Ubuntu yet, I would appreciate if your answers contain the instructions what I should to as well as a rough explanation what the instructions are for.

Thanks for your help!

Where should keyboard focus go when a ‘load more’ content button is clicked

Where should keyboard focus go when a ‘load more’ button is clicked? On websites showing this functionality; either focus is moved to the top of the page when the button is clicked, or focus moves beyond the new content.

I find these methods problematic because how do keyboard users, and assistive technology users know where the new content is started—and easily move to this point.

I am looking for a solution, and although I can think of a couple of ways to address this, I am unsure of the best approach from an accessibility perspective.

  1. Focus is moved to the start of the new content. This could be achieved using a tabindex-1 and scripting to set focus.
  2. New content loads after the ‘load more’ the button remains in position and focus remains on the button. At the end of the new content a new ‘load more’ button appears.

I’m looking for best practice functionality that is also accessible

Sites already checked for a ‘Load more’ content button functionality

  1. Show More Button https://amp.dev/documentation/examples/interactivity-dynamic-content/show_more_button/
  2. Adding a Load More Button to your Content https://www.solodev.com/blog/web-design/adding-a-load-more-button-to-your-content.stml
  3. How to add load more button for a HTML/CSS page?
    https://stackoverflow.com/questions/8352372/how-to-add-load-more-button-for-a-html-css-page

How to implement a custom dead-key based keyboard layout?

I’m a workman user, and I’ve really grown to like the dead-key variant on osx.

The idea of using ‘dead’ keys is based on assumption that pressing 2 easy keys is better than pressing 1 hard key. So to make it easier to type (programming) characters/symbols, we’re going to press an easily reachable key (which will NOT output any character), release it and then press another easily reachable key to produce, say, @ character.

In this layout the COMMA key is a dead key, pressing it will cause keyboard enter a state in which a single stroke of other keys will output a different character than normal state. After that single stroke, the keyboard returns to its normal state.

For example, you’d press COMMA to enter the special state. Now if you strike the A key the output will be a forward slash “/”. To see how to create other characters, refer to following images for more info.

To produce the COMMA character itself, just hit SPACE after entering ‘dead’ state.

I’d like to achieve this functionality on Lubuntu too, but I don’t even know where to start… or if something like this is even possible. Could you please give me some pointers?