Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

win(1) [bsd man page]

win(1)							      General Commands Manual							    win(1)

NAME
win - Terminal emulator SYNOPSIS
win [-v] [-t name] [command [argument ...]] address OPTIONS
-v If the -v option is present, win prints its version number and date and exits. -tname If the -t option is present, win uses +name as the final part of the tag name of its window. DESCRIPTION
win must be able to connect to a running wily(1). win attaches to a window. If the -t option is present, the final part of the tag name is name. If command is present, the final part of the tag name is +command. Otherwise, the final part of the tag name is +win. The first part of the tag name is the current working directory. win runs a program in a child process. The child process is the leader of a process group and is connected to win by a pseudo-terminal. If command is specified, the child process runs $SHELL -c 'command argument ...' otherwise it runs $SHELL -i If SHELL is not found in the environment, /bin/sh is used. TERM=win is placed in the environment of the running program. Output from the running command appears in the window. The point after the last output from the running command is known as the output point. Further output from the running command appears just before the output point. The output point is initially at the end of the win- dow. Normal wily editing commands work in the window. When a newline, interrupt character, or end-of-file character is created after the output point, the text between the output point and the last newline, interrupt character, or end-of-file character in the window (inclusive) is passed to the running program as input. The interrupt character is control-C and the end-of-file character is control-D. The pseudo-terminal initially is configured so that these are recognized with their normal meanings. The B2 commands beginning with the |, <, or > characters or an upper case letter are executed normally by wily. Other B2 are first termi- nated with a newline, if they are not already, and are then appended to the buffer (and thereafter passed to the running program). RETURNS
win returns zero if it is able to successfully create the child process, otherwise it returns non-zero. EXAMPLES
Run a terminal emulator within wily win Run FTP within wily win ftp Run rlogin within wily win -t host.domain rlogin -8 host.domain SEE ALSO
wily(1) Tag(1) Man(1) BUGS
win doesn't follow changes to the terminal attributes. In particular, there is no way to stop echoing or to change its concept of the interrupt and eof characters. rlogin seems to need -8 and, annoyingly, sets echo and onlcr. The latter can be fixed in your .rcrc: if ( ~ $TERM win ) { stty -echo -onlcr } win doesn't follow changes to the terminal attributes. In particular, there is no way to stop echoing or to change its concept of the interrupt and eof characters. WEdestroy messages aren't yet passed by wily. Thus, Del and Delcol can delete the window yet leave win running. There is a race condition; the user can press newline and then delete text before win has a chance to read it. AUTHOR
win was originally written by Gary Capell (gary@cs.su.oz.au). Alan Watson (alan@oldp.nmsu.edu) rewrote it and added support for arguments, pseudo-terminals instead of pipes, and execution of certain B2 commands by wily. The pseudo-terminal support in 9term, written by Matty Farrow (matty@cs.su.oz.au), was a great help. 1R1.1L1 of 1D1 win(1)

Check Out this Related Man Page

XReparentWindow()														 XReparentWindow()

Name
  XReparentWindow - insert a window between another window and its parent.

Synopsis
  XReparentWindow(display, win, parent, x, y)
	Display *display;
	Window win;
	Window parent;
	int x, y;

Arguments
  display   Specifies a connection to an X server; returned from XOpenDisplay().

  win	    Specifies the ID of the window to be reparented.

  parent    Specifies the window ID of the new parent window.

  x	    Specify the coordinates of the window relative to the new parent.

  y

Description
  XReparentWindow() modifies the window hierarchy by placing window win as a child of window parent.  This function is usually used by a win-
  dow manager to put a decoration window behind each application window.  In the case of the window manager, the new parent window must first
  be created as a child of the root window.

  If win is mapped, an XUnmapWindow() request is performed on it automatically.  win is then removed from its current position in the hierar-
  chy, and is inserted as a child of the specified parent.  win is placed on top in the stacking order with respect to siblings.

  A ReparentNotify event is then generated.  The override_redirect member of the structure returned by this event is set to  either  True  or
  False.  Window manager clients normally should ignore this event if this member is set to True.

  Finally, if the window was originally mapped, an XMapWindow() request is performed automatically.

  Descendants of win remain descendants of win; they are not reparented to the old parent of win.

  Normal  exposure  processing on formerly obscured windows is performed.  The server might not generate exposure events for regions from the
  initial unmap that are immediately obscured by the final map.  The request fails if the new parent is not on the same  screen  as  the  old
  parent, or if the new parent is the window itself or an inferior of the window.

Errors
  BadMatch  parent not on same screen as old parent of win.
	    win has a ParentRelative background and parent is not the same depth as win.
	    parent is win or an inferior of win.

  BadWindow parent is InputOnly and win is not.

See Also
  XCirculateSubwindows(),  XCirculateSubwindowsDown(),	XCirculateSubwindowsUp(),  XConfigureWindow(),	XLowerWindow(),  XMoveResizeWindow(),
  XMoveWindow(), XQueryTree(), XRaiseWindow(), XResizeWindow(), XRestackWindows().

Xlib - Window Manipulation													 XReparentWindow()
Man Page

Featured Tech Videos