From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kevin Rodgers Newsgroups: gmane.emacs.help Subject: Re: virtual space? Date: Wed, 22 Oct 2003 09:55:02 -0600 Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: <3F96A856.1060909@yahoo.com> References: <87y8vgbhdc.fsf@lucien.dreaming> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1066838712 14047 80.91.224.253 (22 Oct 2003 16:05:12 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 22 Oct 2003 16:05:12 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Oct 22 18:05:10 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1ACLTy-00031m-00 for ; Wed, 22 Oct 2003 18:05:10 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1ACLT8-0008GA-D0 for geh-help-gnu-emacs@m.gmane.org; Wed, 22 Oct 2003 12:04:18 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!headwall.stanford.edu!fu-berlin.de!uni-berlin.de!170.207.51.80!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 63 Original-NNTP-Posting-Host: 170.207.51.80 Original-X-Trace: news.uni-berlin.de 1066838095 31382508 170.207.51.80 (16 [82742]) User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:0.9.4.1) Gecko/20020406 Netscape6/6.2.2 X-Accept-Language: en-us Original-Xref: shelby.stanford.edu gnu.emacs.help:117535 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:13466 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:13466 Eli Zaretskii wrote: >>From: "Michael Durland" >>Newsgroups: gnu.emacs.help >>Date: Wed, 22 Oct 2003 01:26:00 GMT >> >>>Emacs has an optional feature to cause it pop up a new frame >>>(``window'' in your parlance) to display comlpetion results. See the >>>documentation of the variable `special-display-buffer-names'. Why >>>isn't this sufficient? >> >>Is there a way to show these spawned special frames without an actual >>"frame" around them? That is, just the window contents with no title bar, >>no resizing border, etc. Just the actual contents inside the frame? > > > I don't understand why is this an issue (can you explain?), but it > sounds like the default Emacs behavior, whereby the possible > completions are shown in a window in the same frame, should satisfy > your needs, since there's no new frame borders involved. What am I > missing? He liked your suggestion to display the *Completions* buffer in its own frame, via special-display-buffer-names. But he wants it displayed without any window manager decorations. >>That way it could appear on top of the existing frame and have the >>appearance that it is part of the same frame. > > A separate window popped by Emacs by default in the same frame is, in > fact, part of the same frame. What's wrong with that? He wants the buffer/window to have a separate (special) frame. >>I found how to specify some properties >>of the frame, like position and size, but I didn't figure out how to specify >>system properties like what "style" the spawned frame has. > > What do you mean by the frame's ``style''? I think he wants a new frame property (e.g. window-manager-decorations) that he could specify in special-display-frame-alist. ... >>With a real frame, the "frame stuff" gets in the way of the actual >>contents, which in this case would be numbers with tick marks as >>periods. >> > > It is possible, at least in principle, to have frames without borders > (that's how Emacs creates tooltips, a.k.a. ``balloon help''), if that > is important, although I don't think you can do that now in Emacs. Exactly -- but why not? -- Kevin Rodgers