From ArchWiki
Jump to: navigation, search

"Keyboard Layout Handler" versus setxkbmap and xmodmap

Just to make a note of something I have been struggling with for quite some time: I was unable to get any setxkbmap command to work. Neither in the autostart, nor manually in a terminal window. Neither could I use xmodmap to do my tweak via xinitrc before I started lxde (that works for me with e.g. a barebones openbox, however), while it was possible to use xmodmap manually once LXDE was up and running.

Turns out that the Keyboard Layout Handler in the panel overrides at least the setxkbmap command with its own set of "-option"s. So if you use that: don't try the autostart way described here, but use the GUI option. Persilja (talk) 18:11, 22 August 2013 (UTC)

Fake transparency in lxterminal

Re:special:diff/528795/prev. I meant to say "when a compositing manager is not used."

When compositing manager is used, of course there is real transparency, in both gtk2 and gtk3 versions.

However, I don't want to run a compositing manager because I feel they are unnecessary and bloated. The "fake transparency" in lxterminal, at least when using the gtk2 version, works well for me. I don't find that it's buggy, I use it every day of course. Hopefully eventually the gtk3 version will support fake transparency, until then I think using the gtk2 version works best for me and may be what some other users desire as well.

Taifunbrowser (talk) 23:03, 4 July 2018 (UTC)

Now I added back the section with a bit different wording. --City-busz (talk) 00:43, 5 July 2018 (UTC)