#StackBounty: #nvidia #xorg #xinerama Why won't my saved Nvidia X settings rotate my screen?

Bounty: 100

I have a dual monitor setup and I rotate one of my screens to the left. It is currently working as expected, and is a simple configuration.

enter image description here

The saved /etc/X11/xorg.conf looks like:

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 440.82


Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "type1"
    Load           "freetype"
    Load           "glx"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Philips PHL 241B8Q"
    HorizSync       85.0 - 85.0
    VertRefresh     48.0 - 76.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1060 3GB"
EndSection

Section "Screen"

# Removed Option "nvidiaXineramaInfoOrder" "DFP-5"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-3"
# Removed Option "metamodes" "DP-2: nvidia-auto-select +1080+420 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-0: nvidia-auto-select +0+0 {rotation=left, ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-5"
    Option         "metamodes" "DP-0: nvidia-auto-select +0+0 {rotation=left, ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-2: nvidia-auto-select +1080+420 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Now when I turn the screens off, things get Ubuntu-y. When I turn them back on, the rotate left setting will be unapplied, and the screens will sometimes be in reversed order, i.e., adjusting settings for the screen on the left will change settings for the screen on the right, and the right screen will need to be dragged over so the screens swap places and then apply the rotate setting.

enter image description here

It’s not the end of the world, but every time I turn my screens on I have to play this little guessing game with the Nvidia UI – rotate the screen, apply, oops that was one of Ubuntu’s trick cases where I need to move the right screen over to be the left screen, drag right screen over to left, rotate left screen, save, finally working – all because the saved Xorg config doesn’t load the config like it’s meant to.

Been a Ubuntu desktop user for 5 years now but this stuff is honestly just embarrassing, the need to debug something as simple as a monitor configuration.


Get this bounty!!!

#StackBounty: #nvidia #xorg #xinerama Why won't my saved Nvidia X settings rotate my screen?

Bounty: 100

I have a dual monitor setup and I rotate one of my screens to the left. It is currently working as expected, and is a simple configuration.

enter image description here

The saved /etc/X11/xorg.conf looks like:

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 440.82


Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "type1"
    Load           "freetype"
    Load           "glx"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Philips PHL 241B8Q"
    HorizSync       85.0 - 85.0
    VertRefresh     48.0 - 76.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1060 3GB"
EndSection

Section "Screen"

# Removed Option "nvidiaXineramaInfoOrder" "DFP-5"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-3"
# Removed Option "metamodes" "DP-2: nvidia-auto-select +1080+420 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-0: nvidia-auto-select +0+0 {rotation=left, ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-5"
    Option         "metamodes" "DP-0: nvidia-auto-select +0+0 {rotation=left, ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-2: nvidia-auto-select +1080+420 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Now when I turn the screens off, things get Ubuntu-y. When I turn them back on, the rotate left setting will be unapplied, and the screens will sometimes be in reversed order, i.e., adjusting settings for the screen on the left will change settings for the screen on the right, and the right screen will need to be dragged over so the screens swap places and then apply the rotate setting.

enter image description here

It’s not the end of the world, but every time I turn my screens on I have to play this little guessing game with the Nvidia UI – rotate the screen, apply, oops that was one of Ubuntu’s trick cases where I need to move the right screen over to be the left screen, drag right screen over to left, rotate left screen, save, finally working – all because the saved Xorg config doesn’t load the config like it’s meant to.

Been a Ubuntu desktop user for 5 years now but this stuff is honestly just embarrassing, the need to debug something as simple as a monitor configuration.


Get this bounty!!!

#StackBounty: #nvidia #xorg #xinerama Why won't my saved Nvidia X settings rotate my screen?

Bounty: 100

I have a dual monitor setup and I rotate one of my screens to the left. It is currently working as expected, and is a simple configuration.

enter image description here

The saved /etc/X11/xorg.conf looks like:

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 440.82


Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "type1"
    Load           "freetype"
    Load           "glx"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Philips PHL 241B8Q"
    HorizSync       85.0 - 85.0
    VertRefresh     48.0 - 76.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1060 3GB"
EndSection

Section "Screen"

# Removed Option "nvidiaXineramaInfoOrder" "DFP-5"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-3"
# Removed Option "metamodes" "DP-2: nvidia-auto-select +1080+420 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-0: nvidia-auto-select +0+0 {rotation=left, ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-5"
    Option         "metamodes" "DP-0: nvidia-auto-select +0+0 {rotation=left, ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-2: nvidia-auto-select +1080+420 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Now when I turn the screens off, things get Ubuntu-y. When I turn them back on, the rotate left setting will be unapplied, and the screens will sometimes be in reversed order, i.e., adjusting settings for the screen on the left will change settings for the screen on the right, and the right screen will need to be dragged over so the screens swap places and then apply the rotate setting.

enter image description here

It’s not the end of the world, but every time I turn my screens on I have to play this little guessing game with the Nvidia UI – rotate the screen, apply, oops that was one of Ubuntu’s trick cases where I need to move the right screen over to be the left screen, drag right screen over to left, rotate left screen, save, finally working – all because the saved Xorg config doesn’t load the config like it’s meant to.

Been a Ubuntu desktop user for 5 years now but this stuff is honestly just embarrassing, the need to debug something as simple as a monitor configuration.


Get this bounty!!!

#StackBounty: #nvidia #xorg #xinerama Why won't my saved Nvidia X settings rotate my screen?

Bounty: 100

I have a dual monitor setup and I rotate one of my screens to the left. It is currently working as expected, and is a simple configuration.

enter image description here

The saved /etc/X11/xorg.conf looks like:

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 440.82


Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "type1"
    Load           "freetype"
    Load           "glx"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Philips PHL 241B8Q"
    HorizSync       85.0 - 85.0
    VertRefresh     48.0 - 76.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1060 3GB"
EndSection

Section "Screen"

# Removed Option "nvidiaXineramaInfoOrder" "DFP-5"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-3"
# Removed Option "metamodes" "DP-2: nvidia-auto-select +1080+420 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-0: nvidia-auto-select +0+0 {rotation=left, ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-5"
    Option         "metamodes" "DP-0: nvidia-auto-select +0+0 {rotation=left, ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-2: nvidia-auto-select +1080+420 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Now when I turn the screens off, things get Ubuntu-y. When I turn them back on, the rotate left setting will be unapplied, and the screens will sometimes be in reversed order, i.e., adjusting settings for the screen on the left will change settings for the screen on the right, and the right screen will need to be dragged over so the screens swap places and then apply the rotate setting.

enter image description here

It’s not the end of the world, but every time I turn my screens on I have to play this little guessing game with the Nvidia UI – rotate the screen, apply, oops that was one of Ubuntu’s trick cases where I need to move the right screen over to be the left screen, drag right screen over to left, rotate left screen, save, finally working – all because the saved Xorg config doesn’t load the config like it’s meant to.

Been a Ubuntu desktop user for 5 years now but this stuff is honestly just embarrassing, the need to debug something as simple as a monitor configuration.


Get this bounty!!!

#StackBounty: #nvidia #xorg #xinerama Why won't my saved Nvidia X settings rotate my screen?

Bounty: 100

I have a dual monitor setup and I rotate one of my screens to the left. It is currently working as expected, and is a simple configuration.

enter image description here

The saved /etc/X11/xorg.conf looks like:

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 440.82


Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "type1"
    Load           "freetype"
    Load           "glx"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Philips PHL 241B8Q"
    HorizSync       85.0 - 85.0
    VertRefresh     48.0 - 76.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1060 3GB"
EndSection

Section "Screen"

# Removed Option "nvidiaXineramaInfoOrder" "DFP-5"
# Removed Option "nvidiaXineramaInfoOrder" "DFP-3"
# Removed Option "metamodes" "DP-2: nvidia-auto-select +1080+420 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-0: nvidia-auto-select +0+0 {rotation=left, ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-5"
    Option         "metamodes" "DP-0: nvidia-auto-select +0+0 {rotation=left, ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-2: nvidia-auto-select +1080+420 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Now when I turn the screens off, things get Ubuntu-y. When I turn them back on, the rotate left setting will be unapplied, and the screens will sometimes be in reversed order, i.e., adjusting settings for the screen on the left will change settings for the screen on the right, and the right screen will need to be dragged over so the screens swap places and then apply the rotate setting.

enter image description here

It’s not the end of the world, but every time I turn my screens on I have to play this little guessing game with the Nvidia UI – rotate the screen, apply, oops that was one of Ubuntu’s trick cases where I need to move the right screen over to be the left screen, drag right screen over to left, rotate left screen, save, finally working – all because the saved Xorg config doesn’t load the config like it’s meant to.

Been a Ubuntu desktop user for 5 years now but this stuff is honestly just embarrassing, the need to debug something as simple as a monitor configuration.


Get this bounty!!!

#StackBounty: #x11 #xorg #keyboard-shortcuts #keyboard #i18n Why can't I type a g̃?

Bounty: 100

My language, Guarani, uses G̃/g̃ to denote the nasalized velar approximant. I thought I’d be able to type it by combining a dead tilde with g, but this does not work. Why doesn’t it, and how can I fix it?

My main suspicion is that this has to do with the fact that there is no separate unicode character for g̃, just g with the combining tilde. I can type ỹ and ṽ just fine, but not j̃, r̃, m̃, which seems like good evidence that therein lies the problem.

So one way I could get around this would be to map a key to 0x1000303 (which is U+0303, or ◌̃ ), the combining tilde, instead of to dead_tilde. However, this creates several problems:

  • If I switch to using the combining tilde in all cases:
    • I end up typing e.g. n + ◌̃ in many cases where the single character ñ is expected, and they have different results. For example, I’ve noticed that certain websites won’t display the same search results if I type one vs. the other (obviously that’s on them, but I want a keyboard layout that works with the world as it exists now).
    • It’s annoying that I have to backspace twice to delete characters with the combining tilde, which I can accept if it’s only for the g̃, but it’s a little much with every nasalized character.
  • If I add both, which is what I’m currently doing, this becomes really hard for usability, because:
    • I have to think in each case about which key to use, when my brain thinks of them as the same
    • The mechanics of typing the two are different, since dead_tilde is pressed before a character, whereas ◌̃ goes after. My poor little brain will never get used to that.

It seems like in the ideal scenario I’d have X notice that dead_tilde + g doesn’t work and just process it as if I’m typing g + ◌̃, and enter the two characters for me together, as it does for ñ, ã, ẽ, ĩ, õ, ũ, ỹ, etc.

It’s worth noting that it’s not possible to get around this by adding the g̃ directly to my keyboard layout, as xkb doesn’t seem to support mapping a key to a combined unicode glyph (though see the answer to Custom xkb layout in which one key creates two unicode code points for a hacky workaround). If I could fix that, I suppose this would be much less of a problem.

I’m running Ubuntu 18.04, not sure what other background info would be helpful, but I assume this is a problem for anyone running X.

Edit 1: Editing Compose mappings doesn’t work

Another thing I’ve tried, which also did not work, is editing the Compose mappings to add a composed g̃. I wrote an .XCompose file as follows:

include "%L"

<dead_tilde> <g> : "g̃" gtilde
<dead_tilde> <G> : "G̃" Gtilde

But this also did not work, I assume for the same reason above: X expects a single character, and g̃ is technically two. Incidentally, I noticed a number of mappings shipped in my locale’s default Compose file also don’t work, presumably for the same reason. The following mappings for en_US.UTF-8, and perhaps many more, actually do nothing:

<dead_acute> <dead_tilde> <a>       : "ã́"   # LATIN SMALL LETTER A WITH TILDE AND ACUTE
<dead_grave> <dead_tilde> <a>       : "ã̀"   # LATIN SMALL LETTER A WITH TILDE AND GRAVE
<dead_acute> <dead_tilde> <A>       : "Ã́"   # LATIN CAPITAL LETTER A WITH TILDE AND ACUTE
<dead_grave> <dead_tilde> <A>       : "Ã̀"   # LATIN CAPITAL LETTER A WITH TILDE AND GRAVE
<dead_acute> <dead_tilde> <e>       : "ẽ́"   # LATIN SMALL LETTER E WITH TILDE AND ACUTE
<dead_grave> <dead_tilde> <e>       : "ẽ̀"   # LATIN SMALL LETTER E WITH TILDE AND GRAVE
<dead_acute> <dead_tilde> <E>       : "Ẽ́"   # LATIN CAPITAL LETTER E WITH TILDE AND ACUTE
<dead_grave> <dead_tilde> <E>       : "Ẽ̀"   # LATIN CAPITAL LETTER E WITH TILDE AND GRAVE
<dead_acute> <dead_tilde> <i>       : "ĩ́"   # LATIN SMALL LETTER I WITH TILDE AND ACUTE
<dead_grave> <dead_tilde> <i>       : "ĩ̀"   # LATIN SMALL LETTER I WITH TILDE AND GRAVE
<dead_acute> <dead_tilde> <I>       : "Ĩ́"   # LATIN CAPITAL LETTER I WITH TILDE AND ACUTE
<dead_grave> <dead_tilde> <I>       : "Ĩ̀"   # LATIN CAPITAL LETTER I WITH TILDE AND GRAVE
<dead_grave> <dead_tilde> <o>       : "õ̀"   # LATIN SMALL LETTER O WITH TILDE AND GRAVE
<dead_grave> <dead_tilde> <O>       : "Õ̀"   # LATIN CAPITAL LETTER O WITH TILDE AND GRAVE
<dead_grave> <dead_tilde> <u>       : "ũ̀"   # LATIN SMALL LETTER U WITH TILDE AND GRAVE
<dead_grave> <dead_tilde> <U>       : "Ũ̀"   # LATIN CAPITAL LETTER U WITH TILDE AND GRAVE
<dead_grave> <m>                    : "m̀"   # LATIN SMALL LETTER M WITH GRAVE
<dead_grave> <M>                    : "M̀"   # LATIN CAPITAL LETTER M WITH GRAVE

As a matter of opinion, I do not think this is what we should fix: adding an extra line to Compose files for every possible diacritic just seems wasteful, and is not taking advantage of the simplicity of the nice combining diacritics Unicode wants us to use.


Get this bounty!!!

#StackBounty: #xorg Why can't I type a g̃?

Bounty: 100

My language, Guarani, uses G̃/g̃ to denote the nasalized velar approximant. I thought I’d be able to type it by combining a dead tilde with g, but this does not work. Why doesn’t it, and how can I fix it?

My main suspicion is that this has to do with the fact that there is no separate unicode character for g̃, just g with the combining tilde. I can type ỹ and ṽ just fine, but not j̃, r̃, m̃, which seems like good evidence that therein lies the problem.

So one way I could get around this would be to map a key to 0x1000303 (which is U+0303, or ◌̃ ), the combining tilde, instead of to dead_tilde. However, this creates several problems:

  • If I switch to using the combining tilde in all cases:
    • I end up typing e.g. n + ◌̃ in many cases where the single character ñ is expected, and they have different results. For example, I’ve noticed that certain websites won’t display the same search results if I type one vs. the other (obviously that’s on them, but I want a keyboard layout that works with the world as it exists now).
    • It’s annoying that I have to backspace twice to delete characters with the combining tilde, which I can accept if it’s only for the g̃, but it’s a little much with every nasalized character.
  • If I add both, which is what I’m currently doing, this becomes really hard for usability, because:
    • I have to think in each case about which key to use, when my brain thinks of them as the same
    • The mechanics of typing the two are different, since dead_tilde is pressed before a character, whereas ◌̃ goes after. My poor little brain will never get used to that.

It seems like in the ideal scenario I’d have X notice that dead_tilde + g doesn’t work and just process it as if I’m typing g + ◌̃, and enter the two characters for me together, as it does for ñ, ã, ẽ, ĩ, õ, ũ, ỹ, etc.

It’s worth noting that it’s not possible to get around this by adding the g̃ directly to my keyboard layout, as xkb doesn’t seem to support mapping a key to a combined unicode glyph (though see the answer to Custom xkb layout in which one key creates two unicode code points for a hacky workaround). If I could fix that, I suppose this would be much less of a problem.

I’m running Ubuntu 18.04, not sure what other background info would be helpful, but I assume this is a problem for anyone running X.


Get this bounty!!!