From: Keith David Bershatsky <esq@lawlist.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 33021@debbugs.gnu.org
Subject: bug#33021: nsterm.m: missing two (2) closing parentheses ...
Date: Thu, 11 Jul 2019 11:00:44 -0700 [thread overview]
Message-ID: <m2ims8h2nn.wl%esq@lawlist.com> (raw)
In-Reply-To: <m2r2gwney9.wl%esq@lawlist.com>
It looks like Alan fixed it on 12/01/2018 with 4b176eb86361cff94a223225e8b852adb1accc50.
Both "if" statements to:
if ([child respondsToSelector:@selector(setAccessibilitySubrole:)]
were missing a closing parenthesis, and *accc50 fixed that problem.
As such, it would be appropriate to close out bug 33021 at your convenience.
Keith
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> Date: [07-11-2019 08:39:52] <11 Jul 2019 17:39:52 +0200>
> From: Lars Ingebrigtsen <larsi@gnus.org>
> To: Keith David Bershatsky <esq@lawlist.com>
> Cc: 33021@debbugs.gnu.org
> Subject: Re: bug#33021: nsterm.m: missing two (2) closing parentheses ...
>
> Keith David Bershatsky <esq@lawlist.com> writes:
>
> > At the convenience of the Emacs team, please add two (2) closing parentheses to nsterm.m. While it is possible to build Emacs, working on the functions is difficult because Emacs cannot narrow properly to a defun .... Thanks.
>
> Could you send a patch for this? I'm not quite sure what you're
> referring to here.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-07-11 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 1:14 bug#33021: nsterm.m: missing two (2) closing parentheses Keith David Bershatsky
2019-07-11 15:39 ` Lars Ingebrigtsen
2019-07-11 18:00 ` Keith David Bershatsky [this message]
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=m2ims8h2nn.wl%esq@lawlist.com \
--to=esq@lawlist.com \
--cc=33021@debbugs.gnu.org \
--cc=larsi@gnus.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.