From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58520@debbugs.gnu.org, eggert@cs.ucla.edu, visuweshm@gmail.com
Subject: bug#58520: Persistent failure to DNS-lookup hostname
Date: Mon, 18 Dec 2023 12:41:00 -0500 [thread overview]
Message-ID: <jwvle9rtnpr.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83v88vifju.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 18 Dec 2023 19:30:45 +0200")
>> Cc: 58520@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>
>> Date: Sun, 17 Dec 2023 18:27:10 -0500
>> From: Stefan Monnier via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> > P.S. It would be nice to have that patch that you mentioned that added a
>> > function that fixes the broken requests.
>>
>> I use the patch below.
>> When Emacs gets into this weird state, I do `M-: (res-init) RET` after
>> which I can connect again.
>
> Why do you need Emacs for that? Write a small program that calls
> res_init, and that's it.
I don't understand what you mean. The problem is in the running Emacs
session, not in the overall system. I'd have to write a separate
program that goes and "pokes" inside my running Emacs process, which
sounds quite complicated.
IOW, `res_init` only affects the running program.
Stefan
next prev parent reply other threads:[~2023-12-18 17:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 16:20 bug#58520: Persistent failure to DNS-lookup hostname Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 16:55 ` Paul Eggert
2022-10-14 17:17 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-05 17:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-03 7:57 ` Visuwesh
2023-11-03 16:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-03 18:46 ` Visuwesh
2023-11-03 21:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-04 2:31 ` Visuwesh
2023-12-11 11:54 ` Visuwesh
2023-12-17 23:27 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-18 17:30 ` Eli Zaretskii
2023-12-18 17:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-12-18 17:55 ` Eli Zaretskii
2023-12-18 18:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=jwvle9rtnpr.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=58520@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=visuweshm@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 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).