From: Vincent Montressor <vmontressor@yahoo.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Want old "*compilation*" behavior back!
Date: Tue, 17 May 2011 12:50:13 -0700 (PDT) [thread overview]
Message-ID: <973189.67014.qm@web161408.mail.bf1.yahoo.com> (raw)
In-Reply-To: <4DD2919F.6030304@gmx.at>
Ah-hah, you're right! I just tried
(setq split-height-threshold nil)
... and that seems to do the trick. (Misunderstanding what it meant, I had
tried setting it to small values; I hadn't tried large values or nil.)
I'll have to play with it some more to be sure, but I think I'm fixed. Thank
you!
----- Original Message ----
From: martin rudalics <rudalics@gmx.at>
To: vmontressor@yahoo.com
Cc: help-gnu-emacs@gnu.org
Sent: Tue, May 17, 2011 8:17:51 AM
Subject: Re: Want old "*compilation*" behavior back!
> Ah, you're right about the "buffer" vs. "window" and horizontal vs. vertical
> confusion; sorry about that.
You're not the first one ;-)
> But yes, it does the same unwanted thing with "emacs -Q" as well. And it
seems
> (from experimenting) that split-height/width-threshold don't control this.
Any
> other thoughts?
>
> I would be 90% satisfied with just solving this for *compilation*, and close
to
> 100% satisfied if this got solved for *grep* as well.
>
> (I'm encouraged that it doesn't seem to do this in the most recent builds, at
> least not for you. Maybe this was just an aberration in the version I'm
>using?)
I don't remember. But I completely fail to understand that setting
`split-height-threshold' and `split-width-threshold' to nil or very
large values can allow `display-buffer' to split a window (unless
there's only one window on the frame). Which values did you try?
martin
next prev parent reply other threads:[~2011-05-17 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 15:17 Want old "*compilation*" behavior back! martin rudalics
2011-05-17 19:50 ` Vincent Montressor [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-15 7:26 martin rudalics
2011-05-17 1:23 ` Vincent Montressor
2011-05-13 23:58 Vincent Montressor
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=973189.67014.qm@web161408.mail.bf1.yahoo.com \
--to=vmontressor@yahoo.com \
--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).