@@ -76,7 +76,7 @@ appropriate \--basedir, or more conveniently using the qbpm launch and qbpm choo
76
76
\# launch my profile called work and open internal.mycompany.com
77
77
qbpm launch work internal.mycompany.com
78
78
79
- \# launch a new profile called qb-dev, passing the flags to qutebrowser
79
+ \# launch a new profile called qb-dev, passing the debugging flags to qutebrowser
80
80
qbpm launch -n qb-dev --debug --json-logging
81
81
```
82
82
@@ -88,15 +88,22 @@ appropriate \--basedir, or more conveniently using the qbpm launch and qbpm choo
88
88
*-m, --menu* <menu>
89
89
Use _menu_ instead of the default menu program. This may be the name of a
90
90
program on $PATH or a path to a program, in which case it will be run in
91
- dmenu mode if qbpm knows about the program, or a full command line.
91
+ dmenu mode if qbpm knows about the program, or a full command line. On
92
+ MacOS the special value "applescript" is accepted. Run `qbpm choose --help`
93
+ for a list of known menu programs for your environment.
92
94
93
95
Examples:
94
96
95
97
```
96
- \# runs "echo {profiles} | /path/to/rofi -dmenu -no-custom -p qutebrowser"
97
- qbpm choose -m /path/to/rofi
98
+ qbpm choose --menu fzf
98
99
99
- qbpm choose -m "my-cool-menu --dmenu-mode --prompt qutebrowser"
100
+ qbpm choose --menu "./build/my-cool-menu --dmenu-mode --prompt qutebrowser"
101
+
102
+ \# qbpm knows about fuzzel so it can automatically invoke it as "~/.local/bin/fuzzel --dmenu"
103
+ qbpm choose --menu ~/.local/bin/fuzzel
104
+
105
+ \# if more than one word is provided it will be invoked as is, so `--dmenu` must be included
106
+ qbpm choose --menu 'fuzzel --dmenu --width 100'
100
107
```
101
108
102
109
* from-session* [ options] <session > [ <name >]
0 commit comments