03-15-2013
Difference between .vimrc and .exrc?
What is the difference between .vimrc and .exrc? I google it but didn't find the brief explanation?
Regards
ADI
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi There, :)
I Need to put the following command in the vimrc for the execution of ECLIPSE
so I have written smthing like as follows,
export PATH=$PATH:/JVM location
after this i go to my eclipse folder and when I execute STILL it is not getting opened.....
Any Help that makes my... (6 Replies)
Discussion started by: gk_linux
6 Replies
2. UNIX for Dummies Questions & Answers
Hi
I want to customise my vi environment.So i have created a a .exrc file in my working directory and written all set commands.But when i am invoking vi ,it is not taking any effect of the vi.
Can anybody have any idea what is happening
Thanks in advance
Regds
Sas (12 Replies)
Discussion started by: SasDutta
12 Replies
3. Shell Programming and Scripting
I have created some custom commands (using the map macro feature) and have those map commands in my $HOME/.exrc file (I am using bash) Here are the commands, which I have in my $HOME/.exrc
map! F /user\.base\.scope^V^Mk4ddF
map! L /user\.base\.search^V^Mk4ddL
map! V... (1 Reply)
Discussion started by: inditopgun
1 Replies
4. Solaris
Hi
since we migrated from Solaris 8 to Solaris 10 I do miss a nice feature when editing crontab with vim editor: no more color highlighting after starting to edit. Well there is a hack, see below.
I did define:
export EDITOR='vim -c ":source /export/home/duc904/.vimrc"'
Under Sol8 when... (2 Replies)
Discussion started by: duc904
2 Replies
5. UNIX for Advanced & Expert Users
I was reading this and thought I could put this in my vimrc and it would convert the line endings to unix. Am I doing something wrong or am I missing something?
set ff=unixManaging/Munging Line-Endings with Vi/Vim | Jeet Sukumaran
I used this command and it confirms that my global option is... (2 Replies)
Discussion started by: cokedude
2 Replies
6. Shell Programming and Scripting
I am trying to write a bash script that will create a .bashrc and .vimrc. I was wondering if anyone would know how to do approach this. Would this work if there was no .bashrc file minus the "stuff"
echo "stuff" >> .bashrc (5 Replies)
Discussion started by: meredith1990
5 Replies
7. UNIX for Advanced & Expert Users
I'm having trouble getting my vimrc to work the way I want it. For some reason after I hit enter it is creating tabs instead of spaces like I would expect. Here is an example of what I am talking about. $ = newline, ^I = tab. On the line of struct EDGETAG* q; I hit enter and it created a tab... (2 Replies)
Discussion started by: cokedude
2 Replies
8. Shell Programming and Scripting
Hi,
1. I'm using tcsh and I use a .gvimrc file which was working fine with my previous ksh shell. But while sourcing, I'm getting messages like 'Unmatched " '. I'm not trying anything fancy but just using " for commenting in the very first line and I see the error is thrown right there.
2.... (2 Replies)
Discussion started by: rishikpillai90
2 Replies
9. UNIX for Beginners Questions & Answers
My exrc file contents are
set number
set -o vi
map Q :q!
ab inc include
set number and set -o vi is working but
map and ab is not working can u help me ??
Please use CODE tags as required by forum rules! (1 Reply)
Discussion started by: varun aravinth
1 Replies
10. AIX
There's no Vim in AIX (6 and 7), but Vi is natively available.
I want to save my configuration for Vi like `set nu` to number lines in files.
I couldn't find configuration related to Vi in /etc/ or /usr/etc/ folders.
Please help me with that. (4 Replies)
Discussion started by: Chinggis6
4 Replies
LEARN ABOUT DEBIAN
vim-registry
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)