Sponsored Content
Top Forums Shell Programming and Scripting Continuously display the file name in vim Post 302405528 by thillai_selvan on Friday 19th of March 2010 04:43:11 AM
Old 03-19-2010
Code:
set modeline
set ls=2

Add this line into your .vimrc file.
Now you can see the file name in the bottom always.

Last edited by thillai_selvan; 03-19-2010 at 05:49 AM..
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Shell Script to continuously scan a log file

Hello members, I have some doubts on how to write a script that can reports success / failure of a batch job ? 1. Run a batch job: 2. Wait and search for a particular string in the Log file: tail -f log01*.txt | egrep -v "^SUCCESSFUL" echo "continue with the other tasks" ... (1 Reply)
Discussion started by: novice82
1 Replies

2. Shell Programming and Scripting

^M in yank but not in file in Vim

I am trying to visually select a section of text in vim and then substitute for it using the :%s/ sequence. First I visually select text. Then I yank using "ay. Then I type :%s/ followed by Control R and the register name, in this case a. This fills in the text I have visually selected into... (6 Replies)
Discussion started by: Enobarbus37
6 Replies

3. UNIX for Dummies Questions & Answers

Parsing log file continuously

Hi i have a log file, which keeps appending, i want to find "exceptions" in that log file and copy those exceptions to another file. i am using grep exception filename >> location where to copy but as the file is appending, am not able to view. i am using tail -f command , ... (5 Replies)
Discussion started by: rchaitanya
5 Replies

4. 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

5. UNIX for Dummies Questions & Answers

Vim help - delete words in a file or characters after pattern

I have a file with words that begin with character #. Whenver that character is found that word should be deleted throughout the file. How do I do that in VIM. e.g: afkajfa ladfa ljafa #222222 kjafad ljl afajkj kjlj uouu #44444 jlkj lkjl Output should be afkajfa ladfa ljafa kjafad... (1 Reply)
Discussion started by: osbourneric
1 Replies

6. UNIX for Dummies Questions & Answers

VIM E212: Cannot save a new file

Hey everyone, I'm new to Linux and am attempting to run a TF2 server on a CentOS VPS (terminal only). I followed this guide (link below) and have arrived on step 4, creating a configuration file. When I try to save the new file however, I get the E212: Can't open file for writing error.... (0 Replies)
Discussion started by: rGSyn
0 Replies

7. Shell Programming and Scripting

Help with update vim file-syntax relationship?

There are some ksh files named as "*.lib" in my system. When I open them in VIM, vim syntax can't parse it correctly. Is there a way that I can relate the *.lib with KSH syntax in VIM? Due to access limitation, i can only update the files under my home directory and can't modify the VIM... (6 Replies)
Discussion started by: sleepy_11
6 Replies

8. Shell Programming and Scripting

Cut first column from file in Vi(Vim)

I have a parts file that looks like this: EE36264|0NH46||Y|A|EA|0|0|0|N|LUNETTE 3" ADJ. EYE|0|0|*|0|PEOZZU|N|12|N|N|VPS|N|N|N|N|LUNETTE 3" ADJ. EYE|0|||Receive into Inventory|81755|EE36264|*|*|*|0|0||EE36264|A|*|* F1.5|53932||Y|A|EA|0|0|0|N|FLAT ZERO CAL... (4 Replies)
Discussion started by: djehresmann
4 Replies

9. Emergency UNIX and Linux Support

Script for pinging continuously

Hi, I need to set up a script that would write the results of the ping command from one AIX server to another file may be every minute. Like this I need to gather the data for a period of 24 hours. Can someone please help me with this? G (5 Replies)
Discussion started by: ggayathri
5 Replies

10. UNIX for Beginners Questions & Answers

Shell script for continuously monitoring log file

Hi I have written below log monitoring script to egrep multiple words and redirect the output to a text file and its working fine but I want to add some more below given functionality to it, which is very advance and im not very good in it, so please help if you can :) I am egrepping all the... (1 Reply)
Discussion started by: scazed
1 Replies
vim-registry(5) 						    vim addons							   vim-registry(5)

NAME
vim-registry - syntax for vim-addons registry files SYNOPSIS
PACKAGE-NAME.yaml DESCRIPTION
A registry file is a multi-document YAML file (i.e. it can be composed by several different YAML documents separated by "---" lines). Each YAML document represents a registry entry, that is the information describing a single addon. Ideally, the registry directory contains one file per package shipping addons; with a filename obeying to the convention PACKAGE-NAME.yaml. Hence a single package can contribute to the registry with multiple entries described in a single YAML file. For example, the "vim-scripts" package should ship a single /usr/share/vim/registry/vim-scripts.yaml file, containing one YAML document per shipped addon. The first lines of such file can look like the following: addon: alternate description: "alternate pairing files (e.g. .c/.h) with short ex-commands" basedir: /usr/share/vim-scripts/ disabledby: "let loaded_alternateFile = 1" files: - plugin/a.vim - doc/alternate.txt --- addon: whatdomain description: "query the meaning of a Top Level Domain" basedir: /usr/share/vim-scripts/ disabledby: "let loaded_whatdomain = 1" files: - plugin/whatdomain.vim --- Each registry entry may contain the following fields, to be typeset according to the YAML specification: addon (Required) Name of the addon. description (Required) Human understandable textual description of the addon. files (Required) List of the files which compose the addon and are required to be present in a component of the Vim runtime path for the addon to be enabled. Each file is specified relative to a component of the Vim runtime path. basedir (Optional) Directory where the files shipped by the addon (i.e., where the symlinks of the user/sysadm should point to) reside on the filesys- tem. Default is /usr/share/vim/addons. disabledby (Optional) Vim script command that can be used (usually by adding it to ~/.vimrc) to prevent the addon from being used even when it is installed. The intended usage of this field is to "blacklist" an undesired addon whose files are available, and hence automatically loaded by Vim, in a component of the Vim runtime path. AUTHOR
James Vega <jamessan@debian.org> SEE ALSO
vim-addons(1), YAML specification <http://www.yaml.org/> COPYRIGHT
Copyright (C) 2010 James Vega This program is free software, you can redistribute it and/or modify it under the terms of the GNU General Public License version 3 as pub- lished by the Free Software Foundation; either version 3 of the License, or (at your option) any later version. Debian Project January 2010 vim-registry(5)
All times are GMT -4. The time now is 07:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy