GNU bug report logs - #56432
run-dig vs dig -- do we need both?

Previous Next

Package: emacs;

Reported by: Stefan Kangas <stefan <at> marxist.se>

Date: Thu, 7 Jul 2022 08:38:01 UTC

Severity: wishlist

Fixed in version 29.1

Done: Stefan Kangas <stefan <at> marxist.se>

Bug is archived. No further changes may be made.

Full log


Message #34 received at 56432 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Robert Pluim <rpluim <at> gmail.com>, Lars Ingebrigtsen <larsi <at> gnus.org>,
 56432 <at> debbugs.gnu.org
Subject: Re: bug#56432: run-dig vs dig -- do we need both?
Date: Thu, 7 Jul 2022 15:41:24 +0200
Eli Zaretskii <eliz <at> 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).




This bug report was last modified 3 years and 4 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.