On Tue, Sep 30, 2014 at 12:30 AM, Charlie <aries...@ipstarmail.com.au> wrote: > > On Mon, 29 Sep 2014 17:51:41 -0700 Vincent mentioned this: > Re: fvwm: was i3 sticky/floating windows (brasero requires > gvfs). > >> On Sat, Sep 27, 2014 at 2:44 PM, Charlie <aries...@ipstarmail.com.au> >> wrote: >> > >> > On Sat, 27 Sep 2014 16:20:27 +0200 lee mentioned this: >> > Re: fvwm: was i3 sticky/floating windows (brasero requires >> > gvfs). >> > >> >> >> >> >> Steve Litt <sl...@troubleshooters.com> writes: >> >> >> >> >> >> Because you use fvwm on a regular basis, you should write some >> >> >> documentation on it. >> >> >> >> Please check out [1] --- let me know if it works for you and how >> >> you like it. >> >> >> >> >> >> [1]: https://github.com/lee-/fvwm >> >> >> >> >> >> -- >> >> Knowledge is volatile and fluid. Software is power. >> > >> > >> > From my keyboard: >> > >> > Hello Lee, >> > >> > I've just had a cursory read and you have put a lot of effort >> > into this. Thank you on behalf of those of us who will >> > appreciate and use it. >> > >> > I have a meeting to attend this morning that will keep me away most >> > of the day, so I won't have the time to read all of it till I >> > return. >> > >> > But just quickly and without the history why I moved from fvwm to >> > xfce4. >> > >> > I used the win95 script to get an fvwm setup quickly. I'm tweaking >> > as i go along as time permits. >> > >> > I wanted to get the Debian Menu into the fvwm Root menu to get rid >> > of the taskbar but have not found yet, how that can be done. >> > >> >> Examples of how the Debian menu is configured and used is provided as >> part of the Fvwm package, under /usr/share/doc/fvwm/examples/. >> >> It is composed of three parts: >> 1. A function definition >> >> DestroyFunc SetDebianMenu >> AddToFunc SetDebianMenu >> + I Read /etc/X11/fvwm/menudefs.hook >> >> Which when called will read from the menudefs.hook under >> /etc/X11/fvwm/. This menudefs.hook defines the structure of the Debian >> menu, but is not yet linked to your personal menu. The name of the >> Debian menu is "/Debian". >> >> 2. Calling the function >> >> Test (f /etc/X11/fvwm/menudefs.hook) SetDebianMenu >> >> Which will first test if the menu exists, then calls the function >> defined in step 1. This line can be put anywhere you like, as long as >> it's after the function definition. >> >> 3. Add the Debian menu to your menu >> >> Test (f /etc/X11/fvwm/menudefs.hook) + "Debian Menu" Popup "/Debian" >> >> Insert this as part of your menu definitions, under 'AddToMenu ...'. >> This instructs Fvwm to insert an entry to popup the menu "/Debian". >> >> Hope it helps, >> >> Vincent Chen > > > From my keyboard: > > Hello Vincent, > > Thanks you for that. Doesn't do it for me. I want to get rid of > the taskbar and just have the Debian menu available through the > left mouse click on the desktop instead. > > But it doesn't work for me at all. I can get rid of the taskbar, but > then I don't have a Debian menu I can call up every application in the > Debian menu in a terminal, but that's just too tedious. > That's because you didn't follow the steps I laid out. Insert the snippets I provided in step 1 and 2 directly in your config file. Not inside the root menu or any other directives, but directly in your config file.
> In my menus - Root Menu - there is already this in part: > > + "&Restart%mini.turn.xpm%" Popup Restart > + "&Quit fvwm%mini.stop.xpm%" FvwmForm > FvwmForm-QuitVerify Test (f /etc/X11/fvwm/menudefs.hook) + > "$[gt.&Update My Debian Menu]%menu/terminal.xpm%" PipeRead > 'update-menus && echo "Read $./menudefs.hook"' > Because this does exactly what it says: "Update My Debian Menu". _IF_ you already have a Debian menu, clicking this entry will update the Debian menu. This has nothing to do with actually providing the Debian menu entry in your menu. > But It doesn't show up so I might have to edit it, but don't know how. > So will have to keep playing about when I get time. > Insert the snippet in step 3 in your menu. That's what will actually insert the Debian menu entry in your own menu. I'll try and restate what is being done: - Steps 1 and 2 defines the structure of the Debian menu, and makes Fvwm aware of what the Debian menu looks like. - Step 3 is what makes Fvwm actually show the Debian menu as a menu entry. If you only do steps 1 and 2, Fvwm will know about the Debian menu, but does not display it anywhere. If you only do step 3, Fvwm will display a menu entry, but will have no idea what this "/Debian" menu is. Regards, Vincent -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAFuqiEZbTh7VSRa_fuWv-OMvrpppPBXQoZkrWrgFX=L6j=c...@mail.gmail.com
