Community-driven coverage of elementary OS — news, guides & forums
Dark abstract low-poly geometric landscape with layered triangular facets in deep navy, charcoal, and muted teal, illuminated by a soft electric-blue glow near the horizon

News roundups, tutorials, application guides, and forums — built by users, for users of the elegant Linux distribution.

elementary weekly
#20
Latest roundup · 18 Apr 2015
Freya Release
Final
Covered in weekly #19 & #20
Forum Topics
Active
Installation, customization & more

Customising keyboard shortcuts in elementary OS

elementary OS ships with a practical set of keyboard shortcuts, but the defaults are designed around a generic keyboard rather than the way every person works. Global bindings handle the desktop, window switching and the app grid, while individual applications may add their own accelerators. Learning where those layers meet makes customisation safer and prevents a new shortcut from breaking a familiar command.

The built-in Keyboard settings panel can change many default bindings without editing system databases. A thoughtful scheme can reduce mouse use, make the Australian keyboard layout less awkward and keep frequent actions consistent across apps. The important part is not collecting the largest possible list of combinations; it is choosing a few dependable shortcuts that remain useful after an update or a reinstall.

Keyboard hardware adds another variable. Most Australian users meet both Australian and United States layouts at school or work, and many compact laptops replace Alt or Caps Lock with smaller keys. On a full-size keyboard the Super key often carries a Windows logo, while GNOME still treats it as Super. Confirming the active layout and physical key positions prevents many apparently broken bindings.

Start with the built-in shortcut editor

Open Settings from the Super app grid, then select the Keyboard panel. In recent elementary OS releases, look for a Shortcuts tab or control near Layouts; earlier versions of the panel can look slightly different, so the in-panel search for “shortcut” is useful. From here you can view the active bindings, edit supported entries and return an individual command to its default value.

The list normally mixes desktop actions, such as opening the app grid or switching windows, with workspace commands. It also reveals which modifier is assigned to each action. Click an entry or its pencil icon to enter the capture mode, where the next combination is recorded as a new binding. This is the safest place to discover what is already reserved before making changes.

Not every visible shortcut belongs to elementary OS. A menu inside Files, Text Editor or a browser can define an app-level accelerator, and an application can capture a key while it has focus. When a binding works in one window but not elsewhere, record it as an application shortcut rather than immediately assuming the system-wide editor is at fault.

Change a binding without breaking the desktop

Choose the command, open its editor and press the desired key combination. Most interfaces ask for a final confirmation or automatically save the change after the keys are captured. A combination must include a non-modifier key, so a lone Super, Alt, Ctrl or Shift cannot become a useful binding. Escape usually cancels the capture without changing the old value.

For global actions, a Super-based combination is often easy to remember because it sits outside the crowded Ctrl shortcuts used for copying, pasting and text editing. Keep Alt for window and menu navigation, and reserve Ctrl plus another key for commands that are meaningful inside an application. Modifier combinations involving AltGr or a function key need testing on every keyboard used regularly.

Pay attention to conflict messages. If another command owns the combination, change the existing binding first or choose a different sequence. Conflicts can also be legitimate but limited in scope: Ctrl+W may close a browser tab while a text editor assigns it to Close, demonstrating that identical combinations can serve different applications. After saving, test the shortcut with the target app focused, at the desktop and on another workspace.

Match shortcuts to apps and packages

Some application accelerators are exposed only in the program’s own preferences. Menus often show a key beside Undo, Find, New Window or Preferences, and those labels identify the command that must be changed inside that application. The elementary OS editor controls supported system bindings; it cannot rewrite every menu belonging to GTK, Qt or Electron software.

A useful package management comparison shows that AppCenter, Snap and Flatpak deliver applications with different update and sandboxing arrangements. A shortcut that calls one packaged version may therefore fail after that package is refreshed, even though the application still appears in the app grid.

Custom command bindings should be conservative. Use the current desktop entry or a stable absolute command, quote any path containing spaces and avoid assumptions about the working directory. Shell-only syntax can behave differently when the desktop launches a command without a terminal. When a package update changes the application identifier, revisit the binding rather than adding several alternative launchers.

Handle Australian layouts and shared devices

Start by checking Settings, Keyboard, Layouts against the legends printed on the keycaps. The Australian layout places some punctuation and symbols differently from the United States layout and uses AltGr for several characters. A shortcut built around a punctuation key can appear correct on one layout and fail on another, while Super remains the logical key even when its cap shows a Windows logo.

Daily routines make these differences easy to notice. A commuter in Sydney may move from a shared office laptop to a full-size keyboard at home, while someone in Melbourne can spend the day on a compact keyboard and a train. Build a small reference for the bindings that differ by device, and test them on both an external keyboard and the laptop before relying on them.

A shared or community-managed computer needs a different boundary. A personal preference must not override an administrator’s access rules or a policy for assistive input. For such a device, ask the administrator for the device policy and any community support material that applies before replacing a system-wide binding.

Build a memorable shortcut scheme

A workable scheme has three layers: desktop shortcuts for movement and launching, application shortcuts for editing, and temporary combinations for occasional actions. Keep the first layer small, since it is available everywhere, and use the same pattern for similar jobs. A consistent prefix makes a shortcut easier to recall than a clever mnemonic that changes from app to app.

Start with the actions performed many times each day: opening the app grid, reaching the file manager, switching windows, taking a screenshot or opening a terminal. Select commands that are genuinely global, then reserve a second set for duplicate, close, search and navigation inside applications. Avoid shadowing standard editing keys, and do not assign a command merely because a free combination exists.

Ergonomics matter as much as availability. A shortcut that stretches across four modifiers may look efficient in a table but become tiring during repeated work. Choose one or two modifiers, use keys reachable from the home row, and check whether accessibility tools such as sticky keys or alternative input methods intercept them. A scheme is successful when it reduces effort without making accidental activation more likely.

Diagnose and repair shortcut problems

A shortcut that appears dead often has a mundane cause. The wrong input source may be active, the laptop’s function key may need a separate Fn press, or the focused application may be consuming the combination before the desktop sees it. Remote desktop clients can also reserve combinations locally. Check those conditions before changing the binding again.

For a deeper inspection, the commands gsettings list-recursively org.gnome.desktop.wm.keybindings and gsettings list-recursively org.gnome.settings-daemon.plugins.media-keys reveal relevant stored values in a terminal. The dconf Editor application can show the same settings graphically. Treat these tools as diagnostic views unless a built-in option is unavailable, because editing the wrong schema can produce two commands for one action.

Recovery should be narrow. Use the reset control for the affected entry in the Shortcuts panel, then sign out and back in if the change does not appear immediately. Avoid resetting an entire keybindings schema until individual entries have been checked, since a broad reset can remove several useful customisations at once. Reapply the remaining changes one at a time and retest them.

Purchasing equipment adds a local hardware consideration. Major Australian retailers still present Windows and macOS compatibility more prominently, so confirm that a keyboard has an AltGr key and the expected Australian legends before buying. Under the Australian Consumer Law, businesses must not make misleading representations about product compatibility, making it sensible to retain listings and warranty details. Privacy law also matters if a proposed global launcher records keystrokes or syncs clipboard history: organisations subject to the Privacy Act 1988 and the Australian Privacy Principles need appropriate safeguards for personal information.

Keep the setup portable and durable

Record the final scheme outside the machine as well as inside it. A short table with the action, key combination, application scope and original value makes recovery straightforward after a clean install. When using dconf directly, export only the relevant keybinding path rather than copying an entire home directory. Screenshots are useful for the graphical editor, but typed records are easier to restore and compare.

Keep portable rules in mind. Prefer Super, Ctrl, Alt and Shift over hardware-specific keys; document commands that depend on an application identifier; and check custom bindings after major system or application updates. If the same settings are managed across several computers, use a deliberate configuration process rather than assuming a copied home directory will carry every binding safely.

The durable lesson is simple: begin with the built-in editor, change one binding at a time, test it in the relevant application and at the desktop, and keep only the shortcuts that save time without surprising anyone.

Browse the News Archive
Latest Updates

From the elementary weekly series

Low-poly faceted abstract render in dark charcoal and electric blue tones, suggesting a news bulletin or announcement
elementary news

elementary weekly #20

The first week with the final Freya release — community reactions, tips, and early impressions gathered in one roundup.

Abstract low-poly geometric scene in midnight blue and soft cyan, conveying a live broadcast or event atmosphere
elementary news

elementary SPECIAL

A live Hangouts event with the elementary OS founders, held on 11 April 2015, discussing the Freya final release.

Low-poly faceted render in deep navy and muted teal with subtle amber highlights, suggesting a tutorial or guide
Tips and Tricks

Timeshift Guide

How to use Timeshift — the intuitive system restore utility for elementary OS — to recover from configuration mishaps.

Explore

Topics & Resources

Dive into guides, application recommendations, and community discussions covering every aspect of elementary OS.