From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: van.ly@sdf.org, 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 20:46:10 +0300 [thread overview]
Message-ID: <86o74bbp99.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmqeJzUdvQLMX-hZ8thD1nd-UcaZijDuwnFYgNNUxMFwA@mail.gmail.com> (message from Stefan Kangas on Wed, 25 Sep 2024 10:24:32 -0700)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Wed, 25 Sep 2024 10:24:32 -0700
> Cc: 73455@debbugs.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.
I'm not sure. find-program is used in many places, most of them
unrelated to alignment in "find ... -ls", so we are basically skewing
everything for a single not very frequent case. Why not leave that to
users instead?
next prev parent reply other threads:[~2024-09-25 17:46 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
2024-09-25 17:46 ` Eli Zaretskii [this message]
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=86o74bbp99.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73455@debbugs.gnu.org \
--cc=stefankangas@gmail.com \
--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).