unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Doug Morgan <dougrm@sprynet.com>
Cc: 12380@debbugs.gnu.org
Subject: bug#12380: more control over window splitting
Date: Sun, 13 Feb 2022 10:30:33 +0100	[thread overview]
Message-ID: <87pmnrw1ty.fsf@gnus.org> (raw)
In-Reply-To: <504A43D2.1010307@sprynet.com> (Doug Morgan's message of "Fri, 07 Sep 2012 11:58:26 -0700")

Doug Morgan <dougrm@sprynet.com> writes:

> emac version: 24.2.1
> cygwin
> Vista
>
> Edit a file
> C-x 2
> (OK, now you have a two windows split horizontally)
> C-x C-b
> One of the windows **splits vertically**(!!) to show the buffer menu.
> Older versions of emacs (I don't know how far back you have to go) use
> the "other" window of the two horizontally split window to display the
> menu.  The old way is by far the better way.  The same thing happens
> with C-x 4 C-f and I think other C-x 4 commands. All make for annoying
> work cleaning up your windows after the unwanted vertical splits
> happen.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

Are you still seeing this issue in recent Emacs versions?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2022-02-13  9:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 18:58 bug#12380: other window related commands broken Doug Morgan
2012-09-07 20:26 ` martin rudalics
2012-09-07 22:16   ` Doug Morgan
2012-09-08  1:00     ` Ken Brown
2012-09-08  8:18     ` martin rudalics
2012-09-09  1:34       ` Doug Morgan
2012-09-09 10:05         ` martin rudalics
2012-09-09 13:45           ` Ken Brown
2012-09-10  8:39             ` martin rudalics
2012-09-10 14:10               ` Ken Brown
2012-09-09 21:19           ` Doug Morgan
2022-02-13  9:30 ` Lars Ingebrigtsen [this message]
2022-03-14 10:34   ` bug#12380: more control over window splitting Lars Ingebrigtsen

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=87pmnrw1ty.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=12380@debbugs.gnu.org \
    --cc=dougrm@sprynet.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).