From: Jan Vroonhof <vroonhof@math.ethz.ch>
Subject: Re: url-insert-file-contents
Date: 22 Apr 1997 17:12:57 +0200 [thread overview]
Message-ID: <byiv1f147a.fsf@midget.math.ethz.ch> (raw)
In-Reply-To: wmperry@aventail.com's message of 22 Apr 1997 07:54:43 -0700
wmperry@aventail.com (William M. Perry) writes:
> url-insert-file-contents has not changed in ages. It has always
> returned:
>
> (kill-buffer url-working-buffer)
>
> docs for kill-buffer say:
> Value is t if the buffer is actually killed, nil if user says no.
This is probably related to the gnuserv.el problem that aliasses
kill-buffer to server-kill-buffer which does not have the above
behaviour. It would not be that difficult to fix, but it probably
needs a rethink anyway. My be all the functionality should be in
kill-buffer-hook.
Jan
next prev parent reply other threads:[~1997-04-22 15:12 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 ` Jan Vroonhof [this message]
1997-04-22 16:20 ` url-insert-file-contents Tony Bennett
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=byiv1f147a.fsf@midget.math.ethz.ch \
--to=vroonhof@math.ethz.ch \
/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).