Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: ucs-tables.el contains unbalanced parenthesis...
Date: Tue, 26 Mar 2002 22:13:42 +1100	[thread overview]
Message-ID: <87d6xrwpi1.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <vafg02ny6h9.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 26 Mar 2002 11:21:38 +0100")

On Tue, 26 Mar 2002, Kai Großjohann wrote:
> Daniel Pittman <daniel@rimspace.net> writes:
> 
>> ...at least, it does when trying to parse through it with XEmacs.
>>
>> This means that I can't run an auto-autoloads generator over it
>> trivially.
> 
> I think ucs-tables.el doesn't work for XEmacs anyway.  For XEmacs,
> there is a package Latin-Unity or similar.
> 
> Do you still need autoloads even though the package doesn't work?

Nope. If the file is present, though, my current system will attempt to
build auto-loads for all the files in the directory unconditionally.

The idea of having a file which would contain invalid Lisp, regardless
of it's value, in one of the two branches seems ... odd.

Anyway, I can work around the problem without too much hassle -- it's
not like I can't live without building autoloads there when things
update.

        Daniel

-- 
It is disconcerting to reflect on the number of students we have flunked in
chemistry for not knowing what we later found to be untrue.
        -- quoted by Robert L. Weber's, _Science With a Smile_, 1992



  reply	other threads:[~2002-03-26 11:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-26  6:21 Daniel Pittman
2002-03-26 10:21 ` Kai Großjohann
2002-03-26 11:13   ` Daniel Pittman [this message]
2002-03-26 12:29     ` Kai Großjohann
2002-03-26 13:05       ` Daniel Pittman

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=87d6xrwpi1.fsf@inanna.rimspace.net \
    --to=daniel@rimspace.net \
    /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 NNTP newsgroup(s).