Re: FVWM: Ban area for window placement

[Renato Caldas]

On Tue, Nov 4, 2008 at 9:04 PM, Jesús Guerrero <[EMAIL PROTECTED]> wrote:
> I've had such a setup with two screens (1600x1200 and 1204x768) for a long 
> time
> and using fvwm. Never had a problem with it.
>
> so I suspect it's something to do with xorg not being configured correctly. 
> Unless
> you didn't compile fvwm with proper xinerama support.
>
> Well, I was using nvidia's twinview, but that should be irrelevant.

It's not irrelevant. Nvidia twinview is not xinerama, it actually
creates two X screens.

Moreover, I believe xinerama is conceptually broken for modern X.
You're better off with two screens configured side by side (think
xrandr), but unfortunately fvwm doesn't handle these "modern" setups
correctly...

Cheers,
  Renato

Re: FVWM: Ban area for window placement

[Renato Caldas]

On Wed, Nov 5, 2008 at 12:57 AM, Jesús Guerrero <[EMAIL PROTECTED]> wrote:
> On Wed, 5 Nov 2008 00:39:36 +
> "Renato Caldas" <[EMAIL PROTECTED]> wrote:
>
>> On Tue, Nov 4, 2008 at 9:04 PM, Jesús Guerrero <[EMAIL PROTECTED]> wrote:
>> > I've had such a setup with two screens (1600x1200 and 1204x768) for a long 
>> > time
>> > and using fvwm. Never had a problem with it.
>> >
>> > so I suspect it's something to do with xorg not being configured 
>> > correctly. Unless
>> > you didn't compile fvwm with proper xinerama support.
>> >
>> > Well, I was using nvidia's twinview, but that should be irrelevant.
>>
>> It's not irrelevant. Nvidia twinview is not xinerama, it actually
>> creates two X screens.
>
> I don't know what do you mean by "two screens". But it's not like using dual
> head, it behaves and act by all means like xinerama (you can take one window
> from one monitor and drop it into the other monitor, and you can resize it so
> part of the window is on each monitor).

I shouldn't be talking about "screens" but about "monitors". The
nvidia twinview is not xinerama, but a similar xorg extension, and I'm
having some trouble with the binary blob...

The "modern" extension you want is xrandr 1.2, which comes to replace
xinerama. I believe it is a dual head setup, meaning that there is a
notion of individual "monitors". The binary blob doesn't currently
support xrandr 1.2 AFAIK.

I've tested it successfully with the open-source "nouveau" driver.
Unfortunately the video memory is currently limited to a 1280x1280
total screen area, which prevents more than two 640x480 side by side
monitors... I believe this limitation is arbitrary, but I can't seem
to find who sets the limit...

Anyway, here are a bunch of sites full of interesting information.

http://www.x.org/wiki/Projects/XRandR
http://en.wikipedia.org/wiki/Xinerama

Cheers,
  Renato

> Regards.
> --
> Jesús Guerrero <[EMAIL PROTECTED]>
>

Re: FVWM: keys don't repeat

[Renato Caldas]

On Sat, Dec 6, 2008 at 3:55 PM, Theodore D. Sternberg
<[EMAIL PROTECTED]> wrote:
> On Sat, 6 Dec 2008, Dominik Vogt wrote:
>>
>> If that does not work, some other program or command is switching
>> it off.  Are you sure there is no "xset r off" in your .fvwm2rc?
>
> Nope.  Keys used to repeat until I upgraded my OS from SuSE 10.2 to
> SuSE 11.0.  Moreover, keys do repeat if I run the gnome desktop.
> In the end, I solved the problem by putting xset r on in .bashrc.

It is possible that the gnome desktop is actively turning on key repetition...

I've seen this behavior with Mandrake for the root user. I have little
idea on where that was set up, but it seemed to be a "security"
feature set system-wide. I assume you're not running as root, right?
You could probably check the system files sourced by .bashrc if any of
them is turning repetition off, and then file a bug report to SuSE..

Cheers,
  Renato