Re: [PATCH 3/6] Disable sfdump if there is no xrandr support.

> No idea whether how stable would be the mapping between Xrandr ids and
> ratpoison ids, though, as we don't control the former.  There's not much
> choice though, but 1. you already have implemented a screen_sort
> function, and 2. this sounds better than forcing the user to deal with
> numbers like 42 and 66, especially for 'sselect'. :)

I could use numset (fron number.c), to affect an id to each screen.
The id would be affected at ratpoison start, once screen are detected
and sorted.

Then, if a screen is removed, its numset is released. On screen plugging, a
new numset is affected.

On the positive side, if the user doesn't add or remove screens, its
screen will keep using the same ids.

On the negative side, if the user unplug a screen and plug a different
screen, it will have the same id as the previously unplugged screen.

What's you opinion about it ?

Thanks,

Mathieu