Gnus development mailing list
 help / color / mirror / Atom feed
From: Steven L Baur <steve@miranova.com>
Subject: Re: Make in texinfo/ has been failing for me.
Date: 10 Oct 1996 20:49:18 -0700	[thread overview]
Message-ID: <m2u3s2dutd.fsf@deanna.miranova.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 10 Oct 1996 23:40:08 +0100

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

>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

> Wesley.Hardaker@sphys.unil.ch writes:

Wes> doing a 'make EMACS=xemacs' in the 'texi' directory has been
Wes> failing for me.  It prints a message saying its loading the
Wes> texinfmt library and then quits without doing anything else.

Lars> It's an XEmacs bug, I guess, but I haven't really looked into it.

Yup.  XEmacs command line processing needs some work.  Try brute
forcing it with the attached files, and calling them:

xemacs -batch -l xemacs-hack-gnusman.el
xemacs -batch -l xemacs-hack-messageman.el

[It's not pretty but it seems to work]

            ;; Using the mark to pass bounds this way
            ;; is kludgy, but it's not worth fixing. -- rms.

[-- Attachment #2: xemacs-hack-gnusman.el --]
[-- Type: application/octet-stream, Size: 108 bytes --]

(load "texinfmt")
(find-file "gnus.texi")
(texinfo-every-node-update)
(texinfo-format-buffer)
(save-buffer)

[-- Attachment #3: xemacs-hack-messageman.el --]
[-- Type: application/octet-stream, Size: 111 bytes --]

(load "texinfmt")
(find-file "message.texi")
(texinfo-every-node-update)
(texinfo-format-buffer)
(save-buffer)

  reply	other threads:[~1996-10-11  3:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-10-10  9:30 Wesley.Hardaker
1996-10-10 22:40 ` Lars Magne Ingebrigtsen
1996-10-11  3:49   ` Steven L Baur [this message]
1996-10-11  6:42     ` Wesley.Hardaker

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=m2u3s2dutd.fsf@deanna.miranova.com \
    --to=steve@miranova.com \
    /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).