From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: rpluim@gmail.com, larsi@gnus.org, 56432@debbugs.gnu.org
Subject: bug#56432: run-dig vs dig -- do we need both?
Date: Thu, 07 Jul 2022 13:52:16 +0300 [thread overview]
Message-ID: <837d4p5h5r.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmk6GqR84+=KuhB7fCVEHuCNwCHrZOOH_Rgb_u29=cYmQQ@mail.gmail.com> (message from Stefan Kangas on Thu, 7 Jul 2022 12:47:42 +0200)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Thu, 7 Jul 2022 12:47:42 +0200
> Cc: Robert Pluim <rpluim@gmail.com>, Lars Ingebrigtsen <larsi@gnus.org>, 56432@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > run-dig seems to be able to guess the host using
> > net-utils-machine-at-point, something 'dig' doesn't. So if we want to
> > tell people top use the latter, IMO we should teach 'dig' that trick.
>
> 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?
> 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?
next prev parent reply other threads:[~2022-07-07 10:52 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 [this message]
2022-07-07 13:41 ` Stefan Kangas
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=837d4p5h5r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56432@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rpluim@gmail.com \
--cc=stefan@marxist.se \
/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).