From: Eli Zaretskii <eliz@gnu.org>
Cc: dave@boost-consulting.com, emacs-devel@gnu.org
Subject: Re: [NT] Problem with `man' function
Date: Thu, 27 Oct 2005 07:06:46 +0200 [thread overview]
Message-ID: <ur7a7eeft.fsf@gnu.org> (raw)
In-Reply-To: <E1EUwZn-0003Rl-Mp@fencepost.gnu.org> (rms@gnu.org)
> From: "Richard M. Stallman" <rms@gnu.org>
> Date: Wed, 26 Oct 2005 21:29:07 -0400
> Cc: emacs-devel@gnu.org
>
> > Nobody can tell what the best fix is
> > without first finding out what is really wrong.
>
> I can tell you that if you remove the awk command at the end of the
> filter chain you still get something that looks like a man page.
> Otherwise, you get something that looks like
>
> 0 (00, 0x0) = ?\C-@
>
> And the process sentinel, understandably, has a hard time parsing it.
> I don't know enough about awk nor about the NT shell command processor
> to get much further with this one.
>
> This might be enough to enable the people interested in Windows
> to fix it.
Not for me, it isn't. Sorry.
To try to debug and fix it, I need to know:
(1) What shell is being used to run the commands in the pipeline
that produces the man page;
(2) What ports of gawk and Sed are used (presumably Cygwin, but
that's a guess).
next prev parent reply other threads:[~2005-10-27 5:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-23 12:02 [NT] Problem with `man' function David Abrahams
2005-10-23 16:25 ` Eli Zaretskii
2005-10-24 1:00 ` Richard M. Stallman
2005-10-25 22:06 ` David Abrahams
2005-10-27 1:29 ` Richard M. Stallman
2005-10-27 5:06 ` Eli Zaretskii [this message]
2005-10-27 11:00 ` David Abrahams
2005-11-05 19:21 ` Eli Zaretskii
2006-05-10 20:54 ` Dave Abrahams
2006-05-11 3:49 ` Eli Zaretskii
2006-05-11 4:26 ` David Abrahams
2006-05-11 11:44 ` David Abrahams
2006-05-11 18:36 ` Eli Zaretskii
2006-05-11 20:23 ` David Abrahams
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=ur7a7eeft.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dave@boost-consulting.com \
--cc=emacs-devel@gnu.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).