From: Ken Raeburn <raeburn@raeburn.org>
Subject: Re: odd machine configs: mips-siemens, gec63, pfa50, att3b
Date: Sun, 21 Jul 2002 16:54:38 -0400 [thread overview]
Message-ID: <tx1n0skby41.fsf@raeburn.org> (raw)
In-Reply-To: <E17WMv7-00075b-00@kal-el.raeburn.org> (Ken Raeburn's message of "Sun, 21 Jul 2002 16:03:09 -0400")
> The mips-siemens config defines XSETINT in a way that looks broken; it
> appears to retain the old type of the object being set as the new
> type, instead of setting it to Lisp_Int. Does Emacs even work on this
> system? I'm inclined to just delete the macro, but I'd prefer
> confirmation.
I just discovered this was a problem in mips.h too and was cleaned up
a while back. I'll just go ahead and delete it.
next prev parent reply other threads:[~2002-07-21 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-21 20:03 odd machine configs: mips-siemens, gec63, pfa50, att3b Ken Raeburn
2002-07-21 20:54 ` Ken Raeburn [this message]
2002-07-21 22:02 ` Richard Stallman
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=tx1n0skby41.fsf@raeburn.org \
--to=raeburn@raeburn.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).