Re: First try of fvwm-menu-desktop which creates a full menu
Thomas Funk t.f...@web.de writes: Try the examples in the manpage you requested to get an overview about the look and feel of the different display possibilities. The page is created with asciidoc but in Groff format so you can look into it with man ^^ The man page is a LOT less readable than I expected it to be. Does every period have to be escaped? Not real happy with the result. -- Dan Espen
Re: First try of fvwm-menu-desktop which creates a full menu
Thomas Funk t.f...@web.de writes: Hi Dan! I've attached the advised patch related to your last CVS version of fvwm-menu-desktop. It includes the needed functionality to response to the attached configuration tool for fvwm-menu-desktop. Two new options: - get-menus [selected, all] to send the found menus to the config gui - set-menus [filelist] to tell fvwm-menu-desktop which menus should be build The usage prompt for get-menus says it prints a comma separated list, but I get a space separated list. The usage prompt says selected is an option but it looks like anything other than all is what it looks for. I'm not clear on what the selected option is doing. You're English it pretty good. No such word as founded though. Rule of thumb, NEVER use the word will in documentation. Always describe features as already there. Committing the menu-desktop changes for now. -- Dan Espen
CVS dane: * fvwm-menu-desktop.1.in: Applied patch from Thomas Funk.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: dane12/07/19 15:39:18 Modified files: bin: Tag: branch-2_6 ChangeLog fvwm-menu-desktop.in Log message: * fvwm-menu-desktop.1.in: Applied patch from Thomas Funk. Functionality for configuration tool for fvwm-menu-desktop. Two new options: - get-menus [selected, all] to send the found menus to the config gui - set-menus [filelist] to tell fvwm-menu-desktop which menus should be built. Also another option --insert-in-menu NAME.
Re: First try of fvwm-menu-desktop which creates a full menu
Dan Espen des...@verizon.net wrote: Thomas Funk t.f...@web.de writes: Try the examples in the manpage you requested to get an overview about the look and feel of the different display possibilities. The page is created with asciidoc but in Groff format so you can look into it with man ^^ The man page is a LOT less readable than I expected it to be. Does every period have to be escaped? Not real happy with the result. What do you mean with Does every period have to be escaped ? Do you mean the man page file itself or if you use $./man fvwm-menu-desktop.1 I can send you the asciidoc file. It's plain text with some asciidoc formatings. I have no clue how to write groff. So I use the easier way via asciidoc. Thomas
Re: First try of fvwm-menu-desktop which creates a full menu
Thomas Funk t.f...@web.de writes: Dan Espen des...@verizon.net wrote: Thomas Funk t.f...@web.de writes: Try the examples in the manpage you requested to get an overview about the look and feel of the different display possibilities. The page is created with asciidoc but in Groff format so you can look into it with man ^^ The man page is a LOT less readable than I expected it to be. Does every period have to be escaped? Not real happy with the result. What do you mean with Does every period have to be escaped ? Do you mean the man page file itself or if you use $./man fvwm-menu-desktop.1 I can send you the asciidoc file. It's plain text with some asciidoc formatings. I have no clue how to write groff. So I use the easier way via asciidoc. I guess I mis-understood. If you are writing the man page as asciidoc, that's what should get checked in. I'm guessing the other fvwm developers are okay with going to asciidoc? -- Dan Espen
Re: First try of fvwm-menu-desktop which creates a full menu
On 19 July 2012 22:11, Dan Espen des...@verizon.net wrote: I'm guessing the other fvwm developers are okay with going to asciidoc? No. I have an attempt at this, but it's not finished. We either use groff or nothing, and I don't mean groff backported from some conversion tool. If you don't know groff, start learning. The alternative approach is to put the fvwm-menu-desktop under docbook's control. These are the only two options. -- Thomas Adam
Re: First try of fvwm-menu-desktop which creates a full menu
Am 19.07.2012 22:38, schrieb Dan Espen: Thomas Funk t.f...@web.de writes: Hi Dan! I've attached the advised patch related to your last CVS version of fvwm-menu-desktop. It includes the needed functionality to response to the attached configuration tool for fvwm-menu-desktop. Two new options: - get-menus [selected, all] to send the found menus to the config gui - set-menus [filelist] to tell fvwm-menu-desktop which menus should be build The usage prompt for get-menus says it prints a comma separated list, but I get a space separated list. Uups, forgot to change to 'space separated list'. Would you change it, please? The usage prompt says selected is an option but it looks like anything other than all is what it looks for. I'm not clear on what the selected option is doing. Yes, right. You can use every word you want but it needs a word because I sample in parsemenus() for not get_menus == '' (it's for both). As the user doesn't know it I decided to use 'selected' for the other possibility. You're English it pretty good. No such word as founded though. Thanks for the compliment :-) I try to reduce the german part of my english to a bearable level with talking and writing ^^ Rule of thumb, NEVER use the word will in documentation. Always describe features as already there. Ah, ok. Not known. Thanks for the tip. Thomas
Re: First try of fvwm-menu-desktop which creates a full menu
Thomas Adam tho...@fvwm.org writes: On 19 July 2012 22:11, Dan Espen des...@verizon.net wrote: I'm guessing the other fvwm developers are okay with going to asciidoc? No. I have an attempt at this, but it's not finished. We either use groff or nothing, and I don't mean groff backported from some conversion tool. If you don't know groff, start learning. I thought since you were making the attempt, you thought asciidoc would be a good direction to go in. The alternative approach is to put the fvwm-menu-desktop under docbook's control. These are the only two options. Okay with me. TF: All I really need is the words. I can add (t)groff/man markup as needed. -- Dan Espen
Re: First try of fvwm-menu-desktop which creates a full menu
On Thu, Jul 19, 2012 at 05:48:25PM -0400, Dan Espen wrote: Thomas Adam tho...@fvwm.org writes: On 19 July 2012 22:11, Dan Espen des...@verizon.net wrote: I'm guessing the other fvwm developers are okay with going to asciidoc? No. I have an attempt at this, but it's not finished. We either use groff or nothing, and I don't mean groff backported from some conversion tool. If you don't know groff, start learning. I thought since you were making the attempt, you thought asciidoc would be a good direction to go in. Yes it will be when it's ready. It's pretty much done, bar some plugging in scripts so it builds. But until I can finish that and then rip out the other docs, having it in Asciidoc means we can't use it, and that's bad. -- Thomas Adam -- Deep in my heart I wish I was wrong. But deep in my heart I know I am not. -- Morrissey (Girl Least Likely To -- off of Viva Hate.)
Re: First try of fvwm-menu-desktop which creates a full menu
Thomas Funk t.f...@web.de writes: Am 19.07.2012 22:38, schrieb Dan Espen: Thomas Funk t.f...@web.de writes: Hi Dan! I've attached the advised patch related to your last CVS version of fvwm-menu-desktop. It includes the needed functionality to response to the attached configuration tool for fvwm-menu-desktop. Two new options: - get-menus [selected, all] to send the found menus to the config gui - set-menus [filelist] to tell fvwm-menu-desktop which menus should be build The usage prompt for get-menus says it prints a comma separated list, but I get a space separated list. Uups, forgot to change to 'space separated list'. Would you change it, please? As you probably know by now, I did. The usage prompt says selected is an option but it looks like anything other than all is what it looks for. I'm not clear on what the selected option is doing. Yes, right. You can use every word you want but it needs a word because I sample in parsemenus() for not get_menus == '' (it's for both). As the user doesn't know it I decided to use 'selected' for the other possibility. I don't see get-menus in the man page. I think you want the option to be: --get-menus all | desktop with an error for any other value. Rule of thumb, NEVER use the word will in documentation. Always describe features as already there. Ah, ok. Not known. Thanks for the tip. Pet peeve. We tend to write documentation describing new features as this will do X, but when the reader sees it, it does do X. -- Dan Espen
CVS dane: * fvwm-menu-desktop.in (main): Change --get-menus option to all/desktop.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: dane12/07/19 17:12:55 Modified files: bin: Tag: branch-2_6 ChangeLog fvwm-menu-desktop.in Log message: * fvwm-menu-desktop.in (main): Change --get-menus option to all/desktop. Add validation.
Re: First try of fvwm-menu-desktop which creates a full menu
Thomas Adam tho...@fvwm.org writes: On Thu, Jul 19, 2012 at 05:48:25PM -0400, Dan Espen wrote: Thomas Adam tho...@fvwm.org writes: On 19 July 2012 22:11, Dan Espen des...@verizon.net wrote: I'm guessing the other fvwm developers are okay with going to asciidoc? No. I have an attempt at this, but it's not finished. We either use groff or nothing, and I don't mean groff backported from some conversion tool. If you don't know groff, start learning. I thought since you were making the attempt, you thought asciidoc would be a good direction to go in. Yes it will be when it's ready. It's pretty much done, bar some plugging in scripts so it builds. But until I can finish that and then rip out the other docs, having it in Asciidoc means we can't use it, and that's bad. If we add an asciidoc file, I'd expect the Makefile to be modified to produce the man page or html as required. -- Dan Espen
