01-22-2018
The vim (and vi) utility always starts in command mode. One might guess that the default terminal setting (i.e. TERM=terminal_type) differs on some of your servers and the escape sequence being generated for the up-arrow key on your terminal is being interpreted differently as a result. My guess would be that the escape sequence for that key includes an "a" or "i" or other vim command that puts you in insert mode when TERM is set to something like "dumb" or to a terminal type that does not match whatever terminal type Putty is emulating.
This User Gave Thanks to Don Cragun For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi. Thanks for any help with this. I'm not new to programming but I am new to shell programming. I need a script that will
1. execute 'df -k' and return the volume names with specific text
2. surround each line of the above results in opening and closing xml tags
3. insert the results of step... (5 Replies)
Discussion started by: littlejon
5 Replies
2. Shell Programming and Scripting
Hi,
I need to send "^[" command to the buffer.
I tried to use insert within VIM and press 'ctrl' key and then '^' and '[' key.
but it didn't work.
Does anyone know how to do it?
Thanks a lot!
Julie (2 Replies)
Discussion started by: cin2000
2 Replies
3. UNIX for Dummies Questions & Answers
Hi,
When working in vi, the CTRL+j command for merging lines is very convenient. Is there an equivalent for splitting them (inserting a line break)? I often find myself pressing "i" + "return" + "esc", which I find a bit lengthy.
Thanks in advance! (3 Replies)
Discussion started by: Skogsmulle
3 Replies
4. UNIX for Dummies Questions & Answers
Hi all,
I am very new to this forum and also new to UNIX.
I am working on HP-UX machine. I noticed that for some of the users I am unable to insert the # character in a file in vi mode.
May I know y am I having the problem and how can I resolve this
Thanks,
Maroli (1 Reply)
Discussion started by: maroli
1 Replies
5. UNIX for Dummies Questions & Answers
While using vi or vim on different boxes, I experience different behaviors when I'm inserting (i) or writing on a new line (o). On the Linux box, I can insert and delete with my backspacekey while in the insert mode. It acts a little more like pico,nedit, etc. On the SunOS box, it's a headache... (3 Replies)
Discussion started by: mrwatkin
3 Replies
6. Shell Programming and Scripting
Hi All,
I was looking to open a file using vim within shell script. Can someone please suggest a way/syntax for this?
Thanks in advance. (5 Replies)
Discussion started by: jal_capri
5 Replies
7. Solaris
I downloaded vim.7.2 and compiled the vim source .
Added the vim binary path to PATH (Because iam not the root of the box)
when i load the file using vim it throws me an error
Error detected while processing /home2/e3003091/.vimrc:
line 2:
E185: Cannot find color scheme darkblue
line... (0 Replies)
Discussion started by: girija
0 Replies
8. Shell Programming and Scripting
How can I insert the command executed on the shell into the first line of my output file?
For example if I execute;
zcat *.gz |grep “User5501” > users.out
How can I make my users.out look like;
zcat *.gz |grep “User5501” > users.out
User5501 PA
User5501 UA
User5501 ZA... (3 Replies)
Discussion started by: lewk
3 Replies
9. Shell Programming and Scripting
how can i search each line for ROCT and ROCT1.ROCT1 will be always 1 line after ROCT.
Both the patterns will be found at the end of the line (in alternate lines)
<pattern file>
(rising edge-triggered flip-flop clocked by ROCT)
Endpoint:... (2 Replies)
Discussion started by: dll_fpga
2 Replies
10. Shell Programming and Scripting
I would like to execute and external command and insert it into a particular area of the file I am editing. Note that I have the ORIGINAL AT&T vi training doc dated 1987. Doesnt explain it.
As an example, in a vi editor I have
I would like the result :
After executing the following... (1 Reply)
Discussion started by: popeye
1 Replies
UL(1) BSD General Commands Manual UL(1)
NAME
ul -- do underlining
SYNOPSIS
ul [-i] [-t terminal] [file ...]
DESCRIPTION
The ul utility reads the named files (or standard input if none are given) and translates occurrences of underscores to the sequence which
indicates underlining for the terminal in use, as specified by the environment variable TERM. The file /etc/termcap is read to determine the
appropriate sequences for underlining. If the terminal is incapable of underlining, but is capable of a standout mode then that is used
instead. If the terminal can overstrike, or handles underlining automatically, ul degenerates to cat(1). If the terminal cannot underline,
underlining is ignored. During the translation some other special characters also get translated. E.g. TAB gets expanded to spaces.
The following options are available:
-i Underlining is indicated by a separate line containing appropriate dashes '-'; this is useful when you want to look at the underlin-
ing which is present in an nroff(1) output stream on a CRT-terminal.
-t terminal
Overrides the terminal type specified in the environment with terminal.
ENVIRONMENT
The LANG, LC_ALL, LC_CTYPE and TERM environment variables affect the execution of ul as described in environ(7).
EXIT STATUS
The ul utility exits 0 on success, and >0 if an error occurs.
SEE ALSO
colcrt(1), man(1), nroff(1)
HISTORY
The ul command appeared in 3.0BSD.
BUGS
The nroff(1) command usually outputs a series of backspaces and underlines intermixed with the text to indicate underlining. No attempt is
made to optimize the backward motion.
BSD
August 4, 2004 BSD