From xemacs-m  Fri Dec 20 13:35:00 1996
Received: from jagor.srce.hr (hniksic@jagor.srce.hr [161.53.2.130])
          by xemacs.cs.uiuc.edu (8.8.4/8.8.4) with ESMTP
	  id NAA15355 for <xemacs-beta@xemacs.org>; Fri, 20 Dec 1996 13:34:54 -0600 (CST)
Received: (from hniksic@localhost)
          by jagor.srce.hr (8.8.4/8.8.4)
	  id UAA18821; Fri, 20 Dec 1996 20:34:48 +0100 (MET)
Sender: hniksic@public.srce.hr
To: xemacs-beta@xemacs.org
Subject: Broken stuff (e.g. make-indirect-buffer)
X-URL: ftp://gnjilux.cc.fer.hr/pub/unix/util/wget/
X-Attribution: Hrv
X-Face: &}4JQk=L;e.~x+|eo]#DGk@x3~ed!.~lZ}YQcYb7f[WL9L'Z*+OyA\nAEL1M(".[qvI#a2E
 6WYI5>>e7'@_)3Ol9p|Nn2wNa/;~06jL*B%tTcn/XvhAu7qeES0\|MF%$;sI#yn1+y"
From: Hrvoje Niksic <hniksic@srce.hr>
Date: 20 Dec 1996 20:34:47 +0100
Message-ID: <kig681x2enc.fsf@jagor.srce.hr>
Lines: 20
X-Mailer: Red Gnus v0.76/XEmacs 19.14

I don't know about other people, but unimplemented things handled like
make-indirect-buffer annoy me.  I don't think
"make-indirect-buffer not yet implemented, oops"
is funny at all -- packages validly checking for the function using
(fboundp 'make-indirect-buffer) will make wrong assumptions.

Is there any more of such stuff?  I think we should remove these
things until the functions are *really* implemented.

As a digression, I would like to know about the status of multiple
frames on tty-s.  Would it be hard to implement?  To me it somehow
looks very simple -- if someone would tell me where to start, I can
give it a try.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
WWW:          World-Wide-Waste.  Waste management corporation, which
              handles the billions of tons of garbage generated by just
              about everybody these days.

