You are not logged in.
Pages: 1
Topic closed
I've tried to use menumaker (mmaker -v OpenBox3) to generate the menu files for openbox.
It seems to generate terminal output:
$ mmaker -v OpenBox3
* scanning
desktop... 63 apps found
legacy... 9 apps found
debian... 1 apps found
* merging... 7 coincidings detected
* generating
no terminal emulator specified; will use the default
no suitable terminal emulator foundbut no .config/openbox/menu.xml file is generated in the process. Why is it not working? Where does the output go? (Openbox naturally doesn't read the output either)
Last edited by rabcor (2014-09-16 17:20:58)
Offline
I can confirm this doesn't seem to work in a reasonable way. I tried it out and searched for any files containing what must be in the result, but could find none. There is no man page, and the --help output is limited. But one option in the help output was to send the results to stdout rather than to a (unspecified) file, but when used, nothing was sent to stdout.
It's not clear why, but the tool does not seem to be doing anything. Given the absence of any documentation to help us see if we are doing something wrong, this may warrant a bug report as the program does not seem to do what it claims to do.
EDIT: From menumaker's website
Default MenuMaker operation is to dump menu to WM-specific file inside user's home.
This is certainly not happening.
Last edited by Trilby (2014-09-16 11:06:36)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
As a temporary or maybe permanent substitute you could use obmenu-generator.
Edit: Permanently - was it you autocorrect or just me?
Last edited by emeres (2014-09-16 11:40:41)
Offline
Yes, I just turned to that one, I actually quite love it, it's a convenient tool
Set up my menu in a flash for me.
Last edited by rabcor (2014-09-16 11:38:05)
Offline
This is happening because you do not have a recognised root terminal installed. As specified in the Openbox wiki article (https://wiki.archlinux.org/index.php/Openbox#menumaker), you need to have a root terminal installed. Install xterm and it should work:
# pacman xtermI remember being confused the first time by this as well, which is why I made sure to include this information when re-writing the Openbox article.
Offline
That seems be the case, xterm should be made a dependency. I tested this by moving xterm out of the way and get the same error message.
Offline
I don't know what "root terminal" means in this context. It is no harder to log in as root in any other terminal that it is in xterm.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I don't know what "root terminal" means in this context. It is no harder to log in as root in any other terminal that it is in xterm.
"Root terminal" means whatever menu maker wants it to be! I don't get it either, but that's how it works - LOL
Offline
Neither do I, that part of the wiki should probably be changed.
Offline
So not having xterm was the problem, this program sure has special needs
Marked as solved. And I agree it wouldn't be so bad if it were a dependency.
Last edited by rabcor (2014-09-16 17:22:31)
Offline
@rabcor Then write a bug report: https://www.archlinux.org/packages/comm … menumaker/
Offline
Ok. So basically the link you gave me made me understand much better the concept of my problem.
The openbox-menu software generates a menu.xml file that reads my applications.menu and goes from there. I saw through your link that in order to call programs via terminals you put something like xterm -e in front the program, which in my case is xterm -e htop.
i checked the source-code of openbox-menu and it's setup by default to that (xterm -e). I changed it to lxterminal -e instead, recompiled, and now i'm good to go.
Your help was really appreciated. Thx !!
Offline
showipatlogon, I think you posted in the wrong thread. This thread is six years old and marked solved.
Your openbox menu thread is here: https://bbs.archlinux.org/viewtopic.php?id=261525
Closing.
Offline
Pages: 1
Topic closed