03-10-2004
Copy code to vi
Hi,
whenever I copy a code to vi session from other script it just goes weird.
It just goes across the whole screen and looks really bizzare
If the code is small I can manually remove the tabs and indent it correctly but if it is 2000 lines it makes it really difficult.
Is there something I can do about it and how can I copy efficiently without getting the code all over the place.
Your help will be highly appreciated
Thanks
Rooh
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi everyone.. I'm a full-fledged newbie so bear with me. =)
I'm running code in the shell, and I'd like to copy the lines into a text file. Everytime I try using Contrl-C, the lines repeat as code. Is there some sort of export history function I can use? (1 Reply)
Discussion started by: yohoshua
1 Replies
2. UNIX for Dummies Questions & Answers
I have found a question from the exercises of my study mat. The question is
"Why are there a in-core copy and a disk-copy of i-node block and super block?"
If any one know the proper answer then please send me..... (1 Reply)
Discussion started by: dearanik
1 Replies
3. Solaris
Hi Gurus,
I need some help to fulfill the following requirement.
I have a file A and some contents in it and I have file B and some conent in it.
I need to append the contents on File A to FIle B.
I am sure its Basics but missing it.
Thank You,
Rama (1 Reply)
Discussion started by: rama krishna
1 Replies
4. Shell Programming and Scripting
Hi experts
cp bin root src /mnt
but not copy bin/bigfile
any help?
( I post this thread in the "redhat" forum wrongly, I don't know how to withdraw that question in that wrong forum)
Thanks (6 Replies)
Discussion started by: yanglei_fage
6 Replies
5. Shell Programming and Scripting
Heyas
I'm currently attempting to apply the code of tui-select to tui-list.
That is because tui-list simply made a 1 string list, while tui-select uses dynamicly up to 3 strings per line.
Anyway, so i copy pasted the code, and just made the changes marked with red....
Know that both scripts... (2 Replies)
Discussion started by: sea
2 Replies
6. Shell Programming and Scripting
Hi,
I am new to scripting and i am trying to use below script to copy code to multiple servers and multiple locations on each server. the script is not working or doesnt give any error. Any help is appreciated. basically i want a script to get the code from a location (dir below) and read the... (2 Replies)
Discussion started by: Ron0612
2 Replies
script(1) General Commands Manual script(1)
NAME
script - make typescript of terminal session
SYNOPSIS
[file]
DESCRIPTION
makes a typescript of everything printed on your terminal. It starts a shell named by the environment variable, or by default and silently
records a copy of output to your terminal from that shell or its descendents, using a pseudo-terminal device (see pty(7)).
All output is written to file, or appended to file if the option is given. If no file name is given, the output is saved in a file named
The recording can be sent to a line printer later with lp(1), or reviewed safely with the option of cat(1).
The recording ends when the forked shell exits (or the user ends the session by typing "exit") or the shell and all its descendents close
the pseudo-terminal device.
This program is useful when operating a CRT display and a hard-copy record of the dialog is desired. It can also be used for a simple form
of session auditing.
respects the convention for login shells as described in su(1), sh(1), and ksh(1). Thus, if it is invoked with a command name beginning
with a hyphen (that is, passes a basename to the shell that is also preceded by a hyphen.
The input flow control can be enabled by setting environmental variable before running Please see section for details on using this envi-
ronment variable.
EXAMPLES
Save everything printed on the user's screen into file
Append a copy of everything printed to the user's screen to file
WARNINGS
A command such as which displays the contents of the destination file, should not be issued while executing because it would cause to log
the output of the command to itself until all available disk space is filled. Other commands, such as more(1), can cause the same problem
but to a lesser degree.
records all received output in the file, including typing errors, backspaces, and cursor motions. Note that it does not record typed char-
acters; only echoed characters. Thus passwords are not recorded in the file. Responses other than simple echoes (such as output from
screen-oriented editors and command editing) are recorded as they appeared in the original session.
When there is no input flow control is not set), there can be some data loss while using However, script(1) can behave unexpectedly, if is
set and is not set.
AUTHOR
was developed by the University of California, Berkeley and HP.
script(1)