public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Shaw <ryan.shaw@stanfordalumni.org>
To: gentoo-dev@gentoo.org
Cc: pvdabeel@gentoo.org, mark@cs.columbia.edu
Subject: Re: [gentoo-dev] Emacs ebuild and LEIM
Date: 31 May 2002 17:38:40 +0900	[thread overview]
Message-ID: <1022834321.13287.8.camel@momo> (raw)
In-Reply-To: <87k7pksoqb.fsf@gentoo.shacknet.nu>

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]

okay, but the emacs ebuild does include mule, just
not leim. so the "mule" USE variable can't be used
for this: we would need a new variable.

in any case, i thought USE variables were meant to
be applicable across packages; but "mule" and "leim"
are pretty much emacs-specific. wouldn't in be 
better to have a general "multi-byte" or "i18n"
USE variable?

On Fri, 2002-05-31 at 17:31, Matthew Kennedy wrote:

> Ryan Shaw <ryan.shaw@stanfordalumni.org> writes:
> 
> > Or is this something that could be added to the emacs 
> > ebuild, possibly governed by a new USE variable (say
> > "multi-byte" for apps that have compile-time options
> > for multi-byte charset support)?
> 
> IMO, a use flag is appropriate. Check out how xemacs handles support
> for Mule. I think it's pretty similar to what you're trying to
> achieve.
> 
> -- 
> Matthew Kennedy
> Gentoo Linux Developer
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2002-05-31  8:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-31  3:26 [gentoo-dev] Emacs ebuild and LEIM Ryan Shaw
2002-05-31  8:31 ` Matthew Kennedy
2002-05-31  8:38   ` Ryan Shaw [this message]

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=1022834321.13287.8.camel@momo \
    --to=ryan.shaw@stanfordalumni.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=mark@cs.columbia.edu \
    --cc=pvdabeel@gentoo.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