unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
	"Mattias Engdegård" <mattias.engdegard@gmail.com>,
	71235-done@debbugs.gnu.org
Subject: bug#71235: Failing test on macOS: tramp-test17-dired-with-wildcards
Date: Sun, 02 Jun 2024 15:14:34 +0200	[thread overview]
Message-ID: <87ttibtrk5.fsf@gmx.de> (raw)
In-Reply-To: <CADwFkmkk_Ry2WignMm3vqkAdtaEdrdek_7Zb4HVtJZw4tirdjw@mail.gmail.com> (Stefan Kangas's message of "Sun, 2 Jun 2024 11:04:36 +0000")

Version: 30.1

Stefan Kangas <stefankangas@gmail.com> writes:

Hi Stefan,

>>>     (executable-find "gls")
>>>     => "/opt/homebrew/bin/gls"
>>
>> Hmm. Should we add "/opt/homebrew/bin" to the default
>> tramp-remote-path? It looks very special, even on macOS.
>>
>> OTOH, we have directories like "/local/freeware/bin", "/local/gnu/bin",
>> "/usr/freeware/bin", "/usr/pkg/bin", "/usr/contrib/bin", "/opt/bin",
>> "/opt/sbin" and "/opt/local/bin" there, which are also special.
>
> AFAIK, this is the default location where Homebrew (https://brew.sh/)
> puts binaries, at least on new installations.  (The Homebrew directory
> structure has changed slightly over the years, but I don't know if this
> is one of them since I only noticed it those changes passing.)

Finally, I have done both: Adding "/opt/homebrew/bin" to
tramp-remote-path, and applying the patch to dired-insert-directory I've
shown the other message.

Pushed to master, and closing the bug.

Best regards, Michael.





  parent reply	other threads:[~2024-06-02 13:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27 21:32 bug#71235: Failing test on macOS: tramp-test17-dired-with-wildcards Stefan Kangas
2024-05-28  7:44 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-28 22:56   ` Stefan Kangas
2024-05-29  7:28     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-29 20:51       ` Stefan Kangas
2024-05-30  8:54         ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-30 12:12     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-31  9:22       ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-02 10:37         ` Stefan Kangas
2024-06-02 10:19       ` Stefan Kangas
2024-06-02 10:33         ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-02 11:04           ` Stefan Kangas
2024-06-02 11:07             ` Stefan Kangas
2024-06-02 13:14             ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-06-02 17:51               ` Stefan Kangas
2024-06-02 14:03             ` Gerd Möllmann
2024-06-02 14:23               ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-02 14:46                 ` Gerd Möllmann
2024-06-02 14:55                   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87ttibtrk5.fsf@gmx.de \
    --to=bug-gnu-emacs@gnu.org \
    --cc=71235-done@debbugs.gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=mattias.engdegard@gmail.com \
    --cc=michael.albinus@gmx.de \
    --cc=stefankangas@gmail.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).