Talk:Tutorials/ComposeKey

Jump to: navigation, search

Contents

Thread titleRepliesLast modified
Outdated info?1012:03, 22 April 2019

Outdated info?

Added a section for Plasma, with screenshot.

Should we be keeping information here from KDE 3.x?

13:42, 27 December 2018

The information about KDE3 can be removed. I'm not 100% sure but KDE4 information should also be removed, since KDE don't support KDE4 anymore. But for this I prefer a confirmation from an older admin ;)

There is also a small section about compose key in https://userbase.kde.org/System_Settings/Keyboard.

15:09, 27 December 2018

Ok. If that is the case, and it is deemed the KDE 3 and 4 information be removed, maybe redirect the remaining, so to remove redundancy.

15:23, 27 December 2018

I also found out the gtk section is outdated, look like it's working out of the box with firefox and gimp.

16:01, 27 December 2018

I would very much like to get rid of everything KDE4 specific. There are a few areas where it might be wise to retain some of the old information, though. There are still some applications that are not using Frameworks 5, which should probably still have a page. Also some "expert advice" that only apply to (some version of) KDE4 might still be useful. Basically anything that might still be useful to someone should be retained in some form; however I think it unlikely, that we are getting any new users of KDE4.

When it comes to whole pages I think it best to archive the pages rather than deleting them. Other KDE4 specific information could be moved to special pages, so that it is well separated from the regular info, and also easier to manage in the future.

10:12, 28 December 2018
 

It's not working for me in GTK Apps (GIMP, FF, TB), either out-of-the-box or by following the instructions on this page. The compose key just does nothing. It works fine in QT/KDE apps, eg Kate

Using a clean install of Kubuntu 19.04-beta (4 days until release).

  • Operating System: Kubuntu 19.04
  • KDE Plasma Version: 5.15.4
  • KDE Frameworks Version: 5.56.0
  • Qt Version: 5.12.2
  • Kernel Version: 5.0.0-11-generic


Tried this:

GTK_IM_MODULE=xim firefox

no difference (same for TB & GIMP)

this file does not exist in Kubuntu...

sudo cp /etc/X11/xinit/xinput.d/default /etc/X11/xinit/xinput.d/xim

So I created it..but no joy. Suspect that if I can't make the "launch from shell with ENV var" work, then any other method will also fail.

Has something changed? Or am I being dumb / missing something?

ENV seems to have correct values (even without my fiddling around with /etc/X11/xinit/xinput.d/xim


$ env | grep IM

  • GTK_IM_MODULE=xim
  • QT4_IM_MODULE=xim
  • IM_CONFIG_PHASE=2
  • CLUTTER_IM_MODULE=xim
  • QT_IM_MODULE=ibus


Why is QT_IM_MODULE=ibus ? Does that indicate a change, and means xim is not being triggered anymore?

11:23, 14 April 2019

Strange, it's working for me in Firefox and Kate in Arch Linux without configuring anything specific for gtk.

I will try to reproduce this in a VM with Kubuntu and will report back.

Carl

15:57, 14 April 2019
 
 
 
 
 

This page was last edited on 27 December 2018, at 13:42. Content is available under Creative Commons License SA 4.0 unless otherwise noted.