How do I...

Keyboard shortcuts inside applications

How do I set up keyboard short-cuts?

To set up global shortcuts (which work whatever you're doing) you need to have a ROX-Filer pinboard or panel active ROX-Session can set these up for you). Any item on a pinboard or panel can have a keyboard shortcut set for it by choosing 'Edit Item' from the popup menu.

You can also set keyboard shortcuts for use in filer windows (and some other applications) like this:

  • Open the menu.
  • Point at a menu item, but don't click on it.
  • Press the key.
  • Close the menu.

Keys are automatically saved when the filer quits.

The GTK developers have decided to disable this feature by default. To turn it on:

  • If you are running ROX-Session it will be on by default. It can use controlled using the Keyboard configuration applet.
  • If you are running GNOME, use gconf-editor to turn on the /desktop/gnome/interface/can_change_accels option.
  • If you are using some other XSettings manager, you will have to find how it lets you configure this (anyone know how to do this with xfce-settings-show?)
  • If you are not running an XSettings manager, you can instead add this line to your ~/.gtkrc-2.0 file:
    gtk-can-change-accels = 1

I use SuSE 9 and it still doesn't work!

You also need to create an empty file called ~/.no-qtrc-to-gtkrc-mapping, then log out and log back in again.

Stop the green error messages from appearing

I tried a KDE application and the screen filled with debug messages!

For some unknown reason, KDE defaults to debug-level logging. To stop it printing
all that stuff, run kdebugdialog and turn all the options off.

I get messages from other programs too

The messages are actually displayed by ROX-Session, but are sent by other applications. Since error messages mean that something has gone wrong, you should report a bug against the program producing them (NOT against ROX-Session!).

You can set how long the messages are displayed for from ROX-Session's Options box, and you can see a log of old messages there too. You can also see the log by right-clicking on the messages as they're shown, which is useful if you need more time to read them, or if you want to copy-and-paste into a bug report.

If you really need to disable messages (because some application is just too noisy), you can do this in its AppRun file:

exec some_app "$@" 2>&1

The extra 2>&1 at the end of the exec line causes errors to be treated as normal (non-error) output, so ROX-Session won't display them.

To hide messages from your window manager, create a script containing:

exec window_manager "$@" 2>&1

Then use the name of that script in the ROX-Session Session Settings box.
Note that we do not provide any way to supress all error messages from all applications (despite frequent requests). Ignoring errors is never the right thing to do, and providing this option to users would be irresponsible. Although you may think that the warnings you see are harmless, the same bug could be causing serious trouble to other users. The developers may spend weeks trying to track down the problem, when the message you saw would have located the problem instantly.