From: Alvaro Ramirez <alvaro@xenodium.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Po Lu <luangruo@yahoo.com>,
copyright-clerk@fsf.org, 72827@debbugs.gnu.org
Subject: bug#72827: [PATCH] Adds NSSpeechRecognitionUsageDescription to Info.plist.in
Date: Thu, 29 Aug 2024 08:07:53 +0100 [thread overview]
Message-ID: <m2frqn9586.fsf@xenodium.com> (raw)
In-Reply-To: <8634mnhqb2.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 29 Aug 2024 08:05:21 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: copyright-clerk@fsf.org, 72827@debbugs.gnu.org
>> Date: Thu, 29 Aug 2024 08:57:25 +0800
>> From: Po Lu via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> Alvaro Ramirez <alvaro@xenodium.com> writes:
>>
>> > Here's a tiny patch to add
>> > NSSpeechRecognitionUsageDescription to
>> > Info.plist.in.
>> >
>> > Without NSSpeechRecognitionUsageDescription, we cannot launch
>> > processes that use macOS's speech recognition APIs (including
>> > built-in
>> > shells).
>> >
>> > Here's an eshell example:
>> >
>> > $ macosrec --speech-to-text --input /tmp/audio.mp3
>> > abort trap: 6
>> >
>> > With NSSpeechRecognitionUsageDescription in place, macOS
>> > displays a
>> > dialog asking users to grant permission and allows the speech
>> > APIs to
>> > be used from the process.
>> >
>> > Added change to Emacs 31 NEWS. If there's any chance the
>> > permission
>> > can make it to 30, I'd be happy to rework the patch as
>> > needed.
>> >
>> > Cheers,
>>
>> What speech recognition services exist on Free (GNU/Linux)
>> systems, and
>> do they require like intervention on our part to function in
>> Emacs?
>
> Can you explain why this question is relevant to the patch?
>
> AFAIU, the patch does not invoke any services nor adds any
> features to
> Emacs, it just avoids interfering with existing system features.
> IOW,
> it makes Emacs behave according to the platform requirements and
> conventions.
Correct. No feature added. Purely host OS permission
integration. If macOS determines the user must be asked for this
permission to run a process, the patch enables the permission
request to surface to the user. Without the patch, the process
just fails (terminated by the OS).
next prev parent reply other threads:[~2024-08-29 7:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 9:12 bug#72827: [PATCH] Adds NSSpeechRecognitionUsageDescription to Info.plist.in Alvaro Ramirez
2024-08-29 0:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-29 5:05 ` Eli Zaretskii
2024-08-29 7:07 ` Alvaro Ramirez [this message]
2024-08-30 8:10 ` Stefan Kangas
2024-08-30 9:18 ` Alvaro Ramirez
2024-08-30 16:08 ` Stefan Kangas
2024-08-30 17:45 ` Alvaro Ramirez
2024-08-31 10:39 ` Eli Zaretskii
2024-08-31 11:05 ` Alvaro Ramirez
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=m2frqn9586.fsf@xenodium.com \
--to=alvaro@xenodium.com \
--cc=72827@debbugs.gnu.org \
--cc=copyright-clerk@fsf.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
/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).