From: martin rudalics <rudalics@gmx.at>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 30141@debbugs.gnu.org
Subject: bug#30141: (26.0.91; text-pixel dimensions not properly saved by desktop-save-mode sometimes)
Date: Wed, 14 Mar 2018 09:14:03 +0100 [thread overview]
Message-ID: <5AA8D9CB.4010509@gmx.at> (raw)
In-Reply-To: <CAHyO48xO1-kV_frGKL7k9uv240mvhzoaeWi9rtnCELEN3Uhc1A@mail.gmail.com>
>> We could provide a 'resize-pixelwise' frame parameter which would
>> assure that saving is done in pixels for the corresponding frame.
>> Would that help?
>
> Yes, that would work for me. So then setting that frame-parameter
> would be manual and separate from setting `frame-resize-pixelwise'?
When creating a frame we could make the parameter inherit from the
current value of `frame-resize-pixelwise' unless the parameter has
been specified explicitly for the new frame. But unless we can find a
sufficiently strong reason for implementing such a parameter, it might
be better to pursue your proposal first. This would avoid that we
have to introduce a function like `frame-resize-pixelwise' which tells
for a specific frame whether it should be resized pixelwise or not.
martin
next prev parent reply other threads:[~2018-03-14 8:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 1:24 bug#30141: 26.0.91; text-pixel dimensions not properly saved by desktop-save-mode sometimes Aaron Jensen
2018-01-17 5:43 ` bug#30141: (26.0.91; text-pixel dimensions not properly saved by desktop-save-mode sometimes) Aaron Jensen
2018-01-17 8:49 ` Robert Pluim
2018-01-17 11:45 ` Aaron Jensen
2018-01-17 9:12 ` martin rudalics
2018-01-17 11:50 ` Aaron Jensen
2018-01-17 11:59 ` Aaron Jensen
2018-01-19 18:55 ` martin rudalics
2018-01-19 19:00 ` Aaron Jensen
2018-01-20 10:35 ` martin rudalics
2018-01-20 10:50 ` Eli Zaretskii
2018-01-20 14:07 ` martin rudalics
2018-01-20 14:33 ` Eli Zaretskii
2018-01-22 9:54 ` martin rudalics
2018-02-13 10:23 ` martin rudalics
2018-03-12 22:18 ` Aaron Jensen
2018-03-13 7:26 ` martin rudalics
2018-03-13 15:32 ` Aaron Jensen
2018-03-14 8:14 ` martin rudalics [this message]
2018-03-14 14:59 ` Aaron Jensen
2018-03-14 15:15 ` Aaron Jensen
2018-03-14 20:05 ` martin rudalics
2018-03-14 20:12 ` Aaron Jensen
2018-03-15 8:20 ` martin rudalics
2018-03-15 15:24 ` Aaron Jensen
2018-03-17 10:05 ` martin rudalics
2018-03-17 10:11 ` Noam Postavsky
2018-03-17 11:08 ` martin rudalics
2018-03-17 11:16 ` Eli Zaretskii
2018-03-17 11:28 ` martin rudalics
2018-03-17 16:32 ` Aaron Jensen
2018-01-17 9:12 ` bug#30141: 26.0.91; text-pixel dimensions not properly saved by desktop-save-mode sometimes martin rudalics
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=5AA8D9CB.4010509@gmx.at \
--to=rudalics@gmx.at \
--cc=30141@debbugs.gnu.org \
--cc=aaronjensen@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 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).