Sponsored Content
Full Discussion: Terminal Emulation Issue
Operating Systems Solaris Terminal Emulation Issue Post 302562880 by Corona688 on Saturday 8th of October 2011 06:50:19 PM
Old 10-08-2011
is vt1000 the terminal from the future? Smilie Try VT100
 

10 More Discussions You Might Find Interesting

1. Programming

Terminal Emulation

Hi , I am working on SCO Unix who needs to know some basics concepts about how to write a program that will capture the input , output of one terminal to another ie whatever is being typed as input or echoed as output to terminal say tty02 shall be automatically be falshed to another terminal say... (1 Reply)
Discussion started by: S.P.Prasad
1 Replies

2. UNIX for Dummies Questions & Answers

Terminal Emulation

Hello all, Am new to the forum and hope this post meets the requirements. This post will be rather lengtly but needs to be to explain the problem. I have two computers running Windows 2000 Pro. I travel for a living and use a terminal emulation program called STEP to connect to our Unix... (2 Replies)
Discussion started by: skids
2 Replies

3. BSD

ls -G in terminal emulation

Hi ! As everyone, i installed my system and started "personalizing" it. One of the adjustments was creating an alias in /etc/profile fo ls, so when I type ls it is running ls -G so i can see a colored output. Everything is ok, but after I configured my system to start in X by default (kdm as... (2 Replies)
Discussion started by: Sergiu-IT
2 Replies

4. SCO

Help: Terminal Emulation for SCO Unix...

Question from a newbie: We are running SCO Unix, and are using Century Software Windows Terminal Emulation “Term for Windows” for Win95 v6.3.9b. It used to work fine when we had Win98 on our machines, but now we are updating them with Win2000/XP. This WinTerm works fine on some machines, which... (9 Replies)
Discussion started by: fasal
9 Replies

5. UNIX for Dummies Questions & Answers

terminal emulation displaying in machine language

I entered the command cat 401328 in an attempt to see a file. Now, my screen is displaying machine language. The properties of the file say that it is a postgres application. Is there a command I can enter so everything gets back to normal? Thanks, (2 Replies)
Discussion started by: Debbie
2 Replies

6. UNIX for Dummies Questions & Answers

Differences between Telnet and Terminal Emulation?

HI , I am little confused about differences between Telnet and Terminal Emulation? (1 Reply)
Discussion started by: nixhead
1 Replies

7. AIX

Terminal Emulation- AIX Server- Best Practices

Greetings. We share one AIX server with about 100 users over 4 hub sites via Procomm Plus. Users dvelop bad habits and exit straight out of the terminal window vice correctly logging out of their application session on the server. Sometimes we have to go into the server and terminate their session... (0 Replies)
Discussion started by: pconfig
0 Replies

8. Programming

printer link to terminal emulation

have the following lines in .bash_profile. "ln-s /dev/ttyp0 /dev/lpw10" and ln -s /dev/ttyp0 /dev/lpc10" this allows a terminal emulation running on xp to print locally. I would like to capture the print file and store the output in a directory. Any ideas as to how to capture the print output?... (2 Replies)
Discussion started by: petercp
2 Replies

9. UNIX for Dummies Questions & Answers

Terminal emulation settings help rlogin AIX to SCO

I use a program called TinyTerm to access our AIX machine. It works fine except for when I rlogin into our SCO unix server. Backspace doesn't delete, ctrl-c doesn't work (delete key does same thing), and the most annoying thing is vi acts very wierd. I have to press the down arrow like 3 times to... (11 Replies)
Discussion started by: herot
11 Replies

10. UNIX for Dummies Questions & Answers

Terminal emulation OSX Vs. Solaris 11

I am using Terminal on an OSX system to access and edit crontab files on a 'headless' Solaris 11 server. Crontab -e on OSX invokes vi as the editor, which is fine, but I am getting unexpected characters on keystrokes and have to abort the edit. If this is an emulation issue, would someone please... (1 Reply)
Discussion started by: SmokeyJoe
1 Replies
RESIZE(1)							  X Window System							 RESIZE(1)

NAME
resize - set environment and terminal settings to current xterm window size SYNOPSIS
resize [ -v | -u | -c ] [ -s [ row col ] ] DESCRIPTION
Resize prints a shell command for setting the appropriate environment variables to indicate the current size of xterm window from which the command is run. Resize determines the command through several steps: o first, it finds the name of the user's shell program. It uses the SHELL variable if set, otherwise it uses the user's data from /etc/passwd. o then it decides whether to use Bourne shell syntax or C-Shell syntax. It uses a built-in table of known shells, which can be overrid- den by the -u and -c options. o then resize asks the operating system for the terminal settings. This is the same information which can be manipulated using stty. o then resize asks the terminal for its size in characters. Depending on whether the "-s option is given, resize uses a different escape sequence to ask for this information. o at this point, resize attempts to update the terminal settings to reflect the terminal window's size in pixels: o if the -s option is used, resize then asks the terminal for its size in pixels. o otherwise, resize asks the operating system for the information and updates that after ensuring that the window's dimensions are a multiple of the character height and width. o in either case, the updated terminal settings are done using a different system call than used for stty. o then resize updates the terminal settings to reflect any altered values such as its size in rows or columns. This affects the values shown by stty. o finally, resize writes the shell command for setting the environment variables to the standard output. EXAMPLES
For resize's output to take effect, resize must either be evaluated as part of the command line (usually done with a shell alias or func- tion) or else redirected to a file which can then be read in. From the C shell (usually known as /bin/csh), the following alias could be defined in the user's .cshrc: % alias rs 'set noglob; eval `resize`' After resizing the window, the user would type: % rs Users of versions of the Bourne shell (usually known as /bin/sh) that don't have command functions will need to send the output to a tempo- rary file and then read it back in with the "." command: $ resize > /tmp/out $ . /tmp/out OPTIONS
The following options may be used with resize: -c This option indicates that C shell commands should be generated even if the user's current shell is not /bin/csh. -s [rows columns] This option indicates that Sun console escape sequences will be used instead of the VT100-style xterm escape codes. If rows and columns are given, resize will ask the xterm to resize itself using those values. Both of the escape sequences used for this option (first to obtain the window size and second to modify it) are subject to xterm's allowWindowOps resource setting. The window manager may also choose to disallow the change. The VT100-style escape sequence used to determine the screen size always works for VT100-compatible terminals. VT100s have no cor- responding way to modify the screensize. -u This option indicates that Bourne shell commands should be generated even if the user's current shell is not /bin/sh. -v This causes resize to print a version number to the standard output, and then exit. Note that the Sun console escape sequences are recognized by XFree86 xterm and by dtterm. The resize program may be installed as sunsize, which causes makes it assume the -s option. The rows and columns arguments must appear last; though they are normally associated with the -s option, they are parsed separately. FILES
/etc/termcap for the base termcap entry to modify. ~/.cshrc user's alias for the command. ENVIRONMENT
SHELL Resize determines the user's current shell by first checking if $SHELL is set, and using that. Otherwise it determines the user's shell by looking in the password file (/etc/passwd). Generally Bourne-shell variants (including ksh) do not modify $SHELL, so it is possible for resize to be confused if one runs resize from a Bourne shell spawned from a C shell. TERM Resize sets this to "xterm" if not already set. TERMCAP Resize sets this variable on systems using termcap, e.g., when resize is linked with the termcap library rather than a ter- minfo library. The latter does not provide the complete text for a termcap entry. COLUMNS, LINES Resize sets these variables on systems using terminfo. Many applications (including the curses library) use those variables when set to override their screensize. SEE ALSO
use_env(3) csh(1), stty(1), tset(1) xterm(1) AUTHORS
Mark Vandevoorde (MIT-Athena), Edward Moy (Berkeley) Thomas Dickey (invisible-island.net). Copyright (c) 1984, 1985 by X Consortium See X(7) for a complete copyright notice. Patch #295 2013-07-06 RESIZE(1)
All times are GMT -4. The time now is 02:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy