Re: FVWM: Key binding to raise specific window?

From: Dominik Vogt <dominik.vogt_at_schlund.de>
Date: Mon, 8 Jul 2002 11:52:36 +0200

On Sun, Jul 07, 2002 at 11:33:28PM -0600, Jed S. Baer wrote:
> On Mon, 8 Jul 2002 00:15:28 +0200
> Dominik Vogt <dominik.vogt_at_gmx.de> wrote:
>
> > > I'm using v 2.2.5
> >
> > You should consider upgrading to 2.4.8, the latest stable release.
> > It has a lot of fancy new stuff - and maybe equally important -
> > the 2.4.x series are the only supported stable releases. Now to
> > your question:
>
> I actually installed 2.4.7 from the Sourceforge RPM. I encountered some
> minor problems with it, and went back (this was just this morning, after I
> posted my question). I guess it would be inconsiderate of me to mention
> that, without mentioning what they were, so here goes.
>
> I was somewhat disappointed that I couldn't install the RPM without first
> obtaining libstroke. I know a lot of people consider it to be really
> nifty, but at some point I just get tired of having to intall yet another
> piece of software I'll never use on my system, to be able to get something
> else I do use. I don't mean that to sound like a criticism, and I hope
> that should I decide to build from source, that --disable=libstroke, or
> it's equivalent, is an option. But at the moment, I'm not going to
> download the tarball for the sake of making that discovery - I have very
> limited network bandwidth. I have to admit though, that it's pretty
> unlikely that I'll build from source.

Then you unfortunately have to live with the options that were
compiled into the rpm. We can't supply one rpm for each
combination of options (millions).

> There is a difference in the way menus are drawn. I don't know if it's a
> bug. I looked through the 2.4.7 NEWS file for any mentions of menu changes
> that sounded like what I was seeing, and didn't see any.
>
> MenuStyle * FVWM
> MenuStyle * Foreground seashell, Background DarkSlateGrey
> MenuStyle * Greyed DarkSlateBlue
> MenuStyle * Font -adobe-utopia-medium-r-*-*-19-*-100-100-*-*-iso8859-*
> MenuStyle * MenuFace DGradient 128 4 \
> DarkSlateGrey 10 \
> DarkSlateGrey 58 \
> SlateBlue 22 \
> DarkSlateGrey 10 black
> MenuStyle * SidePic /home/jbaer/images/sideflash.xpm
>
> MenuStyle msmaug FVWM
> MenuStyle msmaug Foreground seashell, Background DarkSlateGrey
> MenuStyle msmaug Greyed DarkSlateBlue
> MenuStyle msmaug Font
> -adobe-utopia-medium-r-*-*-19-*-100-100-*-*-iso8859-* MenuStyle msmaug
> MenuFace DGradient 128 4 \ DarkSlateGrey 10 \
> DarkSlateGrey 58 \
> SlateBlue 22 \
> DarkSlateGrey 10 black
> MenuStyle msmaug SidePic /home/jbaer/images/dgreen_grad.xpm
>
> A menu of style msmaug has a vertical bar, the width of the pixmap, the
> color DarkSlateGrey, running along the left side, while other menus don't.
> I realize my responsibility as a user is to provide good bug reports, but
> please understand that at the moment, there are very good reasons why I'm
> not able to do so. My apologies. dgreen_grad.xpm is transparent, except
> for some greek letters running vertically. I don't imagine it matters that
> they're greek - any 5 letter word would do, or any arrangement of
> non-transparent pixels for that matter. At any rate, I like the way this
> looks in 2.2, but not in 2.4. I should be able to easily reproduce it at a
> later time. How much later, I can't say just now.

I tested this with the latest development code, and there is
definitely a bug somewhere. Sometimes the msmaug MenuStyle is
applied to the wrong menus, sometimes it's not applied to the
correct menus. It seems completely random. When I scroll through
my RootMenu, sometimes the submenus get the menustyle and
sometimes they don't. It's clearly a bug. I'll look into it when
I have the time.

> And, 2.4.7 apparently has problems with swallowing xdaliclock:
>
> *FvwmButtons(2x1 Swallow xdaliclock 'Exec /usr/local/bin/xclock')
>
> -- /usr/local/bin/xclock --
>
> xdaliclock -24 -noseconds -visual best \
> -memory low -bg deepolive -fg palegold \
> -font -*-lucidatypewriter-medium-r-normal-*-15-*-100-100-*-*-*-* \
> -geometry 60x20 &

That command is not correct:

  $ xdaliclock -24 -noseconds -visual best -memory low \
    -bg deepolive -fg palegold -font \
    -*-lucidatypewriter-medium-r-normal-*-15-*-100-100-*-*-*-* \
    -geometry 60x20
  zsh: no matches found:
  -*-lucidatypewriter-medium-r-normal-*-15-*-100-100-*-*-*-*

Since the font name contains wildcards, you have to quote it:

  $ xdaliclock -24 -noseconds -visual best -memory low \
    -bg deepolive -fg palegold -font \
    "-*-lucidatypewriter-medium-r-normal-*-15-*-100-100-*-*-*-*" \
    -geometry 60x20

Bye

Dominik ^_^ ^_^

P.S.: Pleasse always reply to the mailing list, not to my private
address. I usually bounce any such messages to the list anyway.

 --
Dominik Vogt, mail: dominik.vogt_at_schlund.de, phone: 0721/91374-382
Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe
--
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 majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Mon Jul 08 2002 - 04:53:59 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:53 BST