From: Eli Zaretskii <eliz@gnu.org>
To: Alex Gramiak <agrambot@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Remove display member of glyph_string
Date: Thu, 09 May 2019 20:02:26 +0300 [thread overview]
Message-ID: <834l63h87x.fsf@gnu.org> (raw)
In-Reply-To: <871s17ehmq.fsf@gmail.com> (message from Alex Gramiak on Thu, 09 May 2019 10:07:25 -0600)
> From: Alex Gramiak <agrambot@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Thu, 09 May 2019 10:07:25 -0600
>
> >> The only other location that FRAME_X_DISPLAY appears in non-X code is in
> >> the argument to Free_Pixmap in image.c, which can hopefully be
> >> refactored out in a later patch; at that point the other terms can
> >> remove their trivial FRAME_X_DISPLAY definitions.
> >
> > So should we do both in one go, perhaps?
>
> Sure, here's a patch that does it:
Thanks.
> * src/msdos.h:
> * src/nsgui.h:
> * src/nsterm.h:
> * src/w32term.h: Remove unused X-compatibility macros and typedefs.
Please mention the macros and typedefs being removed explicitly, it is
important for later forensics.
> src/image.c | 24 ++----------------------
> src/msdos.h | 1 -
> src/nsgui.h | 1 -
> src/nsterm.h | 6 ------
> src/nsterm.m | 16 ++++++++++++++--
> src/termhooks.h | 8 ++++++++
> src/w32term.c | 14 ++++++++++++++
> src/w32term.h | 3 ---
> src/xterm.c | 12 ++++++++++++
> 9 files changed, 50 insertions(+), 35 deletions(-)
There's one more instance of FRAME_X_DISPLAY in xdisp.c which was
left, and it will fail compilation on non-X platforms.
Otherwise, this LGTM, thanks.
next prev parent reply other threads:[~2019-05-09 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 3:52 [PATCH] Remove display member of glyph_string Alex Gramiak
2019-05-09 5:50 ` Eli Zaretskii
2019-05-09 16:07 ` Alex Gramiak
2019-05-09 17:02 ` Eli Zaretskii [this message]
2019-05-09 17:16 ` Alex Gramiak
2019-05-09 17:59 ` Eli Zaretskii
2019-05-09 18:21 ` Alex Gramiak
2019-05-10 5:30 ` Eli Zaretskii
2019-05-11 4:20 ` Alex Gramiak
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=834l63h87x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=agrambot@gmail.com \
--cc=emacs-devel@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 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.