.gitignorecommits | blame
LICENSEcommits | blame
Makefilecommits | blame
README.mdcommits | blame
Xexamplecommits | blame
mymenu.1commits | blame
mymenu.1.mdcommits | blame
mymenu.ccommits | blame
screen-alt.pngcommits | blame
screen.pngcommits | blame

# MyMenu

> A menu for Xorg, 'cause I was bored

![MyMenu works!](screen.png)

![MyMenu alternate layout](screen-alt.png)


## What?

This is a simple menu for Xorg, like `dmenu(1)`.

## Why?

This was the perfect excuse to learn how to use Xlib.

## How?

Check out the [manpage]( for further documentation. Check
out also the [template](Xexample) for the resources.


## Features

- two layout: `horizontal` (a là dmenu) and `vertical` (a là rofi);
- highly customizable (width, height, position on the screen, colors, borders, ...);
- transparency support
- support for both Xft and bitmap font

## Dependencies

 - Xlib
 - Xinerama *(optional)* for multi-monitor support
 - Xft *(optional)* for TrueType font support
 - pkg-config *(optional)* to generate `LIBS` and `CFLAGS`
 - mandoc *(optional)* to generate the
   [markdown version of the manpage](

## Build

As simple as `make` (or `make gnu` if you're using GNU libc). Keep in
mind that, by default, both Xft and Xinerama are enabled. So, you may
want to run:

  - `make no_xft` to build without xft support;
  - `make no_xinerama` to build without xinerama support;
  - `make no_xft_xinerama` to build without xinerama *and* no xft support.

Or you can update the first lines of the `Makefile` customizing
`OPTIONAL` and `CDEFS` to your needs.

#### ignore case completion / don't have `strcasestr(3)`

If you want to build without the ignore case completion or on your
platform `strcasestr(3)` isn't available, you have to update the
`Makefile` and remove `-DUSE_STRCASESTR`. A simple
``` shell
sed -i.orig 's/-DUSE_STRCASESTR//g' Makefile
should be enough.

## FAQ

 - Does not run / Hangs

   At the startup mymenu will read `stdin` for a list of item, only
   then it'll display a window. Are you sure that you're passing
   something on standard input?

 - Will feature $X be added?

   No. Or maybe yes. In fact, it depends. Open an issue and let's
   discuss. If it's something that's trivial to achieve in combo with
   other tool maybe is not the case to add it here.

 - Is feature $Y present? What $Z do? How to achieve $W?

   Everything is documented in the [man page]( To read
   it, simply execute `man -l mymenu.1` or `mandoc mymenu.1 | less`
   (depending on your system the `-l` option may not be present).


## Scripts

I'm using this script to launch MyMenu with custom item

``` shell

cat <<EOF | /bin/sh -c "$(mymenu "$@")"
sct 4500
connect ethernet
connect home
connect phone

You can generate a list of executables from `$PATH` like this:

``` shell

path=`echo $PATH | sed 's/:/ /g'`

    for i in $path; do
        ls -F $i | grep '.*\*$' | sed 's/\*//'
} | sort -f | /bin/sh -c "$(mymenu "$@")"

You can, for example, select a song to play from the current queue (in mpd), with

fmt="%position% %artist% - %title%"
if song=$(mpc playlist -f "$fmt" | mymenu -p "Song: " -A -d " "); then
    mpc play $(echo $song | sed "s/ .*$//")

Of course you can as well use the `dmenu_path` and `dmenu_run` scripts
that (usually) comes with `dmenu`.