Поиск по:comet.sai.msu.ru -
Поискать по всем серверам
На этой странице приведены все страницы сервера comet.sai.msu.ru ,которые мы индексируем. Показаны документы 601 - 620 из 1544.
Упорядочить по:
URL
|
дате изменения
601. Quit vi
. To quit the vi editor: :q . If you have edited (changed) the file you will be prompted with the message: No write since last change . You can either save the changes or quit without saving any of the changes you have made.
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/vi/three.4.html -- 1.9 Кб -- 17.01.1997
Похожие документы
Похожие документы
602. Saving files and exiting vi
. There are several ways in which you can end your editing session, leave vi and return to the shell. Saving changes . Without saving changes . Saving to another file . Quitting vi .
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/vi/three.html -- 1.9 Кб -- 17.01.1997
Похожие документы
Похожие документы
603. Starting vi and opening files
. To start using vi enter the command: vi filename . The filename can be the name of an existing file or the name of the file that you want to create. Examples . Did You Know? .
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/vi/two.html -- 1.9 Кб -- 17.01.1997
Похожие документы
Похожие документы
604. UNIX shell commands
You can run UNIX commands and see their output without leaving vi. You can also insert the output of a UNIX command into the file you that are editing. To run a single UNIX command use the command: :! UNIX_command . You can start a shell from within vi and use it as you would your usual UNIX environment, then exit the shell and return to vi . ... To insert the output from a UNIX command into a file, immediately after the cursor: :r! command . ...
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/vi/unix.html -- 2.8 Кб -- 17.01.1997
Похожие документы
Похожие документы
605. Take care!
. Do not use the name of a file that already exists. If you do, it will be overwritten by the new copy. Set the shell variable "noclobber" so that existing files cannot be overwritten (or clobbered). How to do it .
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/warnings/cat.html -- 1.9 Кб -- 17.01.1997
Похожие документы
Похожие документы
606. Take care!
. Take care what name you give to the file copy. If you choose the name of a file that already exists it will be overwritten by the new copy! . Either: . Always use the cp command together with its -i option. This will prompt you for confirmation whenever the copy would overwrite an existing file. or . Create a command alias for the cp command. Including the -i flag in the alias will make sure that you are always prompted for confirmation whenever the copy would overwrite an existing file.
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/warnings/copy.html -- 2.3 Кб -- 17.01.1997
Похожие документы
Похожие документы
607. Watch out!
. Never set write permission for all other users on a file or directory which is in your home directory. If you do other users will be able to change its content. This can represent a serious security risk. You can use the umask command to set default access permissions. This will ensure that any files and directories you create have consistent permissions.
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/warnings/permissions.html -- 2.0 Кб -- 17.01.1997
Похожие документы
Похожие документы
608. **Caution**
. Once a file is removed there is no way to retrieve it. Always use the rm command together with its -i option. rm -i filename . This will prompt you for confirmation that you want to remove the file. You can make this the default action for the rm command by creating a command alias that uses this option.
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/warnings/remove.html -- 2.1 Кб -- 17.01.1997
Похожие документы
Похожие документы
609. **Caution**
. If you remove a directory that still holds files there is no way to retrieve it. Always use the rm command together with the -i option. rm -ir directory_name .
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/warnings/remove1.html -- 1.9 Кб -- 17.01.1997
Похожие документы
Похожие документы
610. Tip...
. Use global replacement in its interactive mode to avoid making changes that you don't intend. To do this add the c option to the end of the global replacement command: :g/pattern1/s//pattern2/gc . vi will display the first occurrence of pattern1 . To replace it with pattern2 you must enter y (yes) and press <RETURN> . If you don't want to replace this pattern press <RETURN> to go to the next occurence.
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/warnings/vi.html -- 2.1 Кб -- 17.01.1997
Похожие документы
Похожие документы
611. Check out a file for reading
. To get a copy of one of your files for reading use the command: sccs get filename . To get a copy of each of your files for reading use the command: sccs get SCCS . When you have finished using a file that was fetched from SCCS by sccs get do not attempt to replace it there: remove it.
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/utilities1/chout_1.html -- 2.1 Кб -- 17.01.1997
Похожие документы
Похожие документы
612. Inserting SCCS ID keywords in a file
. You can put one or more ID keywords in each file. These keywords are used to display information about the file whenever a read only version is checked out. SCCS ID keywords include: %G% the date of the delta %I% sid of the retrieved text %M% the current module name %R% the current release number %W% a shorter form for %Z%%M%<tab>%I% %Z% string used by the what command .
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/utilities1/sccs_insert.html -- 2.2 Кб -- 17.01.1997
Похожие документы
Похожие документы
613. Putting files under SCCS control
. Files are placed under the control of SCCS by making an SCCS directory and creating the SCCS file. You also have the option of placing ID keywords in each file. Making an SCCS directory . Inserting SCCS ID keywords in a file . Creating an SCCS file .
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/utilities1/sccs_put.html -- 2.0 Кб -- 17.01.1997
Похожие документы
Похожие документы
614. Making an SCCS directory
. To create the SCCS directory use the command: mkdir SCCS . The directory name must be in upper case.
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/utilities1/sccs_put2.html -- 1.7 Кб -- 17.01.1997
Похожие документы
Похожие документы
615. Creating an SCCS file
. To place files under the control of SCCS use the command: sccs create filename(s) . For each filename given as an argument sccs create does the following: . filename is moved to ,filename . a history file s. filename is created in the SCCS subdirectory . a "read only" copy of the initial version of the file is made by sccs get . You can use the ls command to check that the history files have been created. ls SCCS . Now you can remove the ,filename files: rm ,* .
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/utilities1/sccs_put3.html -- 2.3 Кб -- 17.01.1997
Похожие документы
Похожие документы
616. Creating new releases
. To begin a new release for a file you "get" it with the next release number. sccs get -e -r release_number filename . For example for a file with a version of 2.4 you would want the new release to be 3. sccs get -e -r3 sect1.txt s.sect1.txt: 2.4 new delta 3.1 20 lines .
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/utilities1/sccs_releases.html -- 2.0 Кб -- 17.01.1997
Похожие документы
Похожие документы
617. Comparing files
. You can display the line by line difference between two files with the diff command. diff file1 file2 . The information given by the command tells you what changes need to be made for file1 and file2 to match. If there is no difference between the files you are returned to the shell prompt . diff indicates which lines need be added ( a ), deleted ( d ) or changed ( c ). Lines in file1 are identified with a ( < ) symbol: lines in file2 with a ( > ) symbol. Examples . Did You Know? .
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/utilities2/diff.html -- 2.4 Кб -- 17.01.1997
Похожие документы
Похожие документы
618. Examples of using the diff command
To compare the contents of two files: diff email addresses 2a3,4 > Jean JRS@pollux.ucs.co > Jim jim@frolix8 . This displays a line by line difference between the file email and addresses . ... Here are the contents of files email and addresses used in this example. ... To compare two files ignoring differences in the case of the letters and blank spaces: diff -iw part1 part_one . ...
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/utilities2/diff1.html -- 2.9 Кб -- 17.01.1997
Похожие документы
Похожие документы
619. Example of comparing directories with the diff command
To compare two directories in the current directory: diff usability Usability Only in Usability: schedule diff usability/email Usability/email 2a3,4 > Jean JRS@pollux.ucs.co > Jim jim@frolix8 . diff reports that the file (or directory) schedule is unique to the directory Usability . diff then reports that there are differences between the file email in the directory usability and the file of the same name in the directory Usability . ...
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/utilities2/diff2.1.1.html -- 2.5 Кб -- 17.01.1997
Похожие документы
Похожие документы
620. Comparing directories
. You can use the diff command to compare the contents of two directories: diff directory1 directory2 . The information given by the command tells you what to do to make the directories match. If there is no difference between the directories you are returned to the shell prompt . diff reports if a file or directory is only to be found in directory1 or directory2 . It also reports any line by line differences for files that are common to each directory. Example .
[
Сохраненная копия
]
Ссылки http://comet.sai.msu.ru/UNIXhelp/utilities2/diff2.1.html -- 2.2 Кб -- 17.01.1997
Похожие документы
Похожие документы