Our great sponsors
-
supercollider
An audio server, programming language, and IDE for sound synthesis and algorithmic composition.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
As for items not appearing in this list this may be due to various reasons. Note in dmenu_path how the list of executables is cached. This cache should normally update automatically when you run the script, but if it does not then you can try removing the cache file (will be ~/.cache/dmenu_run if you do not have XDG_CACHE_HOME set). The second thing to note is that this looks for executable files in the directories denoted by the $PATH environment variable. This is running under a sh(ell) and the PATH will not necessarily be the same as what you may have set in your .bashrc as bash is a different shell. In this context all the options presented by dmenu will be the name of the executable file, which means that you have to know the name of the executable you are after (e.g. scide rather than "SuperCollider IDE"). This may take a bit to get used to. And in that context again it may not appear in the list because you assumed that it would list "SuperCollider IDE" as an option. If you look at desktop environments the way they present programs on the desktop or via menus is that they require .desktop files to be present for GUI applications. E.g. this is the .desktop file for SuperCollider IDE: https://github.com/supercollider/supercollider/blob/develop/editors/sc-ide/SuperColliderIDE.desktop