public inbox for gentoo-lisp@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marijn <hkBst@gentoo.org>
To: Imran Rafique <imran@rafique.org>
Cc: gentoo-lisp@lists.gentoo.org
Subject: Re: [gentoo-lisp] vim with embedded racket
Date: Tue, 12 Apr 2011 10:32:36 +0200	[thread overview]
Message-ID: <4DA40E24.1090308@gentoo.org> (raw)
In-Reply-To: <BANLkTinXS8uT9Dj0vTsP2n3A143j2KTO_w@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Imran,

On 04/12/11 04:43, Imran Rafique wrote:
> Gentoo-lispers,
> 
> Currently, vim support for embedded racket is disabled in
> eclass/vim.eclass. I have patched this in my local overlay to add
> support for both racket (and tcl). As dev-scheme/racket is itself not
> part of the standard portage tree, I thought it might not make sense
> to create a new bug to amend the standard vim.eclass. Would it be
> better to just add the amended vim.eclass to the gentoo-lisp overlay
> instead?

Racket is on its way to main tree.

> If so, then should I just send the patch to this list, or create a
> bugzilla bug with some gentoo-lisp specific info?

You can create a bug and have it depend on the bug about getting racket
in main tree (324161).

Marijn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2kDiQACgkQp/VmCx0OL2zQGgCgnL2JgCNjURprwWXP/FnjU7GO
FgoAn08AiN0VVgnjnYVwcP/4mXlxxxqf
=fNOW
-----END PGP SIGNATURE-----



  reply	other threads:[~2011-04-12  8:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12  2:43 [gentoo-lisp] vim with embedded racket Imran Rafique
2011-04-12  8:32 ` Marijn [this message]
2011-04-13  1:45   ` Imran Rafique
2011-04-13 11:36     ` Marijn
2011-04-13 12:32       ` Marijn
2011-04-13 22:57       ` Imran Rafique
2011-04-14  3:34         ` Imran Rafique

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DA40E24.1090308@gentoo.org \
    --to=hkbst@gentoo.org \
    --cc=gentoo-lisp@lists.gentoo.org \
    --cc=imran@rafique.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox