On Mon, 30 Oct 1995, Greg Veres wrote:
> For all those interested in this problem I was having, I have found that it
> must be the way in which I am starting FVWM that causes the error. To
> refresh memories, the error was that if I launched an xterm from a menu
> item in my .fvwmrc file, I would get an invalid argument error when xterm
> had no errors. There was nothing on the rest of the line in my .fvwmrc file
> so that was not it.
The words "invalid argument" come frequently from stty running in your
.bashrc or .bash_profile (or maybe the system wide ones).
It happens when stty is run, but its parent is not connected to a
tty. The following demonstrates:
$ (stFrom owner-fvwm Mon Oct 30 13:56:48 1995
Return-Path: <owner-fvwm>
Received: by hpc.uh.edu (5.x/SMI-SVR4)
id AA02956; Mon, 30 Oct 1995 13:56:48 -0600
Received: from atlantis.eng.umd.edu by hpc.uh.edu (5.x/SMI-SVR4)
id AA02946; Mon, 30 Oct 1995 13:56:45 -0600
Received: (from rsw_at_localhost) by atlantis.eng.umd.edu (8.7/8.7) id OAA00773; Mon, 30 Oct 1995 14:54:10 -0500 (EST)
Date: Mon, 30 Oct 1995 14:54:06 -0500 (EST)
From: "Randall S. Winchester" <rsw_at_eng.umd.edu>
To: fvwm_at_sina.hpc.uh.edu
Subject: FVWM: Here is a fvwm-2.0.38 bug.
Message-Id: <Pine.SUN.3.91.951030143531.461A-100000_at_atlantis.eng.umd.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-fvwm_at_hpc.uh.edu
Precedence: bulk
Priority: non-urgent
X-Majordomo: 1.92
content-length: 490
When I startup "dclock", and move my mouse over the window, the border
does not change color, as a sign of focus change. If the dclock is very near
an xterm then I can move from the xterm to the dclock and the focus is still
in the xterm. This is very odd behaviour. Other WM's do not have this
problem. Any ideas?
Randall
--
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Mon Oct 30 1995 - 08:08:14 GMT