From: npostavs@users.sourceforge.net
To: martin rudalics <rudalics@gmx.at>
Cc: 25511@debbugs.gnu.org, Katsumi Yamaoka <yamaoka@jpl.org>
Subject: bug#25511: 26.0.50; modify-frame-parameters modifies undesignated parameter?
Date: Mon, 05 Jun 2017 08:57:13 -0400 [thread overview]
Message-ID: <87zidmy4ly.fsf@users.sourceforge.net> (raw)
In-Reply-To: <58872061.1050900@gmx.at> (martin rudalics's message of "Tue, 24 Jan 2017 10:37:37 +0100")
martin rudalics <rudalics@gmx.at> writes:
>> Thanks for the suggestions about ‘after-make-frame-functions’,
>> ‘frame-inhibit-implied-resize’, and others. I didn't recall
>> I've been using ‘after-make-frame-functions’ for the other
>> purposes. ;-) I'll try them one by one from now on. Anyway, I
>> concluded I should not use dirty codes such as advising the core
>> functions, as much as possible.
>
> Advising is no problem per se. But ‘after-make-frame-functions’ is
> there so it's better to use it (and along the way find out if there are
> any problems with it). Obviously, my proposal to use the workarea won't
> work for Cygwin anyway, given you figures above.
Is there something more to do with this bug?
next prev parent reply other threads:[~2017-06-05 12:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 7:28 bug#25511: 26.0.50; modify-frame-parameters modifies undesignated parameter? Katsumi Yamaoka
2017-01-23 8:03 ` martin rudalics
2017-01-23 9:01 ` Katsumi Yamaoka
2017-01-23 10:28 ` martin rudalics
2017-01-23 22:54 ` Katsumi Yamaoka
2017-01-24 0:45 ` Katsumi Yamaoka
2017-01-24 7:46 ` martin rudalics
2017-01-24 9:18 ` Katsumi Yamaoka
2017-01-24 9:37 ` martin rudalics
2017-06-05 12:57 ` npostavs [this message]
2017-06-05 13:36 ` martin rudalics
2017-06-06 0:00 ` npostavs
2017-06-06 6:38 ` martin rudalics
2017-01-24 7:46 ` martin rudalics
2017-01-23 17:27 ` Noam Postavsky
2017-01-23 18:01 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zidmy4ly.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=25511@debbugs.gnu.org \
--cc=rudalics@gmx.at \
--cc=yamaoka@jpl.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 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.