02-28-2008
Eureka! I THINK I got it...
I had to make sure the the line / setting:
set nobackup
was placed AFTER the lines
source $VIMRUNTIME/vimrc_example.vim
source $VIMRUNTIME/mswin.vim
once I did that (and opened files,) file backups were no longer created.
I guess I could have answered my own question without posting here, but maybe this post will help some other gVim (in Windows) user out there.
9 More Discussions You Might Find Interesting
1. News, Links, Events and Announcements
NEWS:
Flaw leaves Linux computers vulnerable
http://news.com.com/2100-1001-857265.html
A flaw in a software-compression library used in all versions of Linux could leave the lion's share of systems based on the open-source operating system open to attack, said sources in the security... (3 Replies)
Discussion started by: killerserv
3 Replies
2. UNIX for Advanced & Expert Users
I have set up a samba share on my Linux server. I have a gigabit switch, gigabit NICs in each machine.
I have set up the /etc/samba/smb.conf to support no delay, 8192 send/receive buffers, etc. This helped the rate for Samba go from about 4MB/S to about 10MB/S, but I expect to see about... (1 Reply)
Discussion started by: perspectx
1 Replies
3. Windows & DOS: Issues & Discussions
Have you used gVim editor on Windows (xp)? I am talking about the GUI version of vim that you can click the icon on desktop and the gVim editor pops-up and you can create/edit files.
Here's my problem: When I use vim editor on cygwin to create/edit files the file creation mask is set to a... (3 Replies)
Discussion started by: milhan
3 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I've searched and read, and searched and read some more; but I'm still not connecting the dots or understanding what I need to change.
I have a script that creates a file. If I run it as root, the file gets created with 644 permissions like I want. That seems to make sense (at least I... (2 Replies)
Discussion started by: 65bit
2 Replies
5. UNIX for Dummies Questions & Answers
Hi,
This is my first time on this forum..
I searched the previous answers, but didn't find the answer I was looking for at first glance.
csplit works beautifully for me, except for one thing. My file looks like this:
ad|name1|asdf...(several pages)..asdf ...
ad|name2|asdf...(several... (8 Replies)
Discussion started by: juliette salexa
8 Replies
6. Windows & DOS: Issues & Discussions
I use sugarsync to sync my vimrc across computers. I keep the _vimrc file in a syncing folder and in my home folder, I have a symbolic link ~\_vimrc pointing to ~\Synced Docs\_vimrc. On my mac I have a .vimrc symbolic link pointing at the _vimrc file. On the pc side, every time I open the _vimrc... (3 Replies)
Discussion started by: dp88
3 Replies
7. Windows & DOS: Issues & Discussions
A strange situation: i have configured a piranha lvs router(two load balancer and two real servers),
the virtual ip is 192.168.3.252.
Linux and windows clients are on a different subnet (192.168.3.0) and i use route
route add -net 192.168.3.0/24 dev eth0on linux
for /F "tokens=2 delims=:"... (3 Replies)
Discussion started by: Linusolaradm1
3 Replies
8. UNIX for Advanced & Expert Users
In our project we have several unix scripts that trigger different processes. These scripts write logs to a particular folder 'sesslogs', create output data files in a separate directory called 'datafiles' etc. Usually L1 support team re-run these scripts . We donot want L1 support team to have... (14 Replies)
Discussion started by: waavman
14 Replies
9. Shell Programming and Scripting
I want to crop an image and am using convert
convert mountain.png -crop 3000x4500 +repage -format png mountain--cr.png
The problem is that convert is creating 4 files
mountain--cr-0.png
mountain--cr-1.png
mountain--cr-2.png
mountain--cr-3.png
The first is what I need, the other... (10 Replies)
Discussion started by: Kangol
10 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)