fvwm2 and ClickToFocus (how to stop window raising?)

[George Sanderson]

I got sick of the ancient twm so I downloaded fvwm2 and compiled it on a sparc 10...
(I chose fvwm since it has been recommended to me by friends who use Linux).

I played around with the .fvwm2rc file and enabled ClickToFocus, but the added
behaviour of raising the window when it was focused was more annoying than I first
thought (ie. the standard stupid Windoze/MacOS behaviour).

So, how do I get fvwm2 to focus windows when I click in them, WITHOUT raising them ?
Is there an option which does this already and I have missed it somewhere ?
If not, how do I add/hack/etc this behaviour or modify ClickToFocus ?

(additionally, since I like the lovely feature of fvwm virtual screens/space,
is it possible to automatically focus the window under the pointer, whenever
the screens/space are switched, _while_ using something like ClickToFocus ? )

[Byron A Jeff]

In article <NEWTNews.840780...@kolbod.ix.netcom.com>,
Trebor A. Rude <tre...@mnsinc.com> wrote:
>
>In Article<4vj9q7$i...@griffin.itc.gu.edu.au>, <aiss...@kraken.itc.gu.edu.au>
>writes:

>
>> So, how do I get fvwm2 to focus windows when I click in them, WITHOUT
>> raising them ?
>

> There should be line in your .fvwm2rc that looks something like
>'+ "I" FvwmAuto 200'. FvwmAuto is an fvwm module that automatically raises
>the window with the focus after (in this case) 200 milliseconds. Simple
>removing the line will prevent the behavior.

Nope. This isn't the behavior he (she?) is describing. When ClickToFocus is
enabled, the process of focusing the window also brings it to the top.

AFAIK these two go together. And IMHO it makes sense: why would you
deliberately select a window and not want to view all its contents?
This click to raise behavior is consistent with both ClickFocus and
FollowFocus.

The problem with MAC/Windows (which was alluded to in the original post) is
that there's no way to modify the original behavior. You must click on the
window to focus and it must come to the top when you click it.

I just started playing with autoraise yesterday. It's fairly good for a
default behavior but can be annoying sometimes when you don't want the window.

>
>> (additionally, since I like the lovely feature of fvwm virtual
>screens/space,
>> is it possible to automatically focus the window under the pointer, whenever
>> the screens/space are switched, _while_ using something like ClickToFocus ?
>)
>

>Hmm, I don't think so. But I'm not sure. You might find a better answer on
>comp.os.linux.x or from the fvwm mailing list: fv...@hpc.uh.edu.

That behavior does not exist.

Honestly the best solution is to turn ClicktoFocus off. FollowFocus gives
all the behaviors you want at the minor expense of having to keep the mouse
in the focus window: i.e. the windows won't raise (you must click to raise
them) and whatever window is under the mouse when you switch becomes the focus
window.

I suggest turning off Clicktofocus first and see how well it works for you.
if if turns out to be unusable, then prepare to do some programming because
the behaviors you want are not available....

Good Luck,

BAJ
--
Another random extraction from the mental bit stream of...
Byron A. Jeff - PhD student operating in parallel - And Using Linux!
Georgia Tech, Atlanta GA 30332 Internet: by...@cc.gatech.edu

[Trebor A. Rude]

In Article<4vj9q7$i...@griffin.itc.gu.edu.au>, <aiss...@kraken.itc.gu.edu.au>
writes:

> So, how do I get fvwm2 to focus windows when I click in them, WITHOUT
> raising them ?

There should be line in your .fvwm2rc that looks something like
'+ "I" FvwmAuto 200'. FvwmAuto is an fvwm module that automatically raises
the window with the focus after (in this case) 200 milliseconds. Simple
removing the line will prevent the behavior.

> (additionally, since I like the lovely feature of fvwm virtual

[Hal L. DeVore Jr.]

In article <4vj9q7$i...@griffin.itc.gu.edu.au>,

aiss...@kraken.itc.gu.edu.au (George Sanderson) writes:
> I got sick of the ancient twm so I downloaded fvwm2 and compiled it on a sparc 10...
> (I chose fvwm since it has been recommended to me by friends who use Linux).
>
> I played around with the .fvwm2rc file and enabled ClickToFocus, but the added
> behaviour of raising the window when it was focused was more annoying than I first
> thought (ie. the standard stupid Windoze/MacOS behaviour).
>

> So, how do I get fvwm2 to focus windows when I click in them, WITHOUT raising them ?

> Is there an option which does this already and I have missed it somewhere ?
> If not, how do I add/hack/etc this behaviour or modify ClickToFocus ?
>

> (additionally, since I like the lovely feature of fvwm virtual screens/space,
> is it possible to automatically focus the window under the pointer, whenever
> the screens/space are switched, _while_ using something like ClickToFocus ? )
>

With fvwm2 the autoraise is done by the separate FvwmAuto module (man page text
below). If you don't want autoraise, don't run FvwmAuto in your .fvwm2rc file.

--

Hal DeVore | hde...@bmc.com ---- PGP Key fingerprint
BMC Software, Inc. | EA A3 2F 62 98 38 B0 15 F0 85 76 33 E1 5A 2A 64
Houston, TX USA | <*> Most apologizing, mathematics not Zathras skill

---

NAME

FvwmAuto - the FVWM auto-raise module

SYNOPSIS

FvwmAuto is spawned by fvwm, so no command line invocation will work. An appropriate
invocation from fvwm looks like:

Module FvwmAuto 200

or, from a menu: Popup "Module-Popup"
Title "Modules"
Module "GoodStuff" GoodStuff
Module "NoClutter" FvwmClean
Module "FvwmIdentify" FvwmIdent
Module "Banner" FvwmBanner
Module "Debug" FvwmDebug
Module "SaveDesktop" FvwmSave
Module "AutoRaise" FvwmAuto 200 EndPopup

The numeric argument is required. It specified how long a window must retain the keyboard input
focus before it is raised. The delay is measured in milliseconds, and any integer 0 or greater is
acceptable.

AUTHOR

FvwmAuto just appeared one day, nobody knows how.

[Trebor A. Rude]

In Article<4vkbeg$8...@solaria.cc.gatech.edu>, <by...@cc.gatech.edu> writes:

> Honestly the best solution is to turn ClicktoFocus off. FollowFocus gives
> all the behaviors you want at the minor expense of having to keep the mouse
> in the focus window: i.e. the windows won't raise (you must click to raise
> them) and whatever window is under the mouse when you switch becomes the
focus
> window.

There's also SloppyFocus. It's like MouseFocus, except that when the
pointer leaves the window in focus and goes into the root window, the window
with focus doesn't lose it. Only if the pointer enters a non-root window will
the focus change. This is my default focus style, and I rather like it.

--
Trebor A. Rude
tre...@mnsinc.com

[Robert Nation 885-9815]

>> So, how do I get fvwm2 to focus windows when I click in them, WITHOUT
>> raising them ?

If you recompile Fvwm, but define the compile time flag
CLICKY_MODE_1 (in configure.h, you add #define CLICKY_MODE_1, then do
a clean build), then I think the window will only be raised when you
click on the border.

Rob

[Tero Pelander]

aiss...@kraken.itc.gu.edu.au (George Sanderson) writes:
>I played around with the .fvwm2rc file and enabled ClickToFocus, but the added
>behaviour of raising the window when it was focused was more annoying than I first
>thought (ie. the standard stupid Windoze/MacOS behaviour).

# From my .fvwmrc
AutoRaise -1 # time it takes to raise the window on top. -1 is newer
ClickToFocus

[Luis Fernandes]

>>>>> "byron" == Byron A Jeff <by...@cc.gatech.edu> writes:

> I just started playing with autoraise yesterday. It's fairly
> good for a default behavior but can be annoying sometimes when
> you don't want the window.

There should be a variable that contorls the autoraise treshold; i.e.
the window autoraises only if your pointer stays in the window for a
certain period of time (500ms) and not if the pointer passes through
on the way to another window.

I remember twm, from which fvwm is derived, having this feature (at
least that's how I remember it when I too was a novice and my .twmrc
changed but 5 times a day; the modification date on my .twmrc is Nov.
23, 1993 :-)

[George Sanderson]

:> So, how do I get fvwm2 to focus windows when I click in them, WITHOUT
:> raising them ?

: There should be line in your .fvwm2rc that looks something like

:'+ "I" FvwmAuto 200'. FvwmAuto is an fvwm module that automatically raises
:the window with the focus after (in this case) 200 milliseconds. Simple
:removing the line will prevent the behavior.

nope - it's not in there... The raising window behaviour seems to be
(stupidly) an inherent feature of ClickToFocus.

[Stephan Boettcher]

I started with SloppyFocus, but soon changed to MouseFocus, because of the
following problem:

I used to switch from page to page within the desktop with the keyboard. When
the cursor ended up in the root window, the window in the now invisible page
kept being selected. Most often this was the emacs, which, by accident, received
the next key, instead of the xterm they where intended for.

Maybe this has changed with fvwm2.

Stephan

---------------------------------------------------------------------------
Stephan B"ottcher FAX: +972-3-640-7932
School of Physics and Astronomy Tel: +972-3-640-7722
High Energy Physics Department or -8240
Tel Aviv University Email: ste...@alzt.tau.ac.il
69978 Tel Aviv or boet...@desy.de
Israel WWW: http://zow00.desy.de:8000/~stephan/home.html
---------------------------------------------------------------------------

[Perry Donham]

>>>>> "Byron" == Byron A Jeff <by...@cc.gatech.edu> writes:

Byron> In article
Byron> <NEWTNews.840780...@kolbod.ix.netcom.com>,

Byron> Trebor A. Rude <tre...@mnsinc.com> wrote:
>> In Article<4vj9q7$i...@griffin.itc.gu.edu.au>,
>> <aiss...@kraken.itc.gu.edu.au> writes:
>>

>>> So, how do I get fvwm2 to focus windows when I click in them,
>>> WITHOUT raising them ?
>> There should be line in your .fvwm2rc that looks something
>> like '+ "I" FvwmAuto 200'. FvwmAuto is an fvwm module that
>> automatically raises the window with the focus after (in this
>> case) 200 milliseconds. Simple removing the line will prevent
>> the behavior.

Byron> Nope. This isn't the behavior he (she?) is describing. When
Byron> ClickToFocus is enabled, the process of focusing the window
Byron> also brings it to the top.

Byron> AFAIK these two go together. And IMHO it makes sense: why
Byron> would you deliberately select a window and not want to view
Byron> all its contents? This click to raise behavior is
Byron> consistent with both ClickFocus and FollowFocus.

It's funny to see how we use this stuff in different ways. I
constantly nudge the pointer to a covered window (partially covered, I
can see the first few columns) to type a command or answer a prompt
without raising the window. I use FvwmAuto with a 4-second delay, so
if I really need to see the entire window I can just leave the pointer
there and it'll pop up.

Perry
--
----------------------------------------------------------------------
Finger don...@en-garde.com for PGP public key
PGP encrypted mail welcome
Visit KidPub! http://www.en-garde.com/kidpub

[Byron A Jeff]

In article <m268661...@escrime.en-garde.com>,
Perry Donham <don...@escrime.en-garde.com> wrote:
->>>>> "Byron" == Byron A Jeff <by...@cc.gatech.edu> writes:
-
- Byron> In article
- Byron> <NEWTNews.840780...@kolbod.ix.netcom.com>,
- Byron> Trebor A. Rude <tre...@mnsinc.com> wrote:
- >> In Article<4vj9q7$i...@griffin.itc.gu.edu.au>,
- >> <aiss...@kraken.itc.gu.edu.au> writes:
- >>
- >>> So, how do I get fvwm2 to focus windows when I click in them,
- >>> WITHOUT raising them ?
-
- Byron> Nope. This isn't the behavior he (she?) is describing. When
- Byron> ClickToFocus is enabled, the process of focusing the window
- Byron> also brings it to the top.
-
- Byron> AFAIK these two go together. And IMHO it makes sense: why
- Byron> would you deliberately select a window and not want to view
- Byron> all its contents? This click to raise behavior is
- Byron> consistent with both ClickFocus and FollowFocus.
-
-It's funny to see how we use this stuff in different ways. I
-constantly nudge the pointer to a covered window (partially covered, I
-can see the first few columns) to type a command or answer a prompt
-without raising the window. I use FvwmAuto with a 4-second delay, so
-if I really need to see the entire window I can just leave the pointer
-there and it'll pop up.

Let me clarify. By deliberatly select I mean pointing and clicking.
I do exactly the same as you (Followfocus without the window coming up)
and just starting to experiment with the AutoRaise.

But if you click on the window, it comes up. Very consistent behavior.

BTW it prompts another question: if clicking on the window selects it
but doesn't raise it, then how does one raise the window short of going
to the middle button menu?

I think FollowFocus and Autoraise is a good team. I just can't see how to
divorce ClickFocus and raising the window on click.

[George Sanderson]

by...@cc.gatech.edu (Byron A Jeff) writes:

:BTW it prompts another question: if clicking on the window selects

:it but doesn't raise it, then how does one raise the window short
:of going to the middle button menu?

one could double click inside the window or, more appropriately,
the drag bar.

:I think FollowFocus and Autoraise is a good team. I just can't see

:how to divorce ClickFocus and raising the window on click.

The current ClickToFocus has very annoying behaviour for me.
I can't understand how anybody could use a program like Matlab
with this raise-window-to-front behaviour (just try using it on
a MacOS or Windoze machine to see what i mean).

[Robert L. Urban]

I'm trying to get more-or-less exactly the opposite behaviour as the
original poster...

I would like the focus to follow my mouse, WITHOUT autoraise (that
drives me crazy), and I would like to be able to click button 1 IN a
window (not just on a border) and raise it.

I have tried:
Mouse 1 W N Raise

but my windows not longer got MB1 events.

Maybe there is an obvious solution...

--
Rob Urban
Digital Equipment GmbH
Freischuetzstr. 91
81927 Muenchen
Germany

[Tom Sico]

[note followups to comp.unix.misc only - time to get a few others out]

>> In Article<4vj9q7$i...@griffin.itc.gu.edu.au>,
>> <aiss...@kraken.itc.gu.edu.au> writes:
>>

>> So, how do I get fvwm2 to focus windows when I click in them,

>> WITHOUT raising them ?

My autoraise is currently commented out, ie:

#AutoRaise 750

No worries and no annoying (IMHO) raising.

To answer the person who asked about how to go about raising the window without using the middle key menu, you can bind a function to the mouse or a key combination to do it. For example, I have the following functions (I think they are defaults):

Function "Move-or-Raise"
Move "Motion"
Raise "Motion"
Raise "Click"
Iconify "DoubleClick"
EndFunction

Function "Resize-or-Raise"
Resize "Motion"
Raise "Motion"
Raise "Click"
RaiseLower "DoubleClick"
EndFunction

and they are bound to:

Mouse 1 FS A Function "Resize-or-Raise"
Mouse 1 T A Function "Move-or-Raise"

(mouse 1 on frame (FS) or title (T) in combination with any (A) key will
raise the window.)

I am pretty sure you should be able to just use the Raise command and
not even bother with the functions if you want. Could probably even
bind a key on the keyboard to do it...this is just the way I do I've
done it since twm...

Tom

*expressed opinions are mine, not necessarily my employers*

[Lutz Kotoll]

Hi,

nope, doesn't do it for me -- AutoRaise seems to override ClickToFocus and
puts me into follow focus.

to all on this thread:

instead of arguing which focus method is superior you should accept other
persons likes and dislikes -- and just come back to the original question:
how is the following behavior achieved:

- a window gets focus with a click-action in it (perhaps click into the client
area) -- but it doesn't raise
- a window raises with another click-action (perhaps click onto some border
elements) -- it may receive focus too but it it needn't be, you then have an
additional possibility for personal configuration

if someone knows an answer to _this_, please step forward -- even if it
requires some code hacking.

\bye{Lutz}

--
Lutz....@tu-clausthal.de

There is ONE reason to use Windows95 -- it has multitasking:
you can boot the system and crash it simultaneously!

[Fred Gylys-Colwell]

On 29 Aug 1996 09:43:21 GMT, Lutz Kotoll <in...@obelix.rz.tu-clausthal.de> wrote:
>Hi,
>Tero Pelander (tpe...@antares.utu.fi) wrote:
>> aiss...@kraken.itc.gu.edu.au (George Sanderson) writes:
>> >I played around with the .fvwm2rc file and enabled ClickToFocus, but the added
>> >behaviour of raising the window when it was focused was more annoying than I first
>> >thought (ie. the standard stupid Windoze/MacOS behaviour).
>
>> # From my .fvwmrc
>> AutoRaise -1 # time it takes to raise the window on top. -1 is newer
>> ClickToFocus
>
>nope, doesn't do it for me -- AutoRaise seems to override ClickToFocus and
>puts me into follow focus.

> ...<snip>

I don't have a complete answer to the question. But I tried to do the
same thing and failed. I use the following in my .fvwmrc as the next
best thing. It beats trying to edit the code of fvwm.

<code from .fvwmrc>
# Button 1 in title should raise, 3 should lower, 2 should move.
Mouse 1 ST A Function "Move-or-Raise"
Mouse 1 STW M Raise
Mouse 2 STI A Move
Mouse 2 STW M Move
Mouse 3 STI A Lower
Mouse 3 STW M Lower
<end of code from .fvwmrc>

This allows me to click once on a window to select it, and give it
focus. I then use Alt-button-3 to push the window to the bottom.
This usually gives me the desired effect with two button clicks and
key press. This works because Raise and Lower to not change which
window has focus.

I hope this is helpful to someone.
Fred GC.

--
----------------------------------------------------------------------
Fred Gylys-Colwell fre...@math.bsu.edu (317) 285-8678

[Emiliano]

On 3 Sep 1996 17:27:33 GMT, Fred Gylys-Colwell <fre...@various.math.bsu.edu> wrote:
>On 29 Aug 1996 09:43:21 GMT, Lutz Kotoll <in...@obelix.rz.tu-clausthal.de> wrote:
>>Hi,
>>Tero Pelander (tpe...@antares.utu.fi) wrote:
>>> aiss...@kraken.itc.gu.edu.au (George Sanderson) writes:
>>> >I played around with the .fvwm2rc file and enabled ClickToFocus, but the add
> ed
>>> >behaviour of raising the window when it was focused was more annoying than I
> first
>>> >thought (ie. the standard stupid Windoze/MacOS behaviour).
>>
>>> # From my .fvwmrc
>>> AutoRaise -1 # time it takes to raise the window on top. -1 is newer
>>> ClickToFocus
>>
>>nope, doesn't do it for me -- AutoRaise seems to override ClickToFocus and
>>puts me into follow focus.
>> ...<snip>
>
>I don't have a complete answer to the question. But I tried to do the
>same thing and failed. I use the following in my .fvwmrc as the next
>best thing. It beats trying to edit the code of fvwm.
><code from .fvwmrc>

You guys probably have a line like

+ "I" Module FvwmAuto 500

specified in your InitFunction and RestartFunction (.fvwmrc). Try
commenting it out.

--
Bye,

Emile
===========================================================
the views ... employer
===========================================================
Antonym, n.:
The opposite of the word you're trying to think of.

[Lutz Kotoll]

Hi,

Emiliano (qq...@st13-oa6.oce.nl) wrote:
> You guys probably have a line like

> + "I" Module FvwmAuto 500

> specified in your InitFunction and RestartFunction (.fvwmrc). Try
> commenting it out.

this was already said on this thread.

and the answer is:
no i don't have any FvwmAuto in .fvwmrc!

please give more helpful advices next time

[Emiliano]

On 5 Sep 1996 12:00:58 GMT, Lutz Kotoll <in...@azurix.rz.tu-clausthal.de> wrote:
>Emiliano (qq...@st13-oa6.oce.nl) wrote:
>> You guys probably have a line like
>> + "I" Module FvwmAuto 500
>> specified in your InitFunction and RestartFunction (.fvwmrc). Try
>> commenting it out.
>
>this was already said on this thread.

In what group? Not all answers are posted in all groups in the header
list, you know.

>
>and the answer is:
>no i don't have any FvwmAuto in .fvwmrc!
>
>please give more helpful advices next time

OK, here's some: get an attitude reajustment

I was just trying to help, dude. If you don't like people guessing at
your problems, give us some info: your fvwm version and .fvwmrc might
help.

--
Bye,

Emile
===========================================================
the views ... employer
===========================================================

A year spent in artificial intelligence is enough to make one believe
in God.

[Steve Cahill]

I have had this little nagging problem of my mouse pointer/cursor
pointing about 3 mm to the right of its actual (active) location for
about 9 mounths (since I first installed XF86 on my linux OS).

What this means is I have to have a trained eye when I want to
cut-and-paste (start slightly to the right) or when I want to drag a
scroll-bar. First I thought it might have been a bug in in the XF86
version of openwin, but it is the same in fvwm too.

Does anyone know how to correct for this? Or calibrate it out?

Just another little nag/nuisance :-(

Thanks in advance home X'ers -

--Steve Cahill

[Ron Hensley]

>This usually gives me the desired effect with two button clicks and
>key press. This works because Raise and Lower to not change which
>window has focus.
>
>I hope this is helpful to someone.
> Fred GC.

All you should need is to comment out:
#ClickToFucus
and uncomment
AutoRaise 500

Thats all i did on both BSDI and on Linux and works just fine

--

*******************************************************************
* Ron Hensley r...@dmv.com *
* Junior Systems Administrator http://www.dmv.com/~ron *
* PGP Key at WWW Page *
* DelMarVa OnLine 749-7898 Ext. 403 *
*******************************************************************

[Reinhold J. Gerharz]

in...@azurix.rz.tu-clausthal.de (Lutz Kotoll) wrote:

<deleted>

>please give more helpful advices next time

Perhaps you would prefer NO advice at all.

[Mark V. Dalton]

Emiliano wrote:

> You guys probably have a line like
>
> + "I" Module FvwmAuto 500
>
> specified in your InitFunction and RestartFunction (.fvwmrc). Try
> commenting it out.
>

> --
> Bye,
>
> Emile

I'm a newbie to Red Hat Linux and Metro-X. Can someone tell me where
the file that specifies the root window menu(s) is kept if no .fvwmrc
file is present in the login home directory? I'd like to use the
currently supplied default file as a model but I can't seem to locate
it.

Thanks for any tips supplied.

--
Best Regards,

Mark V. Dalton
1-301-470-4796

[Matthew Cravit]

In article <323455...@lmco.com>,

Mark V. Dalton <mark....@lmco.com> wrote:

>the file that specifies the root window menu(s) is kept if no .fvwmrc
>file is present in the login home directory? I'd like to use the
>currently supplied default file as a model but I can't seem to locate
>it.

Assuming Red Hat puts things in the same place Slackware does, the file
is in /usr/X11/lib/X11/fvwm/system.fvwmrc.

/MC
--
--
Matthew Cravit, N9VWG | Experience is what allows you to
E-mail: mcr...@best.com (home) | recognize a mistake the second
mcr...@adobe.com (work) | time you make it.

[Robert Nation 885-9815]

>how is the following behavior achieved:
>
>- a window gets focus with a click-action in it (perhaps click into the client
>area) -- but it doesn't raise

I thought I already answered this once, but maybe I'm hallucinating....

If you recompile with the option CLICKY_MODE_1 defined, then the window should
only be raised if you click on the border to focus. Clicking in the interior
of the window causes it to be focused but not to raise.

>- a window raises with another click-action (perhaps click onto some border
>elements) -- it may receive focus too but it it needn't be, you then have an
>additional possibility for personal configuration

Its best to click on the border for this, or else use some obscure
modifier combination, ie shift-alt-ctrl-button1 = raise window.

Rob

[Zebee Johnstone]

On Mon, 09 Sep 1996 13:33:53 -0400, "Mark V. Dalton" <mark....@lmco.com> wrote:
>
>I'm a newbie to Red Hat Linux and Metro-X. Can someone tell me where

>the file that specifies the root window menu(s) is kept if no .fvwmrc
>file is present in the login home directory? I'd like to use the
>currently supplied default file as a model but I can't seem to locate
>it.
>

If there is no .fvwmrc, then look for a file in the home dir (/root)
called .Xclients.

also check .Xdefaults and .xsession

Zebee

[Nir Soffer]

Ron Hensley (r...@scorpio.dmv.com) wrote:
: >This usually gives me the desired effect with two button clicks and

: >key press. This works because Raise and Lower to not change which
: >window has focus.
: >
: >I hope this is helpful to someone.
: > Fred GC.

: All you should need is to comment out:
: #ClickToFucus
: and uncomment
: AutoRaise 500

: Thats all i did on both BSDI and on Linux and works just fine

AFAIK these have been disabled in fvwm2 , I think that was what he meant,
was it not?

: --

: *******************************************************************
: * Ron Hensley r...@dmv.com *
: * Junior Systems Administrator http://www.dmv.com/~ron *
: * PGP Key at WWW Page *
: * DelMarVa OnLine 749-7898 Ext. 403 *
: *******************************************************************

--
--
Nir Soffer AKA ScorpioS. scor...@cs.huji.ac.il
"Cry havoc, and let slip the dogs of war!"
- William Shakespeare, "Julius Caesar", Act III, Scene 1

[Michal Jaegermann]

Matthew Cravit (mcr...@best.com) wrote:
: In article <323455...@lmco.com>,
: Mark V. Dalton <mark....@lmco.com> wrote:
:
: >the file that specifies the root window menu(s) is kept if no .fvwmrc

: >file is present in the login home directory?

:
: Assuming Red Hat puts things in the same place Slackware does, the file
: is in /usr/X11/lib/X11/fvwm/system.fvwmrc.

Red Hat is pretty consistent in supplying at least links to various
system configuration files from subdirectories of /etc. Chec
/etc/X11.

--mj

[Hal L. DeVore Jr.]

In article <slrn53c1b9...@tigger.cae.com.au>,

ze...@tigger.cae.com.au (Zebee Johnstone) writes:
> On Mon, 09 Sep 1996 13:33:53 -0400, "Mark V. Dalton" <mark....@lmco.com> wrote:
>>
>>I'm a newbie to Red Hat Linux and Metro-X. Can someone tell me where

>>the file that specifies the root window menu(s) is kept if no .fvwmrc

>>file is present in the login home directory? I'd like to use the
>>currently supplied default file as a model but I can't seem to locate
>>it.
>>
>
> If there is no .fvwmrc, then look for a file in the home dir (/root)
> called .Xclients.
>
> also check .Xdefaults and .xsession

Well, those are quite useful files but have nothing to do with what Mark was
asking.

man fvwm

contains the correct answer...

INITIALIZATION
During initialization, fvwm will search for a configura-
tion file which describes key and button bindings, and a
few other things. The format of these files will be
described later. First, fvwm will search for a file named
.fvwmrc in the users home directory. Failing that, it will
look for /usr/lib/X11/fvwm/system.fvwmrc for system-wide
defaults. If that file is not found, fvwm will exit.

And, FWIW, fvwm2 is superior IMHO to fvwm. There's a nice packaged up "rpm"
of it in the Red Hat contrib ftp directory:
ftp://ftp.redhat.com/pub/contrib/RPMS/fvwm2*

--

Hal DeVore | hde...@bmc.com ---- PGP Key fingerprint
BMC Software, Inc. | EA A3 2F 62 98 38 B0 15 F0 85 76 33 E1 5A 2A 64
Houston, TX USA | <*> Most apologizing, mathematics not Zathras skill.

Hal DeVore | hde...@bmc.com ---- PGP Key fingerprint
BMC Software, Inc. | EA A3 2F 62 98 38 B0 15 F0 85 76 33 E1 5A 2A 64
Houston, TX USA | <*> Most apologizing, mathematics not Zathras skill.

[Jani Jaakkola]

In article <RNATION.96Sep10104130@porgy>,

rnation@porgy (Robert Nation 885-9815) writes:

> I thought I already answered this once, but maybe I'm hallucinating....
>
> If you recompile with the option CLICKY_MODE_1 defined, then the window should
> only be raised if you click on the border to focus. Clicking in the interior
> of the window causes it to be focused but not to raise.
>
>>- a window raises with another click-action (perhaps click onto some border
>>elements) -- it may receive focus too but it it needn't be, you then have an
>>additional possibility for personal configuration
>
> Its best to click on the border for this, or else use some obscure
> modifier combination, ie shift-alt-ctrl-button1 = raise window.
>
> Rob

I made a patch to fvwm95-2 which allows me to
- Raise window with left mouse button click
- Set focus (_No raise_ ) with middle mouse button click
- Lower window with right mouse click

but it needed patches to sources. As far as i know it can't be done
with just changing .fvwmrc or even with CLICK_MODE_1

When i have time, i'll finish the patch and release it, but it is not
going to happen this weekend :)

BTW, rob thanks for fvwm. I love it.

- Jani

[J. Maynard Gelinas]

[responce at bottom]

Zebee Johnstone (ze...@tigger.cae.com.au) wrote:

: On Mon, 09 Sep 1996 13:33:53 -0400, "Mark V. Dalton" <mark....@lmco.com> wrote:
: >
: >I'm a newbie to Red Hat Linux and Metro-X. Can someone tell me where
: >the file that specifies the root window menu(s) is kept if no .fvwmrc
: >file is present in the login home directory? I'd like to use the
: >currently supplied default file as a model but I can't seem to locate
: >it.
: >

: If there is no .fvwmrc, then look for a file in the home dir (/root)
: called .Xclients.

: also check .Xdefaults and .xsession

: Zebee

That's just plain wrong. You want

/usr/X11R6/lib/X11/fvwm/system.fvwmrc

copy this file to your home directory as .fvwmrc and edit it to
your liking.

-jmg