01-31-2008
That is not strange behavior at all if you have "set -o vi" in your profile. Hitting escape at the command line puts you in line command vi mode, so you can edit your command before executing it; hitting vi brings up the full vi editor.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
When I login to a specific machine (running Solaris 2.8; actually serveral machines behave this way), with a known good account, I don't get any shell prompt, and no screen responses to various commands such as ID and PWD. Any ideas on what is causing this, and how to change this behavior? (2 Replies)
Discussion started by: Mufasa
2 Replies
2. UNIX for Dummies Questions & Answers
Hi, I´m using SCO Unix 5.0.5 and I want to configure de variable PS1, so when I type the command:
cd /etc/
the prompt shows
/etc/_>
Is that possible with sh shell? I´ll appreciate your help.
Thanks, a Happy New Year! (1 Reply)
Discussion started by: diegoe
1 Replies
3. UNIX for Dummies Questions & Answers
currently, I set my prompt in my .cshrc file as:
set prompt = "%B%h %m %P %/ \n% "
I have to use certain shells for some specific tasks and would like to set different prompts depending on the type of shell that I am using. Any advice?
Thanks (3 Replies)
Discussion started by: dranNfly
3 Replies
4. UNIX for Dummies Questions & Answers
Does anyone of you know how to turn off color and weird characters on bash shell when using the command "script"? Everytime users on my server used that command to record their script, they either couldn't print it because lp kept giving the "unknown format character" messages or the print paper... (1 Reply)
Discussion started by: Micz
1 Replies
5. Shell Programming and Scripting
Hi,
I want to change the shell prompt, using the cd command.
I have a shell prompt like this -
p78-mfx(dgaw1078/9781)$
Now i do this -
p78-mfx(dgaw1078/9781)$ cd log4j
here the shell prompt should change like this -
p78-mfx(dgaw1078/9781)log4j$ (6 Replies)
Discussion started by: arunkumarmc
6 Replies
6. AIX
here is the one of the scripts:
script1.kshfunction haha
{
print "calling haha"
exit
}
script2.ksh. script1.ksh
haha | tee -a /dev/null
print "i am script 2"
after launching the script2, the result:
---------------------------------------------
calling haha
i am script 2
... (6 Replies)
Discussion started by: getter
6 Replies
7. Shell Programming and Scripting
sqlLogftp_mov=$LOGDIR/logftp_mov_$mydate.log
sqlplus -s $ORAUSER << EOF > $sqlLogftp_mov
SET SERVEROUT ON
@/$SCRIPTDIR/rep_comm_ext_tbl_load.sql
EOF
retorno=0
cnt=`grep -q 'ORA-' $sqlLogftp_mov | wc -l`
if ;
then
retorno=1
echo 'Failure'
sendEmailFalha
exit 1
fi
if ;
then
echo... (8 Replies)
Discussion started by: shyamaladevi
8 Replies
8. Shell Programming and Scripting
I just finish the shell script .
This shell can replace weird characters (such as #$%^@!'"...) in file or directory name by "_"
I spent long time on replacing apostrophe in file/directory name
added: 2012-03-14
the 124th line (/usr/bin/perl -i -e "s#\'#\\'#g" /tmp/rpdir_level$i.tmp) is... (5 Replies)
Discussion started by: begonia
5 Replies
9. Shell Programming and Scripting
I have a script named check which will read the content of a file and check wether those files exist in the current directory. If so it will have the exit status of 0, otherwise it will have 1.
check script:
#!/bin/bash
if ; then #Check there is enough command line parameters.
exit 1... (2 Replies)
Discussion started by: Ray Sun
2 Replies
10. AIX
Dear all experts,
I have a script written to compress a list of files, during compressing, some of the files are having same name. When the compressing started, the same name file will be prompted with message whether to overwrite the old file. I need to enter "y" to continue.
Is there any way I... (7 Replies)
Discussion started by: kwliew999
7 Replies
EX(1) General Commands Manual EX(1)
NAME
ex, edit - text editor
SYNOPSIS
ex [ - ] [ -v ] [ -t tag ] [ -r ] [ +command ] [ -l ] name ...
edit [ ex options ]
DESCRIPTION
Ex is the root of a family of editors: edit, ex and vi. Ex is a superset of ed, with the most notable extension being a display editing
facility. Display based editing is the focus of vi.
If you have not used ed, or are a casual user, you will find that the editor edit is convenient for you. It avoids some of the complexi-
ties of ex used mostly by systems programmers and persons very familiar with ed.
If you have a CRT terminal, you may wish to use a display based editor; in this case see vi(1), which is a command which focuses on the
display editing portion of ex.
DOCUMENTATION
The document Edit: A tutorial (USD:14) provides a comprehensive introduction to edit assuming no previous knowledge of computers or the
UNIX system.
The Ex Reference Manual - Version 3.7 (USD:16) is a comprehensive and complete manual for the command mode features of ex, but you cannot
learn to use the editor by reading it. For an introduction to more advanced forms of editing using the command mode of ex see the editing
documents written by Brian Kernighan for the editor ed; the material in the introductory and advanced documents works also with ex.
An Introduction to Display Editing with Vi (USD:15) introduces the display editor vi and provides reference material on vi. In addition,
the Vi Quick Reference card summarizes the commands of vi in a useful, functional way, and is useful with the Introduction.
FILES
/usr/share/misc/exstrings error messages
/usr/libexec/exrecover recover command
/usr/sbin/expreserve preserve command
/etc/termcap describes capabilities of terminals
~/.exrc editor startup file
/tmp/Exnnnnn editor temporary
/tmp/Rxnnnnn named buffer temporary
/usr/preserve preservation directory
SEE ALSO
awk(1), ed(1), grep(1), sed(1), grep(1), vi(1), termcap(5), environ(7)
AUTHOR
Originally written by William Joy
Mark Horton has maintained the editor since version 2.7, adding macros, support for many unusual terminals, and other features such as word
abbreviation mode.
BUGS
The undo command causes all marks to be lost on lines changed and then restored if the marked lines were changed.
Undo never clears the buffer modified condition.
The z command prints a number of logical rather than physical lines. More than a screen full of output may result if long lines are
present.
File input/output errors don't print a name if the command line `-' option is used.
There is no easy way to do a single scan ignoring case.
The editor does not warn if text is placed in named buffers and not used before exiting the editor.
Null characters are discarded in input files, and cannot appear in resultant files.
4th Berkeley Distribution October 21, 1996 EX(1)