FS#45705 - [conky] Remove conky syntax files for vim

Attached to Project: Arch Linux
Opened by Alexander Belyaev (alexbel) - Sunday, 19 July 2015, 00:43 GMT
Last edited by Gaetan Bisson (vesath) - Sunday, 19 July 2015, 15:58 GMT
Task Type General Gripe
Category Packages: Extra
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Suggestion:
Remove conky syntax files for vim from conky package. The conky package shouldn't interfere with other configuration files. There are plenty plugins to keep conky syntax files up-to-date.

Additional info:
* conky 1.10.0-4
This task depends upon

Closed by  Gaetan Bisson (vesath)
Sunday, 19 July 2015, 15:58 GMT
Reason for closing:  Won't implement
Comment by Gaetan Bisson (vesath) - Sunday, 19 July 2015, 03:47 GMT
In what way does the conky interfere with other configuration files?
What plugins are there to keep conky syntax files up-to-date?
Please be more specific.

Shipping upstream-provided vim-syntax files do not really seem like doing anything wrong to me. For reference, those files were requested in  FS#28435  .
Comment by Alexander Belyaev (alexbel) - Sunday, 19 July 2015, 13:39 GMT
This package adds syntax files for vim:
usr/share/vim/vimfiles/ftdetect/conkyrc.vim
usr/share/vim/vimfiles/syntax/conkyrc.vim

So, if users manage their via package manager like Vundle, Pathogen, NeoBundle, then they have a duplication of config files,
which might lead to unexpected results.

>What plugins are there to keep conky syntax files up-to-date?
- Via package managers(see above)
- Via package manager + vim-polyglot plugin, which aggregates lots of syntax files. It currently doesn't support conky, but I've already sent a pull request

I agree with you that vim-syntax file doesn't to do anything wrong. And there is a very small chance to get a collision between system syntax file and a user defined one, but I'm definitely sure that adding config files for editors is not a job for conky package.

If users want to have syntax files from the box, they might use separate(maybe recommended) packages.
As an example https://www.archlinux.org/packages/community/any/vim-systemd

Update:
I don't want to reopen this task, but I wanna say, that I can see only syntax files for conky, not cmake or any other tools you have mentioned.
In the way you want to manage this package, you probably will end up with a bunch of syntax files for lots of editors vim, emacs, sublime etc.
Comment by Gaetan Bisson (vesath) - Sunday, 19 July 2015, 15:57 GMT
The vim-systemd is separate from the systemd package because upstream is different. This is not the case with conky.

I also note that other packages provide editor configuration files for their own configuration files, including cmake, pacman and mercurial.

I have no idea what the packages you mention (vundle, pathogen, neobundle) do but:
- I cannot see why they would be troubled by conky shipping its vim configuration;
- how that might even lead to "unexpected results";
- they are not in official repositories.

Loading...