On Fri, Jun 05, 2015 at 12:42:52AM -0400, David Morris wrote: > I would be among those opposed to seeing mrxvt tied to a big toolkit > like GTK unless it were an optional component (e.g. mrxvt-gtk as a > separate build configuration).
I'm certainly for this! I don't use menus in mrxvt, and don't plan to in the foreseeable future. I'd be OK deleting it entirely, or moving it to gtk, or improving it (e.g. allow sticky menus), or leaving it as is :) If we just move the menus to gtk, we can certainly make them optional at compile time. In my opinion, the "best" way to handle this is as follows: Mrxvt has the ability to accept commands over a fifo. This interface can be improved a little (e.g. moved to a more secure dbus structure), and then one can write an *external* program (say using python + gtk) that displays menus and communicates to mrxvt via the new dbus interface (or the current fifo hack). The only extra library I think I would lobby for is libvte -- all said and done our terminal emulation has not evolved and is not complete (and doesn't support utf8). But it still works (for me at least), so I'm happy to leave it as is and use my screen/vim hacks for utf8. Btw -- I must say that the lack of utf8 is getting more annoying. Now tools like ls and mv output "smart quotes" (even if your locale is not a UTF8 locale) which shows up as ?? in mrxvt. xinput / pstree use utf8 line drawing characters, etc. GI -- 'Laziness' -- Resting before you get tired. ------------------------------------------------------------------------------ _______________________________________________ Materm-devel mailing list Materm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/materm-devel mrxvt home page: http://materm.sourceforge.net
