From: "Mark H. Wilkinson" <mhw@minster.york.ac.uk>
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: hiding sam window
Date: Wed, 19 Jan 1994 10:01:42 -0500 [thread overview]
Message-ID: <swordfish.758992539@minster.york.ac.uk> (raw)
In-Reply-To: Steve_Kilbane's message of Tue, 18 Jan 1994 07:22:28 -0500
> a word of warning for anyone using mark wilkinson's patch to add a "hide"
> option to menu 3 - don't hide the sam window!
Just to clarify, Steve's talking about a patch which never actually got
posted to this list. The hide option removed a window without removing
a file from sam's internal list; unfortunately sam and samterm disagree
about whether this is a good thing and a core dump can result. If anyone
else has a copy of the patch I'd recommend removing it for the time being.
-Mark.
next reply other threads:[~1994-01-19 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-01-19 15:01 Mark H. Wilkinson [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-01-18 12:22 Steve_Kilbane
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=swordfish.758992539@minster.york.ac.uk \
--to=mhw@minster.york.ac.uk \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
/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).