From: Tony Bennett <tbennett@chapelhill.hp.com>
Subject: Re: url-insert-file-contents
Date: Tue, 22 Apr 1997 12:20:20 -0400 (EDT) [thread overview]
Message-ID: <199704221620.MAA15871@uh-oh.chapelhill.hp.com> (raw)
In-Reply-To: message of William M. Perry (on , Apr 22/1997)
William> url-insert-file-contents has not changed in ages. It has always
William> returned:
William> (kill-buffer url-working-buffer)
William> docs for kill-buffer say:
William> Value is t if the buffer is actually killed, nil if user says no.
My XEmacs 19.15 kill-buffer returns nil on success. But I just noticed
it has following note in docstring, so gnuserv is overriding at least
some its behavior:
NOTE: This function has been enhanced to allow for remote editing
in the following way:
...
--tony
next prev parent reply other threads:[~1997-04-22 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-19 3:14 url-insert-file-contents Lars Magne Ingebrigtsen
1997-04-22 14:54 ` url-insert-file-contents William M. Perry
1997-04-22 15:12 ` url-insert-file-contents Jan Vroonhof
1997-04-22 16:20 ` Tony Bennett [this message]
1997-04-22 17:36 ` url-insert-file-contents William M. Perry
1997-04-24 12:05 ` url-insert-file-contents Lars Magne Ingebrigtsen
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=199704221620.MAA15871@uh-oh.chapelhill.hp.com \
--to=tbennett@chapelhill.hp.com \
/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).