10-05-2002
Try "!" in command mode in vim. You can execute shell commands from vi mode, using the following syntax.
:!<shell cmd>
You can still remain in vi mode after executing the command.
Deepa
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Here is my problem,
I manage a SunOs 5.8 Server, vi is the default command line
editor, I have a line on each users .kshrc profile as follows:
export EDITOR=/bin/vi
I want to use vim as the command line editor, the below line
doesn't work
export EDITOR=/bin/vim
Thank you (1 Reply)
Discussion started by: tony3101
1 Replies
2. UNIX for Advanced & Expert Users
Hi,
I want to use ctags for multiple folders containing .c and .h files. Can anyone help me with it? I have been using ctags for 1 folder at a time but I would like to link multiple folders and access all .c files at a time using ctags.
Thanks,
shahsm (1 Reply)
Discussion started by: shahsm
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
i am using VIM editor through Putty. By the option of Syntax on in .vimrc file i am able to see syntax colors in .c and .cpp files but not in the files with .pc extension.
How can this be done?
:confused: (2 Replies)
Discussion started by: RuchK
2 Replies
4. Shell Programming and Scripting
Hi All,
I am running a script , working very fine on cmd prompt. The problem is that when I open do crontab -e even after setting editor to vi by
set EDITOR=vi it does not open a vi editor , rather it do as below.....
/////////////////////////////////////////////////////
$ set... (6 Replies)
Discussion started by: aarora_98
6 Replies
5. UNIX for Dummies Questions & Answers
I ran into this issue and thanks to various postings in various forums, was
able to figure out the solution but didn't see one posting that laid the
whole issue out cleanly. So thought the following might help others ...
------------------------------------------------------------------------... (2 Replies)
Discussion started by: oxysep
2 Replies
6. UNIX for Advanced & Expert Users
Hi,
I entered the following text in a new file through vim: "Four score and seven years ago" saved and exit.
When I looked at the file size, it was 31B, although is supposed to be 30. I reedited the file (again with vim) to check for errors, but everything seemed fine. When I opened the file... (3 Replies)
Discussion started by: prostiiinet
3 Replies
7. UNIX for Dummies Questions & Answers
how to turn on the color in vim editor."syntax on" is not working for me.
when i do syntax on it only make some of the text basically header files nd functions name in bold.i am working on "secure crt" ..my vim is in /usr/share
i also have .vimrc file in my home folder "~"
Please help me... (11 Replies)
Discussion started by: ascetic
11 Replies
8. 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
9. UNIX for Dummies Questions & Answers
When i exist the vim editor .. to gives '0' in the console... i think it is status of the exit..
How to disable that ... (14 Replies)
Discussion started by: greenworld123
14 Replies
10. UNIX for Beginners Questions & Answers
Hi,
Whenever i try to open a file in any editor like vi, vim and nano i get this help.txt showing up in split screen without any key being pressed. This continues to pop up even when i close the help.txt. This behavior happens only when i am connected via putty. Is there a fix to this issue?
... (1 Reply)
Discussion started by: sunil0391
1 Replies
sh(1) General Commands Manual sh(1)
NAME
sh - overview of various system shells
SYNOPSIS
POSIX Shell
option] ... string] [arg ...]
option] ... string] [arg ...]
Korn Shell
option] ... string] [arg ...]
option] ... string] [arg ...]
C Shell
[command_file] [argument_list ...]
Key Shell
DESCRIPTION
Remarks
The POSIX .2 standard requires that, on a POSIX-compliant system, executing the command activates the POSIX shell (located in file on HP-UX
systems), and executing the command produces an on-line manual entry that displays the syntax of the POSIX shell command-line.
However, the command has historically been associated with the conventional Bourne shell, which could confuse some users. To meet stan-
dards requirements and also clarify the relationships of the various shells and where they reside on the system, this entry provides com-
mand-line syntax and a brief description of each shell, and lists the names of the manual entries where each shell is described in greater
detail.
The Bourne shell is removed from the system starting with HP-UX 11i Version 1.5. Please use the POSIX shell as an alternative.
Shell Descriptions
The HP-UX operating system supports the following shells:
POSIX-conforming command programming language and command interpreter
residing in file Can execute commands read from a terminal or a file. This shell conforms to current POSIX standards in
effect at the time the HP-UX system release was introduced, and is similar to the Korn shell in many respects. Similar in
many respects to the Korn shell, the POSIX shell contains a history mechanism, supports job control, and provides various
other useful features.
Korn-shell command programming language and commands interpreter
residing in file Can execute commands read from a terminal or a file. This shell, like the POSIX shell, contains a his-
tory mechanism, supports job control, and provides various other useful features.
A command language interpreter
that incorporates a command history buffer, C-language-like syntax, and job control facilities.
Restricted version of the POSIX shell command interpreter.
Sets up a login name and execution environment whose capabilities are more controlled (restricted) than normal user
shells.
restricted version of the Korn-shell command interpreter
Sets up a login name and execution environment whose capabilities are more controlled (restricted) than normal user
shells.
An extension of the standard Korn Shell
that uses hierarchical softkey menus and context-sensitive help.
+--------------+--------------------+
| To obtain: | Use the command: |
+--------------+--------------------+
| POSIX Shell | /usr/bin/sh ... |
| Korn Shell | /usr/bin/ksh ... |
| C Shell | /usr/bin/csh ... |
| Key Shell | /usr/bin/keysh |
+--------------+--------------------+
These shells can also be the default invocation, depending on the entry in the file. See also chsh(1).
WARNINGS
Many manual entries contain descriptions of shell behavior or describe program or application behavior similar to ``the shell'' with a ref-
erence to ``see sh(1)''.
SEE ALSO
For more information on the various individual shells, see:
keysh(1) Key Shell description.
ksh(1) Korn Shell description.
sh-posix(1) POSIX Shell description.
csh(1) C Shell description.
sh(1)