From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Robert Pluim <rpluim@gmail.com>,
Lars Ingebrigtsen <larsi@gnus.org>,
56432@debbugs.gnu.org
Subject: bug#56432: run-dig vs dig -- do we need both?
Date: Thu, 7 Jul 2022 15:41:24 +0200 [thread overview]
Message-ID: <CADwFkmn7onJzsxiP4OsudysMRW6Ez+o9js3cavMRKmiNM-YcRA@mail.gmail.com> (raw)
In-Reply-To: <837d4p5h5r.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> > net-utils-machine-at-point does not seem very useful to me (it seems
> > to pick up any word whether or not it looks like a domain name?)
>
> Is it really any worse than not showing any possibly useful default at
> all?
I found it much worse, but this was mostly due to using the obsolete
INITIAL-CONTENTS argument (which meant you had to delete that less
than useful input to type something useful). So I've now changed
`dig' to use a standard default instead (commit 7b84f9a5d8).
> > but perhaps we could use thing-at-point instead?
>
> If thing-at-point can guess machines better, sure, why not? But if it
> isn't better, why not use net-utils-machine-at-point?
It seems like the ffap versions are strictly better, so I've replaced
the net-utils-* versions with ffap-* (commit a651c309fd).
prev parent reply other threads:[~2022-07-07 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 8:37 bug#56432: run-dig vs dig -- do we need both? Stefan Kangas
2022-07-07 8:56 ` Lars Ingebrigtsen
2022-07-07 9:24 ` Robert Pluim
2022-07-07 9:27 ` Lars Ingebrigtsen
2022-07-07 10:37 ` Eli Zaretskii
2022-07-07 14:33 ` Robert Pluim
2022-07-07 9:36 ` Stefan Kangas
2022-07-07 10:37 ` Eli Zaretskii
2022-07-07 10:47 ` Stefan Kangas
2022-07-07 10:52 ` Eli Zaretskii
2022-07-07 13:41 ` Stefan Kangas [this message]
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=CADwFkmn7onJzsxiP4OsudysMRW6Ez+o9js3cavMRKmiNM-YcRA@mail.gmail.com \
--to=stefan@marxist.se \
--cc=56432@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=rpluim@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.