Bug 82998 - xterm -wf doesn't wait for map
xterm -wf doesn't wait for map
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
8.0
i586 Linux
medium Severity medium
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
: MoveUpstream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-29 08:32 EST by Ian Collier
Modified: 2007-04-18 12:50 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-01-29 08:39:53 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ian Collier 2003-01-29 08:32:50 EST
Description of problem:
The "-wf" option as documented in the xterm manual page doesn't work.

Version-Release number of selected component (if applicable):
XFree86-4.2.0-72, although this is a problem on all releases of
Red Hat from 6 onwards (but my 5.1 box works fine).

How reproducible:
Always

Steps to Reproduce:
1. Use a window manager (such as fvwm) which allows interactive
   placing of new windows
2. type: xterm -wf -e sh -c 'sleep 5;echo hello;sleep 5'
3. wait 8 seconds before placing the new window.
    
Actual results:
The new window already says "hello" and quickly disappears.

Expected results:
The new window should be blank for five seconds, then say "hello"
and remain for five further seconds.

Additional info:
This can be fixed by using the flag -DUSE_HANDSHAKE while compiling
xterm/main.c.
Comment 1 Mike A. Harris 2003-01-29 08:39:53 EST
Please report this directly to xfree86@xfree86.org for attention of the
xterm maintainer.  If this is something that needs to be fixed, he is the
one best suited to determine the proper fix and get it into XFree86 CVS
in time for 4.3.0.

We provide xterm only for convenience as it is a historical legacy
application some users prefer.  We do not directly support it however.

Note You need to log in before you can comment on or make changes to this bug.