============================
:Author: $Author: seletz $
:Date: $Date: 2008-03-17 16:46:58 +0100 (Mo, 17 Mär 2008) $
:Revision: $Revision: 60824 $
Abstract
--------
This is a recipe to create a VIM project file. This is good for development,
and if you use VIM_ with the Project_ plugin.
This recipe makes use of the mkvimproject_ egg.
code repository: https://svn.plone.org/svn/collective/buildout/collective.recipe.vimproject/trunk
Usage
-----
Just add a buildout section like this::
[buildout]
parts=vpj
[vpj]
recipe = collective.recipe.vimproject
patterns=.py .zcml .pt .cfg .xml .txt .rst
create_tagfile=yes
in_vim_additional=
set hlsearch
tags=/opt/inquant/buildout/eggs/tags
.. _VIM: http://vim.org
.. _Project: http://www.vim.org/scripts/script.php?script_id=69
.. _mkvimproject: http://pypi.python.org/pypi/mkvimproject/
::
vim: set ft=rst tw=75 nocin nosi ai sw=4 ts=4 expandtab:
Change history
**************
2008-03-17 Stefan Eletzhofer <stefan.eletzhofer@inquant.de>
* setup.py: fixed namespace declaration, added std long_description.
* added test setup
Detailed Documentation
**********************
Supported options
=================
The recipe supports the following options:
All options are **optional**.
patterns
a list of patterns to be included in the project file
create_tagfile
If this key exists, the recipe wil also use **ctags** to create a tag
file of the buildout directory
tags
This list will be added to the **in.vim** script to set the tag files.
Here you can add special directories (like buildout egg caches)
in_vim_additional
additional statements to add verbatim to the **in.vim** script.
Example usage
=============
We'll start by creating a buildout that uses the recipe::
>>> write('buildout.cfg',
... """
... [buildout]
... parts=vpj
... eggs=mkvimproject
... newest=true
...
... [vpj]
... recipe = collective.recipe.vimproject
... patterns=.py .zcml .pt .cfg .xml .txt .rst
... create_tagfile=yes
... in_vim_additional=
... set hlsearch
... tags=/opt/inquant/buildout/eggs/tags
... """)
Running the buildout gives us::
>>> print system(buildout)
Upgraded:
...
Installing test1.
Unused options for test1: 'option2' 'option1'.
Contributors
************
Stefan Eletzhofer
Download
********
Metadata
Release files for collective.recipe.vimproject 0.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| collective.recipe.vimproject-0.3.2.tar.gz | 3.3 kB | Without provenance | Details for collective.recipe.vimproject-0.3.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| collective.recipe.vimproject-0.3.2-py2.4.egg | Legacy Egg format | - | - | Details for collective.recipe.vimproject-0.3.2-py2.4.egg |
Total release size: 9.8 kB
Release files / collective.recipe.vimproject-0.3.2.tar.gz
| Download URL | collective.recipe.vimproject-0.3.2.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d30ec843e670b9b1881dc35835faba6a90a7ad84b6a6edffe9e51a6a88e5c7c3
|
|
BLAKE2b-256 checksum How to use checksums |
7bbd77bb15d5deaf6d33ec58230c53d0c1c50bdaff58d7b425943f2cf230c71a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / collective.recipe.vimproject-0.3.2-py2.4.egg
| Download URL | collective.recipe.vimproject-0.3.2-py2.4.egg |
|---|---|
| Size | 6.5 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
f613af128718688be9f3815ce7106ebd47fb78667f8b17974e7ec04319477280
|
|
BLAKE2b-256 checksum How to use checksums |
51a87562a5fd4d12fdb2d8fd70ad8ce6d8f3e8c3268a9c95388edc7c0c451425
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.recipe.vimproject 0.3.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.