On Sun, 4 May 2008, Thomas Dickey wrote:
On Sun, 4 May 2008, Thomas Adam wrote:
On 04/05/2008, [EMAIL PROTECTED]
[...]
If you think this problem is cured in 2.4.25, I am glad to try it. But I
bet it is not. The problem is as I said one of those weird problems that I
But this doesn't have anything to do with FVWM.
As I said, it happens with FVWM but cannot be repeated with KDE. This
implies that FVWM and KDE are doing something differently. It also happens
if one starts a "bare" X session. You know, the default which is done if
one has no window manager at all. Just one xterm open and nothing else.
From this I would conclude
-- FVWM is doing the same default settings as the "bare" X, at least in
this regard. This may be the "right" behavior, and there may be
nothing "wrong" in this behavior at all.
-- KDE is doing something else, which changes those default settings. This
could conceivably be the "wrong" behavior on the part of KDE. In that case
it manages to bypass the problem, somehow.
Therefore, it does have "something" to do with FVWM. I did not say it is a
bug in FVWM.
OK, I am not using
Slackware, but neither can I reproduce it, and I can't say I am
surprised. There is nothing inherently weird in starting a termina,
typing in su and then for it to mangle your bindings.
It's -possible- it's something to do with XTerm, such as settings for
its resource for thing like:
eightBitInput
eightBitControl
And you perhaps not having set:
XTerm*metaSendsEscape: true
In your ~/.Xdefaults --- but this would explain really why you see
this when you su.
Hmmm. I looked now all over the system in all reasonable places for an
Xdefaults file, found none. I also have no $HOME/.Xdefaults file at all.
This is what man X has to say about such things:
"XENVIRONMENT
This must point to a file containing X resources. The default is
$HOME/.Xdefaults-<hostname>. Unlike /usr/lib/X11/Xresources, it
is consulted each time an X application starts. "
in which it seems that the last sentence is most relevant, here.
Actually, this seems to have fixed the problem. I have done the following
steps:
1. created a file called .Xdefaults and put in it the one line
XTerm*metaSendsEscape: true
and then
2. Exited from X and restarted, then run the same test. At this point the
Alt key is doing right.
That would be a reasonable possibility if he started a new xterm after
doing su,
I did not. And that is not what the man page says, it seems.
but I don't see that in the description (it sounds as if he's
running in the same xterm).
That is right. It is the same xterm.
There is a control sequence in xterm which can change this mode, but
I'd be surprised if mc is using it.
I don't believe so.
Perhaps root's $TERM is set differently - or $TERMINFO and/or $TERMINFO_DIRS
are set. It's not unusual for root's login scripts
to set $TERM
In the window in which one has performed su, the command
echo $TERM
produces the response
xterm
Clearly I could check the other two items. But it seems that the problem
is now cured.
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
Thanks for the suggestions. One of them worked. Also thanks for my
question being answered promptly, and with courtesy. If you come to ask
questions about a USB digital camera, I will try to act the same.
I do agree that the problem is not with fvwm. Still, there is the issue
that KDE manages to avoid choking on the same problem. Therefore, I would
not go so far as to say that it has "nothing to do with FVWM." I do not
think I would have that point of view if I were involved with your
project. I am not involved there. I know that.
But I am very much involved in the Gphoto project. I do quite a bit of
support for cameras, especially those cheap ones at places like Wal-Mart
which come with proprietary communication protocols and are advertised for
Windows only. So if you are having a problem with one of those things, you
and I will switch hats. You will be coming to some place like the
gphoto-users or gphoto-devel list, and I may be the one who works with you
to support your camera.
If some kind of funny business is happening at some basic
level and falls into my purview because it deals with the software that I
wrote, it does bother me. If I were in your shoes, I would truly try to
figure out some way how to bypass the problem as KDE does. I would do that
because a problem like this is one of those kinds of little things that
can drive a user nuts. And few of them are going to be as patient as I am
in trying to hunt the solution.
As much as time permits, I am quite willing to help you test a solution to
this, which could be somehow be packaged with or incorporated into the
FVWM release, so that a user is not faced with the need to chase down
such a stupid problem in the future.
Cheers,
Theodore Kilgore
