From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Alan Third <alan@idiocy.org>
Cc: 69525@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#69525: 30.0.50; MacOS: New warnings on stderr
Date: Sat, 27 Jul 2024 05:56:30 +0200 [thread overview]
Message-ID: <m2le1n4he9.fsf@pro2.fritz.box> (raw)
In-Reply-To: <ZqP62ROhNUEu9OaG@idiocy.org> (Alan Third's message of "Fri, 26 Jul 2024 20:36:57 +0100")
Alan Third <alan@idiocy.org> writes:
>> I find Apple's documentation of the protocol pretty bad, to say the
>> least, and examples seem to be lacking completely. Don't know if I can
>> pull that off.
>
> Yeah, I was trying to work out what the actual differences are between
> them and I suspect they're fairly minimal, but I don't know how we
> should handle insertText:replacementRange: vs the current insertText:,
> for example.
>
> The new one takes a range and the old one doesn't. IMO it's none of
> the window system's business where we insert the text, so do we just
> ignore it? That might cause issues if we're dealing with the language
> input stuff, so we might need to fiddle with that a bit (it was mostly
> contributed by someone who actually used it).
>
> I would agree that Apple's documentation is abysmal. AFAICT most new
> features are exclusively documented in WWDC talks, so if you're not
> immersed in the Apple eco-system it can be very hard to keep track of
> what's changed. I assume that's some sort of marketing ploy.
Yeah, could be. Although I wonder what advantage they expect from making
such stuff effectively a secret :-/.
BTW, I found a github repo with lots of Cocoa samples which might be of
help at some point. This one is about NSTextInputClient, it seems:
https://github.com/HelmutJ/CocoaSampleCode/tree/master/TextInputView
I've read it, but without any further background I find it hard to
understand. Maybe it's helpful for you, though. It does do something
with these ranges, for example.
next prev parent reply other threads:[~2024-07-27 3:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 16:18 bug#69525: 30.0.50; MacOS: New warnings on stderr Gerd Möllmann
2024-03-03 16:26 ` Eli Zaretskii
2024-03-03 17:33 ` Gerd Möllmann
2024-03-03 17:36 ` Gerd Möllmann
2024-03-03 18:06 ` Alan Third
2024-03-03 19:29 ` Gerd Möllmann
2024-03-04 9:12 ` Gerd Möllmann
2024-03-04 13:48 ` Gerd Möllmann
2024-03-04 14:43 ` Gerd Möllmann
2024-03-04 21:40 ` Alan Third
2024-03-05 4:38 ` Gerd Möllmann
2024-03-05 12:59 ` Alan Third
2024-03-05 14:31 ` Gerd Möllmann
2024-03-05 5:31 ` Gerd Möllmann
2024-07-26 10:33 ` Gerd Möllmann
2024-07-26 10:55 ` Eli Zaretskii
2024-07-26 11:02 ` Gerd Möllmann
2024-07-26 19:09 ` Alan Third
2024-07-26 19:24 ` Gerd Möllmann
2024-07-26 19:36 ` Alan Third
2024-07-27 3:56 ` Gerd Möllmann [this message]
2024-07-27 6:37 ` Eli Zaretskii
2024-07-30 6:00 ` Gerd Möllmann
2024-07-31 3:22 ` Gerd Möllmann
2024-07-31 13:51 ` Eli Zaretskii
2024-07-26 9:56 ` Gerd Möllmann
2024-07-26 18:38 ` Alan Third
2024-07-26 19:02 ` Gerd Möllmann
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=m2le1n4he9.fsf@pro2.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=69525@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=eliz@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 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).