03-15-2013
Well, .exrc was established by the original ex before there was a vi. The name vi means visual ex. The name ex means extended ed:
https://www.unix.com/man-page/All/0/ed/ When the open source people wrote vi replacements, notably vim, they had the option to make additional configuration files for options in vim that are not ex/vi compatible. It is a bit like sh, ksh, bash, relative to .profile , $ENV, /etc/profile, /etc/suid-profile, .kshrc, .bashrc, .bash_profile, .bash_login.
The man page lists a bushel of config files down at the end:
Man Page for vim (all Section 0) - The UNIX and Linux Forums
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
shell-quote
SHELL-QUOTE(1p) User Contributed Perl Documentation SHELL-QUOTE(1p)
NAME
shell-quote - quote arguments for safe use, unmodified in a shell command
SYNOPSIS
shell-quote [switch]... arg...
DESCRIPTION
shell-quote lets you pass arbitrary strings through the shell so that they won't be changed by the shell. This lets you process commands
or files with embedded white space or shell globbing characters safely. Here are a few examples.
EXAMPLES
ssh preserving args
When running a remote command with ssh, ssh doesn't preserve the separate arguments it receives. It just joins them with spaces and
passes them to "$SHELL -c". This doesn't work as intended:
ssh host touch 'hi there' # fails
It creates 2 files, hi and there. Instead, do this:
cmd=`shell-quote touch 'hi there'`
ssh host "$cmd"
This gives you just 1 file, hi there.
process find output
It's not ordinarily possible to process an arbitrary list of files output by find with a shell script. Anything you put in $IFS to
split up the output could legitimately be in a file's name. Here's how you can do it using shell-quote:
eval set -- `find -type f -print0 | xargs -0 shell-quote --`
debug shell scripts
shell-quote is better than echo for debugging shell scripts.
debug() {
[ -z "$debug" ] || shell-quote "debug:" "$@"
}
With echo you can't tell the difference between "debug 'foo bar'" and "debug foo bar", but with shell-quote you can.
save a command for later
shell-quote can be used to build up a shell command to run later. Say you want the user to be able to give you switches for a command
you're going to run. If you don't want the switches to be re-evaluated by the shell (which is usually a good idea, else there are
things the user can't pass through), you can do something like this:
user_switches=
while [ $# != 0 ]
do
case x$1 in
x--pass-through)
[ $# -gt 1 ] || die "need an argument for $1"
user_switches="$user_switches "`shell-quote -- "$2"`
shift;;
# process other switches
esac
shift
done
# later
eval "shell-quote some-command $user_switches my args"
OPTIONS
--debug
Turn debugging on.
--help
Show the usage message and die.
--version
Show the version number and exit.
AVAILABILITY
The code is licensed under the GNU GPL. Check http://www.argon.org/~roderick/ or CPAN for updated versions.
AUTHOR
Roderick Schertler <roderick@argon.org>
perl v5.8.4 2005-05-03 SHELL-QUOTE(1p)