From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: okay@toyful.space, 46238@debbugs.gnu.org
Subject: bug#46238: 27.1; recenter-top-bottom in fullscreen
Date: Tue, 2 Feb 2021 17:03:39 +0100 [thread overview]
Message-ID: <9deebc9a-5231-d991-b3ad-9d745bbbce88@gmx.at> (raw)
In-Reply-To: <83im7a5wek.fsf@gnu.org>
> Is the below better?
It's perfect for me.
Thanks, martin
next prev parent reply other threads:[~2021-02-02 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 15:32 bug#46238: 27.1; recenter-top-bottom in fullscreen okay--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-02 8:42 ` martin rudalics
2021-02-02 15:20 ` Eli Zaretskii
2021-02-02 16:03 ` martin rudalics [this message]
2021-02-02 16:26 ` Eli Zaretskii
2021-04-21 3:04 ` Stefan Kangas
2021-04-21 7:03 ` martin rudalics
2021-04-21 8:51 ` Eli Zaretskii
2021-02-02 16:46 ` bug#46238: [External] : " Drew Adams
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=9deebc9a-5231-d991-b3ad-9d745bbbce88@gmx.at \
--to=rudalics@gmx.at \
--cc=46238@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=okay@toyful.space \
/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).