Re: FVWM: fvwm-themes stalls when using root menu
Klaus Zeitler wrote: kzeitler 10861 794 0 14:53:40 pts/30:00 sh -c fvwm-menu-directory -d / --exec-file ^emacs --check-subdir --links --wm It is not a problem of cyclic links somehow? Gert -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: fvwm-themes stalls when using root menu
On 26 May 2003 14:13:01 +0200, Gert Brinkmann wrote: Klaus Zeitler wrote: kzeitler 10861 794 0 14:53:40 pts/30:00 sh -c fvwm-menu-directory -d / --exec-file ^emacs --check-subdir --links --wm It is not a problem of cyclic links somehow? There is no digging in more than depth 1 per menu, so the answer is no. The problem is in unquoted ^ as Klaus said in another message. Just tried on Solaris, this command tries to launch emacs, uff. This is equivalent to PipeRead emacs, fvwm will stall as expected. Regards, Mikhael. -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: fvwm-themes stalls when using root menu
Mikhael == Mikhael Goikhman [EMAIL PROTECTED] writes: Mikhael Mikhael On 22 May 2003 09:01:54 +0200, Klaus Zeitler wrote: Mikhael You may instead kill fvwm-menu-directory process although I never Mikhael saw it may stall in many years, I don't see anything that may Mikhael stall in it. no, killing fvwm-menu-directory doesn't help. But ps shows that the call to fvwm-menu-directory contains more parameters than just '-d /'. kzeitler 10861 794 0 14:53:40 pts/30:00 sh -c fvwm-menu-directory -d / --exec-file ^emacs --check-subdir --links --wm seems to be from functions-appbind in default theme: DestroyFunc FuncFvwmMenuDirectory AddToFunc FuncFvwmMenuDirectory + I PipeRead 'fvwm-menu-directory -d $0 --exec-file ^emacs --check-subdir --links --wm-icons' I can run the whole command (with and without the additional options) just fine in a shell. What amazes me is that fvwm stalls when I simply move the mouse over one of the 2 menu entries Root dir or Home dir, i.e. I don't click any of these two entries. I'd expect fvwm to run the fvwm-menu-directory command as soon as I select, i.e. click one of these entries. Thanks, Klaus -- -- | Klaus Zeitler Lucent Technologies | | Email: [EMAIL PROTECTED] | -- --- Technological progress has merely provided us with more efficient means for going backwards. -- Aldous Huxley -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: fvwm-themes stalls when using root menu
On 23 May 2003 08:46:35 +0200, Klaus Zeitler wrote: Mikhael == Mikhael Goikhman [EMAIL PROTECTED] writes: Mikhael Mikhael On 22 May 2003 09:01:54 +0200, Klaus Zeitler wrote: Mikhael You may instead kill fvwm-menu-directory process although I never Mikhael saw it may stall in many years, I don't see anything that may Mikhael stall in it. no, killing fvwm-menu-directory doesn't help. But ps shows that the call to fvwm-menu-directory contains more parameters than just '-d /'. kzeitler 10861 794 0 14:53:40 pts/30:00 sh -c fvwm-menu-directory -d / --exec-file ^emacs --check-subdir --links --wm seems to be from functions-appbind in default theme: DestroyFunc FuncFvwmMenuDirectory AddToFunc FuncFvwmMenuDirectory + I PipeRead 'fvwm-menu-directory -d $0 --exec-file ^emacs --check-subdir --links --wm-icons' I can run the whole command (with and without the additional options) just fine in a shell. This all is strange. Please create a minimal config ~/.fvwm/minimal that looks like: DestroyFunc FuncFvwmMenuDirectory AddToFunc FuncFvwmMenuDirectory + I PipeRead 'fvwm-menu-directory -d $0' AddToMenu MenuFvwmRoot + MissingSubmenuFunction FuncFvwmMenuDirectory + Root directory Popup / Then do Restart fvwm -f minimal from FvwmConsole. The default root menu should contain the last submenu. Does it stall for you when you enter it? If it does not stall (I think it will on your system), add this command using FvwmConsole that is in the root menu, and enter this submenu again: BusyCursor DynamicMenu True, Read True In case it does not stall (unlikely), type this into FvwmConsole: Restart fvwm-themes-start What amazes me is that fvwm stalls when I simply move the mouse over one of the 2 menu entries Root dir or Home dir, i.e. I don't click any of these two entries. I'd expect fvwm to run the fvwm-menu-directory command as soon as I select, i.e. click one of these entries. All popup submenus work on enter + optional delay, not on click, there are some MenuStyle options to control this, try [EMAIL PROTECTED] I don't see anything to be amazed of, these 2 menus behave exactly like other popup submenus except that they are dynamically built every time. For example there are 2 Menu entries (not Popup) in the same System menu labeled Browser. They are separate menus not submenus, i.e. work on click. I hope they actually work ok for you. Regards, Mikhael. -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: fvwm-themes stalls when using root menu
here's more info: I added Module FvwmCommand to my startup and tried: FvwmCommand FuncFvwmMenuDirectory / Same result, fvwm stalled, but now I could still use this one xterm that had the focus. The session error file (~/.dt/sessionlogs/sfsw51_DISPLAY=:0) now said Option exec-file requires an argument. Somehow it seems as if that ^emacs in: + I PipeRead 'fvwm-menu-directory -d $0 --exec-file ^emacs --check-subdir vanishes into thin air. So now I created an functions-appbind-extra with --- snip --- DestroyFunc FuncFvwmMenuDirectory AddToFunc FuncFvwmMenuDirectory + I PipeRead 'fvwm-menu-directory -d $0 --exec-file ^emacs --check-subdir --links --wm-icons' --- snip --- i.e. with a quoted ^emacs and it works! If that error log wouldn't be overwritten when I start a new session, I'd have found this a lot easier. I think I'm going to save that at the end of my xsession file now. Still I have a few questions: 1. what's happening with that ^file expression? 2. why/how is determined that emacs is used for text files? This is certainly not a problem for me, cause that's the only editor I've been using since 1985, but we have other users here that despise emacs. Isn't it possible to use the env variable EDITOR or some such here? Thanks Klaus -- -- | Klaus Zeitler Lucent Technologies | | Email: [EMAIL PROTECTED] | -- --- Insanity is hereditary. You get it from your kids. -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: fvwm-themes stalls when using root menu
On 23 May 2003 12:56:34 +0200, Klaus Zeitler wrote: I added Module FvwmCommand to my startup and tried: FvwmCommand FuncFvwmMenuDirectory / Same result, fvwm stalled, but now I could still use this one xterm that had the focus. The session error file (~/.dt/sessionlogs/sfsw51_DISPLAY=:0) now said Option exec-file requires an argument. Somehow it seems as if that ^emacs in: + I PipeRead 'fvwm-menu-directory -d $0 --exec-file ^emacs --check-subdir vanishes into thin air. So now I created an functions-appbind-extra with --- snip --- DestroyFunc FuncFvwmMenuDirectory AddToFunc FuncFvwmMenuDirectory + I PipeRead 'fvwm-menu-directory -d $0 --exec-file ^emacs --check-subdir --links --wm-icons' --- snip --- i.e. with a quoted ^emacs and it works! If that error log wouldn't be overwritten when I start a new session, I'd have found this a lot easier. I think I'm going to save that at the end of my xsession file now. Still I have a few questions: 1. what's happening with that ^file expression? You may take a look at man sh on your system. I will quote it. 2. why/how is determined that emacs is used for text files? This is certainly not a problem for me, cause that's the only editor I've been using since 1985, but we have other users here that despise emacs. Isn't it possible to use the env variable EDITOR or some such here? I would really like to use $EDITOR, but this variable is a bit useless in X Window in that some of the editors open their own windows (weird) and some work in the terminal as designed by $EDITOR. So to work for all $EDITOR values you should always open xterm even for emacs. The caret says not to open an xterm. So the only way to customize this is to redefine FuncFvwmMenuDirectory in functions-appbind-extra, you may redefine your own viewer, browser, prefered image processors and so on in the same file too (see FAQ). Regards, Mikhael. -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
