On Fri, Dec 14, 2007 at 11:59:55PM -0700, Chris Kuethe wrote:
> On Dec 14, 2007 11:43 PM, Girish Venkatachalam
> <[EMAIL PROTECTED]> wrote:
> > On 21:42:13 Dec 14, Chris Kuethe wrote:
> > > I don't actually use any of them, but what about by function?
> >
> > As I said I don't either but there migh
On 23:59:55 Dec 14, Chris Kuethe wrote:
> Post links to the plugins, maybe give a 1 or 2 line summary of what they
> do?...
>
Like a regular port? This shouldn't be a problem.
> That was a single example. I think the location of each plugin is
> based on its function. I went to vim.org, and I
On Dec 14, 2007 11:43 PM, Girish Venkatachalam
<[EMAIL PROTECTED]> wrote:
> On 21:42:13 Dec 14, Chris Kuethe wrote:
> > I don't actually use any of them, but what about by function?
>
> As I said I don't either but there might be people who need them.
Post links to the plugins, maybe give a 1 or 2
On 21:42:13 Dec 14, Chris Kuethe wrote:
> I don't actually use any of them, but what about by function?
>
As I said I don't either but there might be people who need them.
> the taglist plugin could go in devel, with an additional category of
> editors, maybe.
Yes but this does not address the
On 21:35:33 Dec 14, brad walker wrote:
> also:
>
> %:s/vim/emacs/g
>
I know that OpenBSD folks even dislike vim sticking to vi. I am not that
geeky. ;)
As to emacs someone else has to take the initiative. I stopped using
it ages go.
-Girish
On Dec 14, 2007 8:33 PM, Girish Venkatachalam
<[EMAIL PROTECTED]> wrote:
> Should they all go under editors/ or do we need a high level directory?
> Perhaps this question is not that important.
>
> I need to know how to structure the porting activity.
>
> I don't use too many plugins myself but I a
On Sat, 2007-12-15 at 09:03 +0530, Girish Venkatachalam wrote:
> Dear friends and fellow porters,
>
> I wish to know how to go about porting the very excellent plugins
> available for the vim editor to OpenBSD.
>
> Many of them rely on vim being compiled with certain features which our
> FLAVOR
