* Rookie Question: No Separate Minibuffer
@ 2005-12-01 9:01 roland.rau
2005-12-01 18:47 ` Kevin Rodgers
2005-12-01 20:57 ` Stefan Monnier
0 siblings, 2 replies; 4+ messages in thread
From: roland.rau @ 2005-12-01 9:01 UTC (permalink / raw)
Dear all,
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).
Thanks,
Roland
[1] "GNU Emacs 22.0.50.2 i386-mingw-nt5.1.2600) of 2005-04-17 on
LAPTOP"
[2] "XEmacs 21.4 (patch 13) \"Rational FORTRAN\" [Lucid]
(i586-pc-win32) of Sun May 25 2003 on TSUNAMI"
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Rookie Question: No Separate Minibuffer
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
1 sibling, 0 replies; 4+ messages in thread
From: Kevin Rodgers @ 2005-12-01 18:47 UTC (permalink / raw)
roland.rau@gmail.com wrote:
> 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).
You should have checked the Emacs manual and the Emacs Lisp manual
first. Something is setting the frame's minibuffer frame parameter to
nil.
--
Kevin Rodgers
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Rookie Question: No Separate Minibuffer
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
2005-12-05 10:52 ` roland.rau
1 sibling, 1 reply; 4+ messages in thread
From: Stefan Monnier @ 2005-12-01 20:57 UTC (permalink / raw)
> 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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Rookie Question: No Separate Minibuffer
2005-12-01 20:57 ` Stefan Monnier
@ 2005-12-05 10:52 ` roland.rau
0 siblings, 0 replies; 4+ messages in thread
From: roland.rau @ 2005-12-05 10:52 UTC (permalink / raw)
Thanks to Stefan Monnier and Kevin Rodgers for their replies!
It was, indeed, the case: In some additional file loaded from the
.emacs file, minibuffer's frame parameter was set to nil.
Sorry for the late acknowledgment, but I was away for a few days.
Best,
Roland
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-12-05 10:52 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2005-12-05 10:52 ` roland.rau
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).