An interactive Linux terminal app can appear in your application launcher and dock through a user-level .desktop entry. Set Exec= to the app’s executable, use Terminal=true for a terminal user interface (TUI), then open the new launcher entry and pin it to the dock.
A TUI stays open for interaction, unlike a one-shot command-line interface (CLI) command that prints output and exits. The steps below use Superfile as an example. How-To Geek’s walkthrough stores its entry at ~/.local/share/applications/superfile.desktop and uses the command spf.
Guide sections
- What you need
- What Exec= , Path= and Terminal= control
- Create a .desktop entry for Superfile
- If the shortcut does not launch the app
- If a command exits immediately
What you need
Have the terminal app installed, and know how to locate its executable. An icon is optional; if you add one, use an icon name or a path to an icon file that exists on your system.
What Exec=, Path= and Terminal= control
These three fields handle different launch details. In particular, Path= is not the same as the shell’s $PATH variable.
| Field | What it controls | When to use it |
Exec= | The command to run. A full executable path can be used, or a bare command name can be searched for in the desktop environment’s $PATH. | Set it to the installed app’s executable or a command the desktop environment can find. |
Path= | The application’s working directory. | Add it if the app needs to start in a particular folder. |
Terminal= | Whether the program runs in a terminal window. | Set Terminal=true for an interactive TUI. |
Create a .desktop entry for Superfile
- Find the executable. Run
which spfin a terminal and use the path it returns. Ifspfis available in the desktop environment’s$PATH, you can useExec=spfinstead. - Create the user applications directory. Run
mkdir -p ~/.local/share/applicationsif the directory does not already exist. - Create the entry file. Make
~/.local/share/applications/superfile.desktopin a text editor. For an Application entry, the desktop-entry standard requiresTypeandName. - Add the launch settings. Replace the executable and icon placeholders with paths that work on your system. Keep
Path=commented out unless Superfile needs a particular working directory.
[Desktop Entry]
Type=Application
Name=Superfile
Exec=/absolute/path/to/spf
Icon=/absolute/path/to/superfile.svg
Terminal=true
# Optional, only if the app needs a particular working directory:
# Path=/absolute/path/to/application-folder
- Save the file. Check that its name ends in
.desktopand that the paths you entered point to the executable and, if used, the icon. - Find and pin the launcher. Open your desktop’s application launcher and search for Superfile. Once it appears, use your desktop environment’s usual option to add it to the dock.
The Superfile walkthrough uses this user-level entry to make the app available from the launcher. A desktop environment may need a logout or restart before it displays a newly created entry.
If the shortcut does not launch the app
First check Exec=. If it contains a bare command such as spf, the desktop environment must be able to find that command through its $PATH; otherwise, use the correct full executable path. Path= addresses a different problem: it sets the working directory in which the application starts.
One Linux Mint user reported that extracted ZIP applications worked from their own folders but failed from shortcuts, and that adding Path= fixed that case. For your entry, set Path= only if the app depends on a particular working directory.
If a command exits immediately
A one-shot CLI command may close its terminal window after finishing, which leaves little time to read its output. Professor Gerry Jenkins’s English-language tutorial demonstrates a shell-script wrapper that runs sleep after a quick-exit command to keep the output visible. The tutorial shows this approach in Linux Mint with Cinnamon.
For a new launcher entry that does not appear, a logout or restart may prompt the desktop environment to display it.