03-16-2013
They have the same purpose.
Only vim looks for $HOME/.vimrc file. vim can also use $HOME/.exrc file, as can any vi editor.
Only one of $HOME/.vimrc and $HOME/.exrc is read by vim, whichever it finds first. To prevent confusion, I would suggest just use one file, and delete the other one.
I just use $HOME/.exrc file and do not have the $HOME/.vimrc file.
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
shunit2
SHUNIT2(1) SHUNIT2(1)
NAME
shunit2 - A unit test framework for shell scripts
SYNOPSIS
shunit2 unitfile
DESCRIPTION
shUnit2 is a xUnit unit test framework for Bourne based shell scripts, and it is designed to work in a similar manner to JUnit, PyUnit,
etc.. If you have ever had the desire to write a unit test for a shell script, shUnit2 can do the job.
You can either run shunit2 directly from the commandline and specify the unit file or directly source the shunit2 executable.
If you directly execute shunit2 and don't specify a unitfile shunit2 assumes a empty testfile and will return without an error message.
EXAMPLE
Simple script to test if 1 equals 1
#! /bin/sh
testEquality()
{
assertEquals 1 1
}
# load shunit2
. shunit2
Execute shUnit2 unit tests directly from the commandline
shunit2 /path/to/unit/file
OPTIONS
shunit2 does not support any commandline options at all. You can either source shunit2 to execute your unit tests or directly run shunit2
as a commandline script.
SEE ALSO
For more information see http://code.google.com/p/shunit2/ or have a look at the installed documentation in /usr/share/doc/shunit2/
AUTHOR
shunit2 was written by Kate Ward <kate.ward@forestent.com>. This manpage was written by Ulrich Dangel <mru@spamt.net>.
2.1.6 03/25/2012 SHUNIT2(1)