From: Miles Bader <miles@gnu.org>
Subject: Re: How to make emacs auto-recognize utf-8 encoded files upon visiting
Date: 27 Sep 2002 23:41:36 +0900 [thread overview]
Message-ID: <87ofajwl3z.fsf@tc-1-100.kawasaki.gol.ne.jp> (raw)
In-Reply-To: mailman.1033135767.32171.help-gnu-emacs@gnu.org
Charles Muller <acmuller@gol.com> writes:
> I noticed a good bit of negative reaction toward TEI-Emacs when I
> first mentioned it, where people expressed alarm about the TEI people
> not caring about the about the GPL and not reporting to the GNU
> development team. I think that these concerns come as a result of
> people not really checking into what the package is, and what it does.
> It is not a new version of Emacs, such as XEmacs. It is simply an
> add-on, that contains mode enhancements, and some of its own new
> modes--just the way people are accustomed to adding on calendar modes,
> e-mail packages, or whatever.
It's perfectly fine for groups such as the TEI to have such add-on
packages, and it's certainly not necessary for them to `write to the GNU
development team and then wait for a future version for it to be
implemented.'
However, for people who have developed big packages, I think it would be
a good thing to try to maintain some sort of `loose contact' (and maybe
they have done so, I don't know), just so that people know what's out
there, and perhaps can avoid duplicating the work they've done. If
some of their stuff is of general utility, often it can be merged into
the emacs distribution, which will lessen the maintenance burden.
For instance the problem with unicode font coverage you mentioned is a
apparently a big annoyance for the people developing the `real' unicode
version of emacs.
I think that in the case of many big packages (e.g. `semantic'), there's
a general awareness in the emacs community that they exist, so formal
contact isn't necassary. I hadn't heard of the TEI work though.
-Miles
--
We live, as we dream -- alone....
next prev parent reply other threads:[~2002-09-27 14:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 16:39 How to make emacs auto-recognize utf-8 encoded files upon visiting Gerald Wildgruber
2002-09-23 23:35 ` Jesper Harder
2002-09-24 3:29 ` Charles Muller
[not found] ` <mailman.1032838300.26368.help-gnu-emacs@gnu.org>
2002-09-24 6:27 ` Miles Bader
2002-09-24 8:59 ` Charles Muller
2002-09-24 15:12 ` Eli Zaretskii
2002-09-25 6:45 ` Charles Muller
2002-09-25 6:55 ` Eli Zaretskii
2002-09-25 8:07 ` Charles Muller
2002-09-25 8:33 ` Charles Muller
2002-09-26 4:42 ` Eli Zaretskii
2002-09-26 7:00 ` Charles Muller
2002-09-26 16:05 ` Eli Zaretskii
2002-09-27 0:36 ` Charles Muller
[not found] ` <mailman.1033086929.4506.help-gnu-emacs@gnu.org>
2002-09-27 1:42 ` Miles Bader
2002-09-27 7:06 ` Charles Muller
[not found] ` <mailman.1033110323.17834.help-gnu-emacs@gnu.org>
2002-09-27 9:07 ` Miles Bader
2002-09-27 11:56 ` Kai Großjohann
2002-09-27 14:10 ` Charles Muller
[not found] ` <mailman.1033135767.32171.help-gnu-emacs@gnu.org>
2002-09-27 14:41 ` Miles Bader [this message]
2002-09-27 15:54 ` Stefan Monnier <foo@acm.com>
2002-09-25 9:21 ` Charles Muller
2002-09-25 9:26 ` Charles Muller
2002-09-25 9:41 ` Charles Muller
[not found] ` <mailman.1032936261.7964.help-gnu-emacs@gnu.org>
2002-09-25 8:23 ` Miles Bader
2002-09-25 14:55 ` Stefan Monnier <foo@acm.com>
2002-09-24 19:05 ` tramp Roger Mason
[not found] ` <mailman.1032848900.31556.help-gnu-emacs@gnu.org>
2002-09-24 8:26 ` How to make emacs auto-recognize utf-8 encoded files upon visiting A. Lucien Meyers
2002-09-24 11:45 ` auto-recognize utf-8 encoded files upon visiting: solved (sort of...) Gerald Wildgruber
2002-09-24 12:39 ` Charles Muller
[not found] ` <mailman.1032871109.14505.help-gnu-emacs@gnu.org>
2002-09-25 14:28 ` A. L. Meyers
2002-09-24 18:57 ` How to make emacs auto-recognize utf-8 encoded files upon visiting Dominic Cronin
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ofajwl3z.fsf@tc-1-100.kawasaki.gol.ne.jp \
--to=miles@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).