From: Eli Zaretskii <eliz@gnu.org>
To: Christoph Arenz <tiga.arenz@web.de>
Cc: 54800-done@debbugs.gnu.org
Subject: bug#54800: 28.1; calc: Cursor positioned at weird position in calc stack
Date: Wed, 13 Apr 2022 16:11:04 +0300 [thread overview]
Message-ID: <83czhl3z87.fsf@gnu.org> (raw)
In-Reply-To: <44113a6c-9ff6-41e6-cf91-bbb3fea5da78@web.de> (message from Christoph Arenz on Tue, 12 Apr 2022 22:44:16 +0200)
> Date: Tue, 12 Apr 2022 22:44:16 +0200
> From: Christoph Arenz <tiga.arenz@web.de>
> Cc: 54800@debbugs.gnu.org
>
>
> > And there are still cases where above does not work correctly.
> > E.g. when using a theme which has different line heights for header
> > line and mode line than for text lines,
> > say M-x load-theme leuven .
> >
> > Approaching it differently seems to cover those cases as well:
> >
> > (vertical-motion (- 1 (window-body-height)))
>
> N.B.
> This works for me as long as line-spacing is nil.
> For non-nil there seems to be a bug in window-body-height.
> I have opened bug report #54894 for that.
Thanks, I think people who use line-spacing in Calc stack window, or
otherwise change the default height of a window-line, should know what
they are doing and what would be the result.
I installed the change to use the 'floor' argument to window-height,
and I think this works well enough in the "usual" use cases;
everything else would be a non-trivial enhancement. So I'm closing
this bug.
prev parent reply other threads:[~2022-04-13 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 19:44 bug#54800: 28.1; calc: Cursor positioned at weird position in calc stack Christoph Arenz
2022-04-09 7:34 ` Eli Zaretskii
2022-04-09 12:31 ` Christoph Arenz
2022-04-09 13:32 ` Eli Zaretskii
2022-04-11 10:25 ` Christoph Arenz
2022-04-11 11:27 ` Eli Zaretskii
2022-04-11 11:45 ` Eli Zaretskii
2022-04-11 14:53 ` Christoph Arenz
2022-04-12 15:45 ` Christoph Arenz
2022-04-12 20:44 ` Christoph Arenz
2022-04-13 13:11 ` Eli Zaretskii [this message]
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=83czhl3z87.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54800-done@debbugs.gnu.org \
--cc=tiga.arenz@web.de \
/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).