From owner-freebsd-ports  Sat Jul 22 14:21:09 1995
Return-Path: ports-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id OAA04568
          for ports-outgoing; Sat, 22 Jul 1995 14:21:09 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id OAA04561
          for <ports@FreeBSD.org>; Sat, 22 Jul 1995 14:21:07 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id OAA04640; Sat, 22 Jul 1995 14:21:01 -0700
Date: Sat, 22 Jul 1995 14:21:01 -0700
Message-Id: <199507222121.OAA04640@silvia.HIP.Berkeley.EDU>
To: jmacd@uclink.berkeley.edu
CC: bug-gnu-emacs@prep.ai.mit.edu, ports@FreeBSD.org
In-reply-to: <199507221026.DAA06542@uclink.berkeley.edu> (jmacd@uclink.berkeley.edu)
Subject: Re: M-x man hangs emacs 19.29[FreeBSD]
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: ports-owner@FreeBSD.org
Precedence: bulk

 * In GNU Emacs 19.29.3 (i386-unknown-freebsd2.0.0, X toolkit) of Sat Jul  1 1995 on axis.HIP.Berkeley.EDU
 * configured using  --with-x-toolkit=athena
 * 
 * As stated above, M-x man hangs emacs under FreeBSD.  MANPATH is
 * set properly.  For the FreeBSD recipients, does M-x man work?
 * Why is it always me?

It hung on me on thud.cdrom.com too.  It is running something that is
pretty much FreeBSD-2.0.5R.  It doesn't hang on silvia.hip.berkeley.edu,
which is running FreeBSD-2.2-current.

They are both configured with "--with-x-toolkit" (no "=athena"),
unless someone recompiled emacs on thud.

Satoshi