From: Robert Weiner <rsw@gnu.org>
To: emacs-devel <emacs-devel@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, Richard Stallman <rms@gnu.org>
Subject: Re: Any way to prevent window splits for a window or a major-mode
Date: Tue, 5 Dec 2017 17:45:26 -0500 [thread overview]
Message-ID: <CA+OMD9jti-3NF7fUE0pOkL0=EbhegdgYk233ib92cw-06oD+7w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
On Fri, Dec 1, 2017 at 4:35 PM, Robert Weiner <rsw@gnu.org> wrote:
> I have looked through the Windows sections of the Elisp manual but did not
> see an option that would do this specifically
>
Now that we have resolved this issue by utilizing
display-buffer-in-side-window, I went back to the Elisp manual to see why I
did not
find this. I was looking for information related to preserving the display
of a window and window splitting. That led me to
both the sections on "Preserving Window Sizes" and "Splitting Windows"
neither of which have references to the sections on
Side Windows or Atomic Windows.
The last two paragraphs in the "Displaying Buffers in Side Windows" section
are key to understanding that one would want
to use a side window when a non-splittable window is desired. I think a
mention of that (and/or link) should be added near the
beginning of the "Splitting Windows" section. It might save others a lot
of time.
Regards,
Bob
>
[-- Attachment #2: Type: text/html, Size: 2604 bytes --]
next reply other threads:[~2017-12-05 22:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 22:45 Robert Weiner [this message]
2017-12-06 8:56 ` Any way to prevent window splits for a window or a major-mode martin rudalics
2017-12-06 18:11 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2017-12-01 21:35 Robert Weiner
2017-12-01 21:40 ` Eric Abrahamsen
2017-12-01 21:57 ` Drew Adams
2017-12-02 10:17 ` martin rudalics
2017-12-04 13:44 ` Robert Weiner
2017-12-05 8:53 ` martin rudalics
2017-12-05 17:04 ` Robert Weiner
2017-12-06 8:56 ` martin rudalics
2017-12-06 15:44 ` Robert Weiner
2017-12-07 9:27 ` martin rudalics
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='CA+OMD9jti-3NF7fUE0pOkL0=EbhegdgYk233ib92cw-06oD+7w@mail.gmail.com' \
--to=rsw@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=rswgnu@gmail.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).