From: Eze Ogwuma <zcaceog@ucl.ac.uk>
Subject: Re: Problem with SOUP packing files
Date: 19 Feb 1997 02:17:24 +0000 [thread overview]
Message-ID: <m3raidedzf.fsf@ucl.ac.uk> (raw)
In-Reply-To: Eze Ogwuma's message of Wed, 12 Feb 1997 23:53:29 +0000 (GMT)
Some of the discussion on this occurred off the list; so if anyone is
interested, I found that setting the "shell-file-name" variable for
emacs on the server to "/bin/sh" solved the problem. Csh, Ksh and Tcsh
didn't work.
Eze Ogwuma <zcaceog@ucl.ac.uk> writes:
> Hi,
>
> I'm using SOUP to transfer stuff between machines. Each time I've used
> G-s-p to pack the SOUP files on the server, Gnus has exited with the
> message "Couldn't pack packet". A tgz file has been left in my home
> directory but the files in ~/SoupBrew are not deleted.
>
> The server uses Gnus v5.3
>
> The tgz file is correctly incorporated by Gnus on my home system.
>
> Can someone please tell me what's going?
>
> Thanks.
>
--
Eze Ogwuma
prev parent reply other threads:[~1997-02-19 2:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-02-12 23:53 Eze Ogwuma
1997-02-14 9:28 ` Lars Magne Ingebrigtsen
1997-02-14 15:21 ` Eze Ogwuma
1997-02-14 19:53 ` Eze Ogwuma
1997-02-19 2:17 ` Eze Ogwuma [this message]
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=m3raidedzf.fsf@ucl.ac.uk \
--to=zcaceog@ucl.ac.uk \
/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).