From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Rookie Question: No Separate Minibuffer
Date: Thu, 01 Dec 2005 15:57:55 -0500 [thread overview]
Message-ID: <87ek4wo7ry.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: 1133427660.358247.104160@f14g2000cwb.googlegroups.com
> I installed yesterday (for auctex & preview-latex) GNU Emacs[1].
> Coming from XEmacs[2], I evaluated my .emacs file (or .xemacs/init.el)
> line by line and after a short while, GNU Emacs behaved as I hoped.
> This morning, however, when I started GNU Emacs, the minibuffer turned
> out to be a separate window.
> Can somebody point me into the direction what I can do to avoid this?
> I checked the usenet for "separate minibuffer" but the results
> (typically from the 90s) dealt mainly with the wish to have a separate
> minibuffer (which is not my wish).
I'd grep for `minibuffer' in your .emacs and any elisp file it loads.
Stefan
next prev parent reply other threads:[~2005-12-01 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 9:01 Rookie Question: No Separate Minibuffer roland.rau
2005-12-01 18:47 ` Kevin Rodgers
2005-12-01 20:57 ` Stefan Monnier [this message]
2005-12-05 10:52 ` roland.rau
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=87ek4wo7ry.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.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).