sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: Scott Schwartz <schwartz@groucho.cs.psu.edu>
To: Sam Fans <sam-fans@hawkwind.utcs.toronto.edu>
Subject: Re: quit with modified files
Date: Wed, 26 May 1993 20:21:12 -0400	[thread overview]
Message-ID: <93May26.202013edt.2620@groucho.cs.psu.edu> (raw)
In-Reply-To: Your message of "Tue, 25 May 1993 19:07:35 EDT." <93May25.190741edt.2688@hawkwind.utcs.toronto.edu>

Thanks for the patch Chris.  But now I have a second question. :-)
Consider this:

	; sam/sam -d                 
	B /etc/fstab
	 -. /etc/fstab
	i
	foo
	.
	D /etc/fstab
	?changes to "/etc/fstab"
	B /etc/svdtab
	 -. /etc/svdtab
	D /etc/fstab
	q

In other words, the second close attempt on a file will always succeed,
even if other operations have taken place in the meantime.  That seems
rather aggressive to me; when the man page talks about a ``subsequent
D'', I expected that it meant an immediately subsequent one.



  reply	other threads:[~1993-05-27  0:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-05-24 18:48 Scott Schwartz
1993-05-25 23:07 ` Chris Siebenmann
1993-05-27  0:21   ` Scott Schwartz [this message]
1993-05-26  4:30 Chris Siebenmann

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=93May26.202013edt.2620@groucho.cs.psu.edu \
    --to=schwartz@groucho.cs.psu.edu \
    --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).