Sponsored Content
Full Discussion: Vim tips and tricks
Top Forums UNIX for Beginners Questions & Answers Vim tips and tricks Post 302557715 by phamnu on Thursday 22nd of September 2011 03:28:48 AM
Old 09-22-2011
I am a beginner with unix, so may be my question will be very stupid.

I have problem with saving a FORTRAN's code after changing it.
I used the "vim" command to read the code, then use the "SHIFT-I" to insert some new part in the code.
After that I don't know how to save the code.
I tried the command: ":w" but it just write to the code, it can not save the code.
Thanks in advance for helping me.

---------- Post updated at 02:28 AM ---------- Previous update was at 02:02 AM ----------

Could I have another question here?
If I want to copy 19 lines in the fortran code (for example from line 1 to line 19) after using the command "vim" to read the code, what should I do?
Thank so much!
 

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

tar tricks

Hello there, Is there anyway to make the tar utility print the contents of the files inside it (not list the files, but rather their contents) sequentially from the command line? What I ultimately would like to do is to have a way of printing the contents of each file in the tar archive... (2 Replies)
Discussion started by: neked
2 Replies

2. Shell Programming and Scripting

need couple of ksh tricks please

1) I ran myScript with 2 arguments, I meant to use 3 if I do r my, it will rerun it with the 2 arguments. is there a way I can do r my and add a third argument at the end? 2) say I did myAcript.ksh 2 5 7 8 I realise my typo. is there an easy way to redo the command replacing A with S? ... (4 Replies)
Discussion started by: JamesByars
4 Replies

3. Post Here to Contact Site Administrators and Moderators

Solaris tips and tricks

What do you think could we open new top topic with tips and tricks and to show to other users some tricks what do we know like dtrace , new virtual server , how to add new users etc. This is only suggestion (1 Reply)
Discussion started by: solaris_user
1 Replies

4. UNIX for Dummies Questions & Answers

Sed Tricks

I have a file which containd a string "old" and I need to replace all old with "new" if and only if it is a string not part of a string like Gold or fold etc. I tried with sed like below echo "old gold old" | sed 's/old/new/g' It doesn't give the desired output, It give "old Gnew new".... (3 Replies)
Discussion started by: siba.s.nayak
3 Replies

5. Solaris

Very Importan - Vim Settings - Error while opening a File using vim

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

6. UNIX for Advanced & Expert Users

Basic VI tricks

I found a decent guide of VI basic tricks. This guide does expect you to have a decent understanding of VI. It does not go over very much beginner related. vi Manual (3 Replies)
Discussion started by: cokedude
3 Replies
OHCOUNT(1)							   User Commands							OHCOUNT(1)

NAME
ohcount - manual page for ohcount 3.0.0 SYNOPSIS
ohcount [option] [paths...] DESCRIPTION
Ohloh source code line counter command line tool. http://www.ohloh.net/ [option] can be one of the following: -a, --annotate -d, --detect -h, --help -i, --individual -l, --license -re -s, --summary -a, --annotate Show annotated source code The contents of all source code files found within the given paths will be emitted to stdout. Each line will be prefixed with a tab-delimited language name and semantic categorization (code, comment, or blank). -d, --detect Find source code files Recursively find all source code files within the given paths. For each source code file found, the file name will be emitted to stdout prefixed with a tab-delimited language name. -h, --help Display this message -i, --individual Count lines of code per file Count lines in all source code files within the given paths, and emit a report of the lines of code, comments, and blanks in each language per file. -l, --license Displays detected licensing information contained in each source code file. -re Prints raw entity information to the screen (mainly for debugging). -s, --summary Count lines of code (default) Count lines in all source code files within the given paths, and emit a report of the total number of lines of code, comments, and blanks in each language. This is the default action. [paths] can refer to any number of individual files or directories. Directories will be probed recursively. If no path is given, the current directory will be used. ohcount 3.0.0 September 2011 OHCOUNT(1)
All times are GMT -4. The time now is 12:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy