Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#7246 - Actuality of /etc/gvimrc and global gvim-setting issue

Attached to Project: Arch Linux
Opened by Marcus Werner (prakti) - Wednesday, 23 May 2007, 11:23 GMT
Last edited by Tobias Kieslich (tobias) - Wednesday, 22 August 2007, 19:35 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture All
Severity High
Priority Normal
Reported Version 0.8 Voodoo
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

/etc/gvimrc is heavily out of date.
Mostly because of the borked highlighting settings. I've attached a hopefully proper replacement.

Is it possible to make gvim first source /etc/vimrc, afterwards /etc/gvimrc, then ~/.vimrc and least ~/.gvimrc.

In the Unix-world it has been *most* common that user-settings _do_ override system-wide settings. The current order of sourcing first /etc/vimrc then ~/.vimrc, afterwards /etc/gvimrc and least ~/.gvimrc is highly unnerving.

Especially if one has all his configuration in ~/.vimrc and is forced to have a ~/.gvimrc sourcing the ~/.vimrc

best regards,
   gvimrc (1.2 KiB)
This task depends upon

Closed by  Tobias Kieslich (tobias)
Wednesday, 22 August 2007, 19:35 GMT
Reason for closing:  Not a bug
Comment by Tobias Kieslich (tobias) - Tuesday, 21 August 2007, 21:25 GMT
pacman has functions for that to keep changes once you made them. I like to keep these files close to the vanilla style. In case you consider it outdated and don't wanna use .gvimrc to change it, you better should convince upstream managers to update the files.

Loading...