From: Ilya Kulakov <kulakov.ilya@gmail.com>
To: git@vger.kernel.org
Subject: git-gui: Visualize * History does nothing on macOS
Date: Thu, 9 May 2024 11:17:19 -0700 [thread overview]
Message-ID: <38A18180-3CC9-411B-B5D3-36C5C32B6EE9@gmail.com> (raw)
Both "Visualize <branch>'s History" and "Visualize All Branch History" do nothing on macOS. In the terminal it logs:
Error in startup script: 58:103: execution error: Not authorized to send Apple events to System Events. (-1743)
while executing
"exec osascript -e [format {
tell application "System Events"
set frontmost of processes whose unix id is %d to true
end te..."
invoked from within
"if {[tk windowingsystem] eq "aqua"} {
exec osascript -e [format {
tell application "System Events"
set frontmost of processes ..."
(file "/opt/homebrew/bin/gitk" line 12321)
The relevant code at https://github.com/git/git/blob/0f3415f1f8478b05e64db11eb8aaa2915e48fef6/git-gui/git-gui.sh#L271-L279 should not be fatal, because the permission to access "System Events" and arbitrarily manipulate windows is optional.
Best Regards,
Ilya Kulakov
next reply other threads:[~2024-05-09 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 18:17 Ilya Kulakov [this message]
2024-05-09 19:05 ` git-gui: Visualize * History does nothing on macOS Eric Sunshine
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=38A18180-3CC9-411B-B5D3-36C5C32B6EE9@gmail.com \
--to=kulakov.ilya@gmail.com \
--cc=git@vger.kernel.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.
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).