unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Van Ly <van.ly@sdf.org>
Cc: 73455@debbugs.gnu.org
Subject: bug#73455: 30.0.91: find buffer pretty print columns don't line up on 1080p
Date: Wed, 25 Sep 2024 10:24:32 -0700	[thread overview]
Message-ID: <CADwFkmmqeJzUdvQLMX-hZ8thD1nd-UcaZijDuwnFYgNNUxMFwA@mail.gmail.com> (raw)
In-Reply-To: <86plorbtf6.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> If you set the value of find-program to "gfind", I think you should be
> able to add only /usr/pkg/bin to PATH, and that should not override
> the original "find", "make", etc.

Would it be worth considering doing the same as we did for
`insert-directory-program`, i.e. the below?  I'm not sure if this would
be considered too opinionated for people that are very used to a BSD
userland.

This still requires GNU find to be installed, of course (on macOS with
Homebrew, that would be `brew install findutils`).

diff --git a/lisp/progmodes/grep.el b/lisp/progmodes/grep.el
index b453ac60ed2..97583c8afb8 100644
--- a/lisp/progmodes/grep.el
+++ b/lisp/progmodes/grep.el
@@ -550,7 +550,11 @@ grep-program
 This variable's value takes effect when `grep-compute-defaults' is called.")

 ;;;###autoload
-(defvar find-program (purecopy "find")
+(defvar find-program
+  (if (and (memq system-type '(berkeley-unix darwin))
+           (executable-find "gfind"))
+      (purecopy "gfind")
+    (purecopy "find"))
   "The default find program.
 This is used by commands like `grep-find-command', `find-dired'
 and others.")





  reply	other threads:[~2024-09-25 17:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-24 15:27 bug#73455: 30.0.91: find buffer pretty print columns don't line up on 1080p Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-24 18:02 ` Eli Zaretskii
2024-09-25  9:39   ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-25 12:26     ` Eli Zaretskii
2024-09-25 15:36       ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-25 16:16         ` Eli Zaretskii
2024-09-25 17:24           ` Stefan Kangas [this message]
2024-09-25 17:46             ` Eli Zaretskii
2024-09-26 13:20               ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-26 14:11                 ` Eli Zaretskii

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=CADwFkmmqeJzUdvQLMX-hZ8thD1nd-UcaZijDuwnFYgNNUxMFwA@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=73455@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=van.ly@sdf.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).