Sponsored Content
Top Forums UNIX for Dummies Questions & Answers color in emacs... when ssh-ing to my FreeBSD box Post 6330 by LivinFree on Monday 3rd of September 2001 09:23:48 PM
Old 09-03-2001

I use putty to connect to all the Unices at work. I get color on the Slackware boxes (that support it), and my terminal type string is simply set to "xterm" (no quotes). If that doesn't work, try executing (from the console): echo $TERM. Now, set whatever the value of TERM is as your terminal type string in putty. Hope it works!

 

8 More Discussions You Might Find Interesting

1. Red Hat

ssh-ing to port 80.

i am using redhat 8.0 and trying to connect to my local port 80 to run some HTTP. i know this can easily be done with telnet localhost 80, however telnet is not running, ssh is. ssh localhost -p 80 gives me a "Connection refused" error. i've been trying to find out more information on the web,... (3 Replies)
Discussion started by: effigy
3 Replies

2. UNIX for Dummies Questions & Answers

Emacs color syntax highlighting

So... i cant get it to work. I had already posted this but it got deleted. Details: Im running SSH shell on Windows XP, connecting to a server whose term is vt100 (someone asked me that last time) Im trying to get the syntax highlighting in cc mode to work in color, but its black and... (0 Replies)
Discussion started by: viejid
0 Replies

3. UNIX for Advanced & Expert Users

Access files from prev box after SSH to another box

i'm not much of an advanced unix programmer but I'm trying to write a script to access files on box1 after ssh from box 1 to box2. when ssh is invoked in the script i'm getting logged into box2 and losing complete touch with box1 which is normal i guess. but my main aim with my script is when i... (3 Replies)
Discussion started by: pharos467
3 Replies

4. OS X (Apple)

Emacs set-cursor-color in iTerm problem

Hi I'm trying to customise emacs to work within iTerm (I've aliased emacs = emacs -nw so it runs inside my shell) but I can't get the 'set-cursor-color' to work. I have the following in my .emacs file: (set-cursor-color "LightSkyBlue") ... (0 Replies)
Discussion started by: pepperjacl
0 Replies

5. Shell Programming and Scripting

grep'ing and sed'ing chunks in bash... need help on speeding up a log parser.

I have a file that is 20 - 80+ MB in size that is a certain type of log file. It logs one of our processes and this process is multi-threaded. Therefore the log file is kind of a mess. Here's an example: The logfile looks like: "DATE TIME - THREAD ID - Details", and a new file is created... (4 Replies)
Discussion started by: elinenbe
4 Replies

6. UNIX for Dummies Questions & Answers

Public Key Authentication over SSH and Sudo-ing Implementation

Hi, We are currently implementing an Identity Management application which has several Unix systems as its target system. A pre-defined connector will be installed to provide connection between the Identity Management application and the Unix target system. The connection will use Public Key... (1 Reply)
Discussion started by: tristanD
1 Replies

7. Red Hat

cannot ssh (use NFS) on RHEL box, but can mount external & ssh out of RHEL box

Ok, Im trying to get NFS working on my RHEL 5 box, apparently i can use the box as a client, but not as a server. If it helps i cant ssh into the box (server), but as a client ssh works fine. Ive configured server: /etc/hosts.allow: all : all all :all@all setup my /etc/exports file... (4 Replies)
Discussion started by: drs.grid
4 Replies

8. UNIX for Dummies Questions & Answers

How to use emacs? Also how to open existing emacs files with .cgi format?

Hi All, I am new to this forum and a beginner in unix. Please correct me if I put the question in a wrong way.. How to use emacs editor? Also how to open existing emacs files with .cgi format? I have the following link :- http link i.e. url and path : /abc/xyz.dev/xyz/documents What... (7 Replies)
Discussion started by: swathi123
7 Replies
ttytype(1)						      General Commands Manual							ttytype(1)

NAME
ttytype - terminal identification program SYNOPSIS
type] DESCRIPTION
automatically identifies the current terminal type by sending an identification request sequence to the terminal. This method works for local, modem, and remote terminal connections, as well as for the and terminal emulators. Once the terminal has been identified, prints the terminal's type to the standard output (see terminfo(4)). This string is usually used as the value for the environment variable. If is unable to determine the correct terminal type, it prompts the user for the correct terminal identification string. Options recognizes the following options: Causes to return an ID of "unknown" instead of prompting for the terminal type if auto-identification fails. If this option is not present, interactively prompts the user for the terminal type if it is unable to determine the correct type automati- cally. Causes to prompt for the terminal type before it sends the terminal identification request sequence. If the user responds with only a carriage return, proceeds with the automatic terminal identification process. Any other response is taken as the correct terminal type. Note that the and variables are not set if the user manually enters a terminal type. The option is normally used only for terminals that do not behave well when presented with terminal identification request sequence. It gives the user a chance to respond with the correct terminal type before any escape sequences are sent that could have an adverse effect on the terminal. The option can be used in conjunction with the option. The option only inhibits interactive prompting after has failed to identify the terminal by other means. Tells to print a series of shell commands to set the and environment variables to appropriate values. In addition, the variable is set to the two-character sequence representing the appropriate erase character for the terminal (DEL for ANSI termi- nals, backspace for all others). This two-character sequence can then be used as an argument to or (see stty(1) and tset(1)). The environment variable is consulted to see which shell syntax to use for setting the environment variables. This output is normally used with a command of the form: normally attempts identification of Wyse, ANSI and HP terminals. The type argument can be used to restrict the inquiry to that required for terminals of the specified type. The accepted types are and Multiple options can be specified. Enable verbose messages to standard error. Notes Use of the option is highly recommended because many terminals support variable-size displays. This option provides the only means for automatically configuring the user environment in such a manner that applications can handle these terminals correctly. Note that and are not set if the option is used and the user manually enters a terminal type. The following steps are performed in the order indicated when identifying a terminal: 1. tries the Wyse 30/50/60 id request sequence. 2. tries the standard ANSI ID request sequence. If a response is received, it is converted to a string according to an internal table. 3. tries the HP id request sequence. 4. If none of the above steps succeed, prompts interactively for the correct terminal type unless the option has been given. may skip one or more of the first three steps, depending on the presence of options. The HP ID request sequence can switch some ANSI terminals into an unexpected operating mode. Recovery from such a condition sometimes requires cycling power on the terminal. To avoid this problem, always sends the HP identification sequence last. EXAMPLES
is most commonly used as part of the login sequence. The following shell script fragment can be used during login shell initialization: # # If TERM is not set, see if our port is listed in /etc/ttytype. # If /etc/ttytype doesn't have information for our port, run # ttytype(1) to try to determine the type of terminal we have. # # To have ttytype(1) prompt for the terminal type before trying # to automatically identify the terminal, add the "-p" option # to the "ttytype -s" command below. # if [ -z "$TERM" -o "$TERM" = network ]; then unset TERM eval `tset -s -Q` if [ -z "$TERM" -o "$TERM" = unknown ]; then eval `ttytype -s` tset -Q -e ${ERASE:-^h} $TERM fi fi WARNINGS
The terminal identification sequences sent by can cause unexpected behavior on terminals other than the Wyse 30/50/60, standard ANSI or HP terminals. If you have such terminals in your configuration, use the or options to prevent from sending sequences that cause unexpected behavior. AUTHOR
was developed by HP. SEE ALSO
csh(1), ksh(1), sh(1), stty(1), ttytype(4), environ(5). ttytype(1)
All times are GMT -4. The time now is 01:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy