From: Peter S Galbraith <GalbraithP@dfo-mpo.gc.ca>
Cc: Dan Cardamore <dan@hld.ca>
Subject: Re: dabbrev not to create a new window
Date: Thu, 31 Oct 2002 09:00:49 -0500 [thread overview]
Message-ID: <20021031140049.A9C55297B0@mixing.qc.dfo.ca> (raw)
In-Reply-To: Message from "Peter Milliken" <peterm@resmed.com.au> of "Thu, 31 Oct 2002 08:06:30 +1100." <WQXv9.21940$Sr6.657957@ozemail.com.au>
"Dan Cardamore" <dan@hld.ca> wrote:
> I'm using dabbrev and I'd like to have it show me the possible
> completions without splitting my window in half.
Peter Milliken <peterm@resmed.com.au> wrote:
> I wrote a small routine that provides word completion at point (as does
> dabbrev).
[cut]
>
> Other people have found it useful, you might also. It can be found on the
> Emacs Wiki site at http://www.emacswiki.org/elisp/expand-a-word.el.
Sounds like a good tool!
Dan, it sounds like framepop.el will also do what you want.
It's description follows:
Defines temp-buffer-show-function to display buffers in a dedicated
temporary frame (and so requires a display which can accomodate
separate frames). The frame is automatically shrink-wrapped to just
contain the buffer (restricted to a maximum and minimum
size). Buffers thus affected include *Help*, completion buffers and
buffer listings.
Commands are provided for manipulating the FramePop frame:
scrolling, resizing, window manager functions, and also a facility
for copying the displayed buffer. You need never lose that handy
*Help* buffer again!
You'll find it with google search (or email me and I'll send a copy
along with the setup I use).
Peter
prev parent reply other threads:[~2002-10-31 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 18:24 dabbrev not to create a new window Dan Cardamore
2002-10-30 21:06 ` Peter Milliken
[not found] ` <peterm@resmed.com.au>
2002-10-31 14:00 ` Peter S Galbraith [this message]
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=20021031140049.A9C55297B0@mixing.qc.dfo.ca \
--to=galbraithp@dfo-mpo.gc.ca \
--cc=dan@hld.ca \
/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).