Hackage :: [Package]

hdmenu: A small wrapper around dmenu

[ gpl, library, program, system ] [ Propose Tags ]

hdmenu is a small wrapper around dmenu that can 1. Display commands in order of usage and, optionally, apply a frequency decay every time an item is selected. 2. Specify extra files to consider, which will be opened by a program of your choice (e.g., xdg-open). 3. Open certain executables inside of your terminal.

[Skip to Readme]

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

  • No Candidates
Versions [RSS] 0.3.0
Change log CHANGELOG.md
Dependencies base (>=4.17.2 && <4.22), base-prelude (>=1.6.1 && <1.7), bytestring (>=0.11.5 && <0.13), bytestring-lexing (>=0.5.0 && <0.6), containers (>=0.6.7 && <0.8), directory (>=1.3.7 && <1.5), double-conversion (>=2.0.4 && <2.1), hdmenu, optparse-applicative (>=0.17.1 && <0.19), posix-paths (>=0.3.0 && <0.4), process (>=1.6.18 && <1.7), process-extras (>=0.7.4 && <0.8), text (>=2.0.2 && <2.2), tomland (>=1.3.3 && <1.4), unix (>=2.7.3 && <3), utf8-string (>=1.0.2 && <1.1) [details]
License GPL-3.0-only
Author Tony Zorman
Maintainer Tony Zorman <soliditsallgood@mailbox.org>
Category system
Home page https://github.com/slotThe/hmenu#readme
Bug tracker https://github.com/slotThe/hmenu/issues
Source repo head: git clone https://github.com/slotThe/hmenu
Uploaded by TonyZorman at 2024-05-23T19:24:13Z
Distributions
Executables hdmenu
Downloads 14 total (14 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs uploaded by user
Build status unknown [no reports yet]

Readme for hdmenu-0.3.0

[back to package description]

hdmenu

hdmenu is a small wrapper around dmenu—it can't do very much, though I guess that's the point. It might be most notable for being a discount yeganesh.

Features

  1. Display commands in order of usage and, optionally, apply a frequency decay every time an item is selected.
  2. Specify extra files to consider, which will be opened by a program of your choice (e.g., xdg-open).
  3. Open certain executables inside of your terminal.

Configuration

Hdmenu is configured using a TOML file inside the $XDG_CONFIG_HOME/hdmenu directory (probably ~/.config/hdmenu). See example.toml for an example configuration.

Note that, while having a config file is optional, the $XDG_CONFIG_HOME/hdmenu directory will be created in either case, in order to store the history file there.

Configuration option

The configuration file takes the following arguments:

  • open : A custom opening script (default: xdg-open).

  • files: Files one wishes to edit; they will be opened according to open. This can also take directories

    files = [ "~/.config/emacs/" ]

    in which case all files in that directory will be added to the list of files that hdmenu cares about. Directories can also be traversed recursively:

    # Files from `~/.config/emacs/' and all of its subdirectories.
files = [ "~/.config/emacs/" ]

  • executable: Custom dmenu executable (default: dmenu).

  • terminal: A terminal emulator (default: xterm).

  • tty-programs: A list of programs to be opened in the above terminal emulator. For example, specifying

    tty-programs = [ "htop" ]

    will effectively enable one to start htop directly from dmenu without having to open an extraneous terminal.

  • decay: A frequency decay; all non-selected items will be multiplied by this number (default: 1). A good value may be something like 0.997

Command line options

  • --histFile

    • Short: -f
    • Description: Path to the history file to use.

  • --files-only

    • Short: -o
    • Description: Whether to only show the user-specified files.

  • --decay

    • Short: -d
    • Description: A frequency decay; all non-selected items will be multiplied by this

All options after -- will be directly forwarded to dmenu, so you may specify options in the following way:

hdmenu -f /path/to/file -- -i -f -nb '#282A36' -nf '#BBBBBB' -sb '#8BE9FD' -sf '#000000' -fn 'Inconsolata Regular-10'

Installation

Stack

Build with stack build, then copy the executable to a convenient location (or just use stack install, to copy the executable to the local-bin-path).

Cabal

Build with cabal install.