From: David Golden <david.golden@oceanfree.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs minibuffer - text wrapping of code completion hints from SLIME
Date: Sun, 02 Dec 2007 03:10:18 +0000 [thread overview]
Message-ID: <ump4j.23566$j7.444140@news.indigo.ie> (raw)
In-Reply-To: ce10e230-df19-47ab-a6ba-cf4b78a0292d@t47g2000hsc.googlegroups.com
joubert.nel@gmail.com wrote:
> However, when code-completion text is automatically put there by SLIME
> (for Common Lisp hacking) and it doesn't fit the width, there's no
> text wrapping - i.e. only the 1st line of the minibuffer contains
> text.
>
> Any ideas?
>
Not sure (as usual, might be better directed to the slime mailing
list...), but you might want to look into
M-x customize-variable
slime-autodoc-use-multiline-p
(though it sounds like you _don't_ want the minibuffer
itself resizing, ho hum)
prev parent reply other threads:[~2007-12-02 3:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-01 22:34 Emacs minibuffer - text wrapping of code completion hints from SLIME joubert.nel
2007-12-02 3:10 ` David Golden [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='ump4j.23566$j7.444140@news.indigo.ie' \
--to=david.golden@oceanfree.net \
--cc=help-gnu-emacs@gnu.org \
/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).