From: "Eli Zaretskii" <eliz@elta.co.il>
Subject: Re: virtual space?
Date: Wed, 22 Oct 2003 19:44:16 +0200 [thread overview]
Message-ID: <6480-Wed22Oct2003194416+0200-eliz@elta.co.il> (raw)
In-Reply-To: <3F96A856.1060909@yahoo.com> (message from Kevin Rodgers on Wed, 22 Oct 2003 09:55:02 -0600)
> From: Kevin Rodgers <ihs_4664@yahoo.com>
> Newsgroups: gnu.emacs.help
> Date: Wed, 22 Oct 2003 09:55:02 -0600
> >
> > 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.
I understood that.
> But he wants it displayed without any window manager decorations.
I understood that, too, but didn't understand _why_ he wants that, and
asked for explanations.
> > 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 understood that, but didn't understand why.
> > 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?
Because no one has coded it, I guess. See x_create_tip_frame for how
it is done; someone needs to add similar code to the function
x-create-frame which is used to create all the other frames on
graphics displays.
next prev parent reply other threads:[~2003-10-22 17:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-19 21:31 virtual space? Michael Durland
2003-10-19 21:52 ` Sudarshan S. Chawathe
2003-10-19 23:25 ` Michael Durland
2003-10-20 5:36 ` Björn Lindström
2003-10-21 1:52 ` Michael Durland
2003-10-21 4:07 ` Dan Anderson
2003-10-21 5:44 ` Eli Zaretskii
2003-10-21 8:47 ` Barman Brakjoller
2003-10-21 15:04 ` Stefan Monnier
2003-10-22 1:33 ` Michael Durland
[not found] ` <mailman.2047.1066715377.21628.help-gnu-emacs@gnu.org>
2003-10-22 1:26 ` Michael Durland
2003-10-22 14:37 ` Eli Zaretskii
[not found] ` <mailman.2213.1066834114.21628.help-gnu-emacs@gnu.org>
2003-10-22 15:55 ` Kevin Rodgers
2003-10-22 17:44 ` Eli Zaretskii [this message]
[not found] ` <mailman.2225.1066844986.21628.help-gnu-emacs@gnu.org>
2003-12-02 21:09 ` Kai Grossjohann
2003-10-22 17:29 ` Stefan Monnier
2003-12-02 21:04 ` Kai Grossjohann
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6480-Wed22Oct2003194416+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).