all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ahmed Khanzada <me@enzu.ru>
To: Alan Third <alan@idiocy.org>, Ahmed Khanzada <me@enzu.ru>,
	emacs-devel@gnu.org
Subject: Re: [PATCH] Fix misnamed variable breaking GNUstep Emacs.app build
Date: Sat, 18 Apr 2020 12:19:11 -0700	[thread overview]
Message-ID: <864ktgy53k.wl-me@enzu.ru> (raw)
In-Reply-To: <20200418123031.GA54322@breton.holly.idiocy.org>

[-- Attachment #1: Type: text/plain, Size: 292 bytes --]

On Sat, 18 Apr 2020 05:30:31 -0700,
The result of the git format patch -1 is attached to this email.

Sorry for the inline patch, that is just how OpenBSD prefers it. Should
all patches be attachments going forward, or just the end stages before
ommit? Inline is sometimes easier to review.


[-- Attachment #2: 0001-Fix-misnamed-variable-breaking-GNUstep-Emacs.app.patch --]
[-- Type: text/plain, Size: 641 bytes --]

From 2fa8915eacf2b5f1315f5cac025f53af9a3a7efe Mon Sep 17 00:00:00 2001
From: Ahmed Khanzada <lenzuru@gmail.com>
Date: Sat, 18 Apr 2020 12:15:17 -0700
Subject: [PATCH] Fix misnamed variable breaking GNUstep Emacs.app

---
 src/nsterm.m | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/nsterm.m b/src/nsterm.m
index 9cd1c9d860..5eb44639f5 100644
--- a/src/nsterm.m
+++ b/src/nsterm.m
@@ -1875,7 +1875,7 @@ Hide the window (X11 semantics)
 
          FIXME: Surely there's a better way than just hardcoding 100
          in here?  */
-      boundsRect.origin.x = 100;
+      topLeft.x = 100;
 #endif
     }
 
-- 
2.22.0


[-- Attachment #3: Type: text/plain, Size: 1 bytes --]



  reply	other threads:[~2020-04-18 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17 23:14 [PATCH] Fix misnamed variable breaking GNUstep Emacs.app build Ahmed Khanzada
2020-04-18 12:30 ` Alan Third
2020-04-18 19:19   ` Ahmed Khanzada [this message]
2020-04-18 19:49     ` Alan Third

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=864ktgy53k.wl-me@enzu.ru \
    --to=me@enzu.ru \
    --cc=alan@idiocy.org \
    --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.