Niceee! Github has brought in the command pallet. This is awesome. I think majority of GUI software need to implement command pallet hopefully with the same uniform keyboard shortcut.

Software categories who should consider this imho: are
- browsers (similar to what Vivaldi has done)
- text editors and IDEs (e.g Kate)
- photo editors (e.g Krita)
- video editors
- file browsers
- chat applications (e.g Element, @dino)
- music players (e.g @nuclear, Amarok, Cantata)
- PDF editors (e.g Okular)

I think @gitea and ultimately @codeberg can also plan bringing the command pallet feature which is very useful and handy. Perhaps it would also help with the server load as users don't load multiple pages to navigate but rather use the command pallet to jump to repos and issues with a very minimal Ajax requests to the server.

Wish I knew how I could help though.

Nice idea, feel free to fire a feature request at Codeberg or directly to the Gitea maintainers.

@codeberg @gitea

Surprisingly no one have created feature request for command pallet during the past two days (or at least I didn't find any). I created a feature request ironically on Github for having this feature on Gitea:

I tried to be comprehensive and add some examples, but still, I don't know how else I can help as I'm not a Go dev. So let me know what help might be needed and I'll be happy to help.

Someone still looking for a weekend project?
Implementing (maybe a proof of concept) of a command-pallet based quick navigation for #Gitea?


@Mehrad @codeberg it may exist under a different name such as “keyboard shortcuts”. As for being hosted on GitHub we have already migrated most of our repos to, and are actively working on the last one.

@gitea @codeberg

But there is a drastic huge difference between keyboard shortcuts and command pallet. Basically shortcuts is a limited set of functions and actions maps to a key binding that the user should remember be heart, where as command pallet is a fuzzy search box that can call actions, but it can also accept complex multi-step commands with some arguments and also can help in navigation. A command pallet is potentially an ad-hoc CLI interface inside a GUI.

@Mehrad @dino @nuclear
If such command input bars become more widespread, there should also be a way to access and trigger the search results (or actions) from outside the application.

This might allow integration into a system-wide command bar and could also provide an interface for automation.

Then again, I somehow get the nagging feeling that in some way the wheel is being reinvented, at least partially.

@floppy @Mehrad @dino
We've had an issue for this idea since forever:

I wanted to also expose this functionality via the local REST api that we already use for integrations (just like @floppy suggests)

@floppy The thing I loved most about OSX was the search part in help. When I didn't know where to find something, I just had to open the search under the help menu of any application and just start typing. And now in VScode (every few moon that I use it) I very often use their command pallet to again find something or do something quickly. Imho this should be some sort of feature that the Window Manager provides (as it does/did in OSX). If that happens there is no reinventing the wheel.

@floppy The most frustrating part of working with LibreOffice, Gimp and Inkscape is that I usually know what I want to do and I know the name (or I have few candidates in mind), but I cannot find the damn thing in the menus. I then have to try Searxing it or have to dive into the rabbit-hole of nested menus.

Inkscape v1.1 have solved this for good, but the rest are still a pain in every orifice imaginable.

Sign in to participate in the conversation

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.