From: martin rudalics <rudalics@gmx.at>
To: Nicolas Richard <theonewiththeevillook@yahoo.fr>, 18304@debbugs.gnu.org
Subject: bug#18304: 24.3.92; Making and using side windows
Date: Thu, 21 Aug 2014 11:24:18 +0200 [thread overview]
Message-ID: <53F5BAC2.50008@gmx.at> (raw)
In-Reply-To: <87tx576tj7.fsf@geodiff-mac3.ulb.ac.be>
> emacs -q --eval '(display-buffer-in-major-side-window (current-buffer) (quote right) 0)' -f calendar
>
> I get an error:
>
> Debugger entered--Lisp error: (error "Cannot split side window or parent of side window")
> signal(error ("Cannot split side window or parent of side window"))
> error("Cannot split side window or parent of side window")
> byte-code(...)
> split-window(nil nil)
> split-window-below()
> calendar-basic-setup(nil)
> calendar(nil)
> call-interactively(calendar record nil)
> command-execute(calendar record)
> execute-extended-command(nil "calendar")
> call-interactively(execute-extended-command nil nil)
> command-execute(execute-extended-command)
>
> I have no idea if this is a bug
There were at least two bugs here, namely
(1) `calendar-basic-setup' calls `split-window-below' without checking
whether the selected window can be split at all.
(2) `window-splittable-p' doesn't check whether the argument window is a
side window.
Both should be fixed with revision 117719 on trunk.
> because I don't know how the user is
> supposed to use/create side windows (see also #18170).
Bugs like the ones you found here should get fixed before promoting side
windows generally.
BTW, if you intend to put the calendar in a side window
emacs -q --eval '(display-buffer-in-major-side-window (current-buffer) (quote bottom) 0)' -f calendar
should look better.
martin
next prev parent reply other threads:[~2014-08-21 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 15:59 bug#18304: 24.3.92; Making and using side windows Nicolas Richard
2014-08-21 9:24 ` martin rudalics [this message]
2014-08-21 9:36 ` Nicolas Richard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53F5BAC2.50008@gmx.at \
--to=rudalics@gmx.at \
--cc=18304@debbugs.gnu.org \
--cc=theonewiththeevillook@yahoo.fr \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.