super-productivity/docs/wiki/4.-Reference.md
Johannes Millan 73c1848ba9 fix(docs): resolve markdown linting errors in all wiki files
- Add top-level headings to all wiki files (MD041)
- Fix heading spacing and blank line issues (MD022, MD012)
- Convert HTML badges to markdown format (MD033)
- Add alt text to images (MD045)
- Fix list indentation and numbering (MD005, MD029, MD032)
- Remove trailing punctuation from headings (MD026)
- Convert emphasis to proper headings (MD036)
- Fix heading level increments (MD001)
- Add trailing newlines to all files (MD047)

This ensures the wiki-sync.yml GitHub Action will pass linting.
All changes maintain the same visual appearance and functionality.

Fixes the lint failures reported in GitHub Action run #21212863659
2026-01-21 18:03:05 +01:00

1.9 KiB
Executable file

Reference

Settings and Preferences

Keyboard-Shortcuts

  • Shift+P: Open create project dialog
  • Shift+A: Open add task bar
  • Enter: Edit currently focussed task title
  • Arrow keys: Navigate around task list
  • D: Mark currently focused task as done
  • A: Add subtask to currently focused task
  • Y: Toggle tracking time to currently focused task
  • S: Open schedule dialog for currently focused task
  • Backspace: Delete currently focused task
  • ArrowRight: Open additional info panel for currently focused task
  • Ctrl+Shift+ArrowUp: Move currently focused task up in list
  • Ctrl+Shift+ArrowDown: Move currently focused task down in list

Short-Syntax

Can be used when adding a task. (Each of these can be disabled in settings->short syntax)

  • # <tag-name>: add a tag to the task

    ("task-description #tag1")

  • <number>m or <number>h: set time-estimate for the task

    ("task-description 10m" or "task-description 5h")

  • @<time>: add due time to the task

    ("task-description @fri 10pm")

  • + <project-name>: add the task to an existing project

    ("task-description +Important Project")

  • Ctr + 2: toggle between moving the new task to the bottom and top of the list

JSON-Models

Wayland-Compatibility

If you're experiencing issues running Super Productivity on Wayland (such as rendering problems, VSync errors, or GLib-GObject warnings), you can force the application to use X11 mode by starting it with the --force-x11 parameter:

superproductivity --force-x11

This will automatically apply compatibility fixes including:

  • Forcing the Ozone platform to use X11 instead of Wayland
  • Disabling GPU VSync to prevent GetVSyncParametersIfAvailable() errors
  • Setting the appropriate environment variables for X11 compatibility

The application will automatically detect Wayland sessions and apply these fixes, but you can use this flag if automatic detection doesn't work properly.