10-03-2002
try typing fg and the command prompt
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
LEARN ABOUT HPUX
gettydefs
gettydefs(4) Kernel Interfaces Manual gettydefs(4)
NAME
gettydefs - speed and terminal settings used by getty
DESCRIPTION
The file contains information used by to set up the speed and terminal settings for a line (see getty(1M)). It supplies information on
what the prompt should look like. It also supplies the speed to try next if the user indicates the current speed is not correct by typing
a Break character.
Each entry in has the following format:
Each entry is followed by a blank line. The various fields can contain quoted characters of the form etc., as well as where nnn is the
octal value of the desired character. The various fields are:
label This is the string against which tries to match its second argument. It is often the speed, such as at which the terminal
is supposed to run, but it need not be (see below).
initial-flags These flags are the initial settings to which the terminal is to be set if a terminal type is not specified to (see
ioctl(2)). The flags that understands are the same as the ones listed in (see termio(7)). Normally only the speed flag is
required in the initial-flags. automatically sets the terminal to raw input mode and takes care of most of the other flags.
The initial-flag settings remain in effect until executes
final-flags These flags take the same values as the initial-flags and are set just before executes The speed flag is again required.
The composite flag takes care of most of the other flags that need to be set so that the processor and terminal are communi-
cating in a rational fashion. The other two commonly specified final-flags are so that tabs are sent to the terminal as
spaces, and so that the line is hung up on the final close.
login-prompt This entire field is printed as the login-prompt. Unlike the above fields where white space is ignored (a space, tab or
new-line), they are included in the login-prompt field.
next-label If this entry does not specify the desired speed, indicated by the user typing a Break character, searches for the entry
with next-label as its label field and set up the terminal for those settings. Usually, a series of speeds are linked
together in this fashion, into a closed set. For example, linked to which in turn is linked to which finally is linked to
If is called without a second argument, the first entry of is used, thus making the first entry of the default entry. It is also used if
cannot find the specified label. If itself is missing, there is one entry built into the command which brings up a terminal at baud.
It is strongly recommended that after making or modifying it be run through with the check option to ensure that there are no errors.
EXAMPLES
The following two lines show an example of 300/1200 baud toggle, which is useful for dial-up ports:
The following line shows a typical 9600 baud entry for a hard-wired connection:
FILES
SEE ALSO
getty(1M), login(1), ioctl(2), termio(7).
gettydefs(4)