On 2014/07/17 23:39, Edd Barrett wrote:
> Hi Stuart,
>
> Thanks for the input. All sounds reasonable to me.
>
> On Thu, Jul 17, 2014 at 12:04:21PM +0100, Stuart Henderson wrote:
> > On 2014/07/17 11:17, Edd Barrett wrote:
> > > On Sat, Jun 28, 2014 at 01:49:04PM +0100, Edd Barrett wrote:
> > I do
Hi Stuart,
Thanks for the input. All sounds reasonable to me.
On Thu, Jul 17, 2014 at 12:04:21PM +0100, Stuart Henderson wrote:
> On 2014/07/17 11:17, Edd Barrett wrote:
> > On Sat, Jun 28, 2014 at 01:49:04PM +0100, Edd Barrett wrote:
> I don't have the original mail with the attachment any more
On 2014/07/17 11:17, Edd Barrett wrote:
> On Sat, Jun 28, 2014 at 01:49:04PM +0100, Edd Barrett wrote:
> > However, the port is quite unusual and whilst I have managed to mostly get
> > this into shape, there are still some outstanding issues which I am at a
> > loss on:
> >
> > * MODRUBY_REV ne
On Sat, Jun 28, 2014 at 01:49:04PM +0100, Edd Barrett wrote:
> However, the port is quite unusual and whilst I have managed to mostly get
> this into shape, there are still some outstanding issues which I am at a
> loss on:
>
> * MODRUBY_REV needs to kept in sync with editors/vim. Is there a way
I haven't looked at everything, but a couple of comments:
RUN_DEPENDS = ${BUILD_DEPENDS}
- Standard for ports is to do this the other way round, to avoid risk
of a run depepency on something which should only be build dependency.
Even if it's not necessary for a particular port, just do
Hey,
Attached is a WIP port of the command-t plugin for vim:
https://www.youtube.com/watch?v=zprB9KDyaME
I wouldn't usually package a vim plugin, but this one builds a ruby
extension written in C and needs a patch, so it kinda makes sense to do so.
Install and press '\t' to enable the plugin. Wo
