HellO!

I finally installed the new ratpoison and discovered something I
should have noted before my mail...

On Mon, 29 May 2006 22:37:16 +0200, Luca Capello wrote:
> AFAIK, 9menu is not the tiniest solution.  From a first sight, it
> seems so, but then it's not, ratmenu (which is a 9menu derivative)
> is better:
[...]
> [EMAIL PROTECTED]:~$ dpkg -s 9menu | grep Depends
> Depends: libc6 (>= 2.3.5-1), libx11-6, libxext6
> [EMAIL PROTECTED]:~$ dpkg -s ratmenu | grep Depends
> Depends: libc6 (>= 2.3.5-1), libx11-6
> [EMAIL PROTECTED]:~$ dpkg -s libxext6 | grep Installed
> Installed-Size: 108
[...]
> 9menu requires 76 + 108 = 184K, while ratmenu only 96K.  Because of
> this, if I should depend on a menu, I'll go for ratmenu.

/me should have checked the ratpoison dependencies, too.  In fact,
ratpoison already pulls libxext6 as a dependency, so the fact that
9menu requires it or not is irrelevant, thus resulting in 9menu as the
tiniest solution for a menu.

> From a first point of view, I just tried both menus for the first
> time and the only difference is that after executing a menu command
> ratmenu exits, while 9menu waits for another one and so on.

OK, now that I use Escape-. to call the menu, 9menu exits as soon as I
choose a menu command.

> Moreover, there're no other informations in the
> /usr/share/doc/9menu/README (and a README.Debian doesn't exist).

While this is still true, the major problem is on ratpoison side: news
about the menu command and keybinding are present only in the Escape-?
output and in the /usr/share/doc/ratpoison/README.Debian (even if in
the latter case they are "hidden" in the patch explanation).  The man
page doesn't include the menu command (patch attached).  I would
better advertise the new menu command, maybe with a NEWS.Debian.

Sorry for the noise, I hope that this time my mail is more useful ;-)

Thx, bye,
Gismo / Luca

Attachment: ratpoison.1_menu-command_gismo-20060530.patch.gz
Description: ratpoison.1: add menu command

Attachment: pgprD7cDnZS70.pgp
Description: PGP signature

Reply via email to