From: martin rudalics <rudalics@gmx.at>
To: Alan Mackenzie <acm@muc.de>, Eli Zaretskii <eliz@gnu.org>
Cc: 36250@debbugs.gnu.org
Subject: bug#36250: [PATCH] Allow Emacs to be resized arbitrarily
Date: Mon, 17 Jun 2019 10:43:57 +0200 [thread overview]
Message-ID: <c0caee40-f115-c559-947b-9b948fcd083e@gmx.at> (raw)
In-Reply-To: <20190617075444.83363.qmail@mail.muc.de>
> Yes. Having a whole number of lines in a window is a legitimate thing to
> want.
It's legitimate provided as long as you (1) don't want to display your
frame in fullscreen mode and the screen size is not an integral
multiple of the frame's character size, and (2) don't use a tiling
window manager.
> Also, I remember vaguely partial lines causing problems in Follow Mode in
> the past.
Doesn't that imply that one cannot use Follow Mode for *info* buffers?
> In case they cause problems there again, or somewhere else, we
> should have the ability to disable partial lines.
In general, you cannot "disable" partial lines on graphical displays
any more.
martin
next prev parent reply other threads:[~2019-06-17 8:43 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 17:59 bug#36250: Allow Emacs to be resized arbitrarily Konstantin Kharlamov
2019-06-16 18:01 ` bug#36250: [PATCH] " Konstantin Kharlamov
2019-06-16 18:24 ` Eli Zaretskii
2019-06-16 18:34 ` Eli Zaretskii
2019-06-17 8:22 ` martin rudalics
2019-06-17 8:41 ` Konstantin Kharlamov
2019-06-17 8:46 ` martin rudalics
2019-06-17 8:58 ` Juanma Barranquero
2019-06-16 18:42 ` Konstantin Kharlamov
2019-06-16 18:53 ` Eli Zaretskii
2019-06-16 18:59 ` Konstantin Kharlamov
2019-06-16 19:07 ` Eli Zaretskii
2019-06-16 19:15 ` Eli Zaretskii
2019-06-16 18:22 ` bug#36250: " Konstantin Kharlamov
2019-06-16 18:22 ` bug#36250: [PATCH v2] " Konstantin Kharlamov
2019-06-16 18:55 ` bug#36250: [PATCH v3] " Konstantin Kharlamov
2019-06-16 19:10 ` Eli Zaretskii
2019-06-17 12:32 ` Konstantin Kharlamov
2019-06-17 14:56 ` Eli Zaretskii
2019-06-18 20:34 ` Konstantin Kharlamov
2019-06-19 16:13 ` Eli Zaretskii
2020-08-26 10:26 ` Lars Ingebrigtsen
[not found] ` <mailman.222.1560709505.10840.bug-gnu-emacs@gnu.org>
2019-06-17 7:54 ` bug#36250: [PATCH] " Alan Mackenzie
2019-06-17 8:43 ` martin rudalics [this message]
2019-06-17 14:38 ` Eli Zaretskii
2019-06-18 8:17 ` martin rudalics
2019-06-18 15:49 ` Eli Zaretskii
2019-06-17 8:21 ` bug#36250: " martin rudalics
2019-06-17 8:27 ` Konstantin Kharlamov
2019-06-17 8:44 ` martin rudalics
2019-06-17 9:14 ` Konstantin Kharlamov
2019-06-17 9:46 ` martin rudalics
2019-06-17 14:41 ` Eli Zaretskii
2019-06-18 20:35 ` bug#36250: [PATCH] Improve a bit frame-resize-pixelwise documentation Konstantin Kharlamov
2019-06-18 20:38 ` Andreas Schwab
2019-06-19 16:16 ` Eli Zaretskii
2019-06-28 11:27 ` Konstantin Kharlamov
2019-06-28 13:16 ` Eli Zaretskii
2019-06-28 13:59 ` Konstantin Kharlamov
2019-06-28 14:22 ` Eli Zaretskii
2019-06-28 14:34 ` Konstantin Kharlamov
2019-06-28 14:49 ` Eli Zaretskii
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=c0caee40-f115-c559-947b-9b948fcd083e@gmx.at \
--to=rudalics@gmx.at \
--cc=36250@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
/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).