On 19-Feb-09 12:02, Luc Hermitte wrote:
I've finally implemented my own unit testing plugin for vim. [1]
This is a first draft, and all comments are welcomed.
The plugin has been strongly inspired by Tom Link's tAssert plugin
(thanks Tom!).
...
My plugin is made for Unit Testing, and
BTW, tAssert provides convenience functions that my script don't (yet?).
At first, I wondered if both plugins should be merged.
This is also the reason why I'd rather prefer to
strip down my tassert plugin and to leave only the TAssert command and
some utility functions in it.
Just in
However I've made a different design choice: my plugin acts as a
preprocessor. Thanks to that, I'm able to know the line where an
assertion failure occurred
Cool.
BTW, tAssert provides convenience functions that my script don't (yet?).
At first, I wondered if both plugins should be merged.
Tom Link wrote:
However I've made a different design choice: my plugin acts as a
preprocessor. Thanks to that, I'm able to know the line where an
assertion failure occurred
Cool.
BTW, tAssert provides convenience functions that my script don't (yet?).
At first, I wondered if
On 20/02/09 16:03, Charles Campbell wrote:
Tom Link wrote:
However I've made a different design choice: my plugin acts as a
preprocessor. Thanks to that, I'm able to know the line where an
assertion failure occurred
Cool.
BTW, tAssert provides convenience functions that my script don't
I personally think part of the problem is that vim is a rather fragile
environment (because it's a really versatile editor that can adapt to
different usage styles). A script that works well for me doesn't
necessarily work for you because you use different options etc. and
IMHO it is too
- Ingo Karkat sw...@ingo-karkat.de a écrit :
On 06-Feb-09 22:17, Luc Hermitte wrote:
BTW, a good Unit Testing framework is most welcomed. There is
already one, but it lacks quickfix integration, and a
simple :command-like syntax.
Luc, which unit testing framework are you talking
Tom Link micat...@gmail.com wrote:
Luc, which unit testing framework are you talking about?
A vim.sf.net search points to
http://www.vim.org/scripts/script.php?script_id=1125
That's the one.
I once wrote
http://www.vim.org/scripts/script.php?script_id=1730
that is supposed to solve a
On 07-Feb-09 7:08, Tom Link wrote:
Luc, which unit testing framework are you talking about?
A vim.sf.net search points to
http://www.vim.org/scripts/script.php?script_id=1125
I once wrote
http://www.vim.org/scripts/script.php?script_id=1730
that is supposed to solve a similar purpose
On 07-Feb-09 12:39, Luc Hermitte wrote:
My few requirements, in case it helps:
- we should be able to test values with very simple things like:
:Assert value 42
- the result should end in the quickfix window (which implies
a first pass on functions/files to determine the current line
Hi Tom,
On Fri, Feb 06, at 10:56 Tom Link wrote:
So for a start, I am proposing a VimLib project, maintainable by the Vim
community, written entirely in VimL and except from one function (see
below) it will independent from the vim official distribution.
It's based on personal
On Feb 7, 1:00 pm, Ingo Karkat sw...@ingo-karkat.de wrote:
Which takes us back to the original topic of this thread: There are many
different plugins in various states (mostly of disarray), and it's hard for
users to judge the applicability and how well it is being maintained.
On Feb 7, 7:14
Hi John,
On Fri, Feb 06, at 10:44 John Beckett wrote:
Garrett Whelan wrote:
3) Is there a central repository of vim scripts/extentions?
It seems rather haphazard to me. I often find 4-5 scripts
that solve my problem with little documentation for any and
none of them have been updated
Hello,
Agathoklis D. Hatzimanikas a.hat...@gmail.com :
So for a start, I am proposing a VimLib project, maintainable by the
Vim community, written entirely in VimL and except from one function (see
below) it will independent from the vim official distribution.
So far there are two such
Luc, which unit testing framework are you talking about?
A vim.sf.net search points to
http://www.vim.org/scripts/script.php?script_id=1125
I once wrote
http://www.vim.org/scripts/script.php?script_id=1730
that is supposed to solve a similar purpose although it's still quite
minimalist.
So for a start, I am proposing a VimLib project, maintainable by the Vim
community, written entirely in VimL and except from one function (see
below) it will independent from the vim official distribution.
It's based on personal experiments and from the work
of Marc Weber and Luc Hermitte.
16 matches
Mail list logo
