document updated 11 years ago, on May 26, 2012
- INCREASE THE FONT SIZE
- write the separate scripts that are mentioned below in section headers
- change from pydmenu.py to dmenu_freq, so that we have a lot more control of what goes in/out of dmenu
- change my ~/.dmenu_run script to use 'compgen -c' instead of 'dmenu_path' to generate the list-of-lines
- this allows aliases to be included automatically
- this requires pydmenu.py => dmenu_freq
- add '-l 10' to the dmenu call
- this requires pydmenu.py => dmenu_freq
==== dmenu_freq ====
Usage:
- pipe in a list-of-lines
- it outputs a list-of-lines
- at the command line, it takes one parameter: a UID that indicates which "set" the
frequency data should be recorded under
a perl rewrite of yeganesh / pydmenu.py
additional features:
- make sure the config file is a text file with ONE TEXT LINE per entry
- guarantee that, if the user deletes a line, that the config file will be okay
- this makes it somewhat easy to delete an entry
==== dmenu_run_auto ====
Usage:
- Pipe the output of 'dmenu' to this (the chosen-item)
- It outputs the chosen-item. (possibly modified)
It determines if the chosen command should be run within a terminal, or if it's a GUI program.
It also determines it if should be run under sudo/gksudo or not.
If it should be run within a terminal, it modifies the command to be wrapped in a
terminal-launch call.
If GUI, it passes the command through unmodified.
This needs a config file of its own, so it can decide which goes where. See also:
https://bbs.archlinux.org/viewtopic.php?pid=1046547#p1046547
https://bbs.archlinux.org/viewtopic.php?pid=1088164#p1088164
Things like 'shutdown -h now' should be run via gksudo.