Gnus development mailing list
 help / color / mirror / Atom feed
From: gsstark@MIT.EDU (Greg Stark)
Cc: ding@ifi.uio.no
Subject: Re: Generating the info-files under zsh
Date: 14 Jan 1996 01:10:45 -0500	[thread overview]
Message-ID: <ycqpwcn2tne.fsf@bill-the-cat.mit.edu> (raw)
In-Reply-To: steve@miranova.miranova.com's message of 12 Jan 1996 08:58:15 -0800


> 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.

This node is a problem in Info as well, I can't select it from the menu, but I
can select the next one and then go to the previous.  In various places it
shows up as "A Programmer@'s" or "A Programmer's" Guide, and in the printed
version there's an grave accent on the s.

greg


  reply	other threads:[~1996-01-14  6:10 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
1996-01-14  6:10     ` Greg Stark [this message]
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=ycqpwcn2tne.fsf@bill-the-cat.mit.edu \
    --to=gsstark@mit.edu \
    --cc=ding@ifi.uio.no \
    /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).