From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: xfq.free@gmail.com, 14993@debbugs.gnu.org
Subject: bug#14993: [PATCH] Update information about fonts
Date: Sat, 15 Aug 2020 13:06:37 +0200 [thread overview]
Message-ID: <m2k0y0418i.fsf@gmail.com> (raw)
In-Reply-To: <87imdk1a0c.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 15 Aug 2020 12:25:23 +0200")
>>>>> On Sat, 15 Aug 2020 12:25:23 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:
Lars> Robert Pluim <rpluim@gmail.com> writes:
>> I guess you'd need to be a bit careful that successive frames didnʼt
>> overlap with previous ones (especially the last one).
Lars> Yeah... hm... and with images that may overlap when "scrolling down".
Lars> Well, that's a problem in general: A frame may show half a line at the
Lars> bottom, for instance, and we don't really want that when printing the
Lars> buffer.
binding frame-resize-pixelwise to nil I think solves the line issue,
not necessarily the image issue.
Lars> So it would take more than just wrapping that function to have a
Lars> workable solution...
Could you create a single frame that shows the entire buffer and use
that? Probably that would run into problems with window managers not
letting you create frames larger than the screen size.
Robert
next prev parent reply other threads:[~2020-08-15 11:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 9:16 bug#14993: [PATCH] Update information about fonts Xue Fuqiao
2013-07-31 13:54 ` Xue Fuqiao
2013-07-31 14:13 ` Wolfgang Jenkner
2013-07-31 15:46 ` Eli Zaretskii
2013-08-02 13:10 ` Kenichi Handa
2013-08-02 13:51 ` Eli Zaretskii
2016-02-24 4:32 ` Lars Ingebrigtsen
2016-02-24 17:17 ` Eli Zaretskii
2020-08-13 11:20 ` Lars Ingebrigtsen
2020-08-13 12:48 ` Robert Pluim
2020-08-14 11:42 ` Lars Ingebrigtsen
2020-08-14 14:08 ` Robert Pluim
2020-08-15 10:25 ` Lars Ingebrigtsen
2020-08-15 11:06 ` Robert Pluim [this message]
2020-08-15 11:17 ` Lars Ingebrigtsen
2020-10-13 1:46 ` Lars Ingebrigtsen
2020-08-13 13:25 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2k0y0418i.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=14993@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=xfq.free@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 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.