Gnus development mailing list
 help / color / mirror / Atom feed
From: steve@miranova.miranova.com (Steven L. Baur)
Subject: Re: Generating the info-files under zsh
Date: 12 Jan 1996 08:58:15 -0800	[thread overview]
Message-ID: <m2buo9qriv.fsf@miranova.com> (raw)
In-Reply-To: "d. cord hall"'s message of 10 Jan 1996 11:10:22 -0800

>>>>> "d." == "d cord hall" <dhall@apk.net> writes:

    d.> ð thus on Wed, 10 Jan 1996 14:13:09 +0100, Andrew virtually
    d.> scripted...
    Andrew> When browsing the gnus info-files, and jumping into the
    Andrew> Index section I see:

    Andrew> Yep I have zsh as login-shell, and are there any1 else out
    Andrew> there with the same problems, or have I done something
    Andrew> wrong as usual?

    d.> unfortunately I can't reproduce this problem, and yes I'm
    d.> running zsh on linux 1.3.20 kernal (ELF platform).  i do know
    d.> there are a couple of nodes missing here and there.  possible
    d.> info file corruption?

I too have zsh as a login shell, but I'm having more trouble with Perl
(texi2html).  The (September) Gnus info files have been bad for a long
time.  The current problem is with the ``A Programmer's Guide to
Gnus'' node.

--
steve@miranova.com baur


  reply	other threads:[~1996-01-12 16:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-01-10 13:13 Andrew Eskilsson
1996-01-10 17:28 ` Generating the info-files under zsh, solved Andy Eskilsson
1996-01-10 19:10 ` Generating the info-files under zsh d. cord hall
1996-01-12 16:58   ` Steven L. Baur [this message]
1996-01-14  6:10     ` Greg Stark
1996-01-15 23:17       ` Lars Magne Ingebrigtsen

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