Xref: utzoo gnu.emacs.help:1773 comp.emacs:10559 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!samsung!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!tut.cis.ohio-state.edu!unreplyable!garbage From: darrylo@HPNMXX.SR.HP.COM Newsgroups: gnu.emacs.help,comp.emacs Subject: Re: Menu bar (pull down) in Emacs? Message-ID: <9104172218.AA27088@hpnmd.hp.com> Date: 17 Apr 91 22:10:48 GMT References: <9104171955.AA02951@bullwinkle> Sender: daemon@tut.cis.ohio-state.edu Followup-To: gnu.emacs.help Organization: Gatewayed from the GNU Project mailing list help-gnu-emacs@prep.ai.mit.edu Lines: 57 > Does anyone have an example of this with olwm? I'm afraid that I don't have any olwm examples. However, here is an UNTESTED example for twm: ------------------------------------------------------------------------------- Button1 = : root : f.menu "button1" menu "button1" { "Emacs Utilities" f.title "-------------" f.nop "Read mail" !"gnudoit '(mh-rmail)' &" } ------------------------------------------------------------------------------- This defines a single menu pick called "Read mail", which uses the Emacs MH facilities to read mail. It's quite easy to define hierarchical pop-up menus for Emacs this way. Something similar for mwm would be (please, no flames about non-free software -- I don't have access to olwm, and so I can't give olwm examples): ------------------------------------------------------------------------------- Menu emacs_menu { "Root Menu" f.title "" f.separator "Read mail" f.exec "gnudoit '(mh-rmail)' &" } # # Must have a line like the following in .Xdefaults: # # Mwm*buttonBindings: MainButtonBindings # Buttons MainButtonBindings { root f.menu emacs_menu # # etc., etc. # } ------------------------------------------------------------------------------- All this does assume that you have gnuclient (gnuserv) installed on your system. -- Darryl Okahata UUCP: {hplabs!, hpcea!, hpfcla!} hpnmd!darrylo Internet: darrylo%hpnmd@relay.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion or policy of Hewlett-Packard or of the little green men that have been following him all day.