From: Steinar Bang <sb@dod.no>
To: gmane-discuss@hawk.netfonds.no
Cc: ding@gnus.org
Subject: Re: "No DNS server configuration found" when approving spam reports
Date: Sun, 28 Dec 2008 15:03:54 +0100 [thread overview]
Message-ID: <ueizs9z1x.fsf@dod.no> (raw)
In-Reply-To: <uiqp4a6mr.fsf@dod.no>
>>>>> Steinar Bang <sb@dod.no>:
>> The place the dns-query function fails, is in the call to
>> dns-make-network-process, and in dns-make-network-process the place
>> it fails is here
>> `(let ((server ,server)
>> when I press SPC when the cursor is placed after the closing
>> parantheses on the above line.
> Some more details:
> - Before pressing space, the cursor is positioned over the quote `
> - After pressing space the cursor is positioned over the )
> - The minibuffer displays the text "Result: (car dns-servers)"
> - After the next space the cursor is positioned on top of the
> second-to-last closing parantheses in this line
> (open-network-stream "dns" (current-buffer) server "domain")))))
> and the minibuffer displays:
> Result: (let ((server (car dns-servers)) (coding-system-for-read (quote binary)) (coding-system-for-write (quote binary))) (if (fboundp (quote make-network-process)) (make-network-process :name "dns" :coding (quote binary) :buffer (current-buffer) :host server :service "domain" :type (quote datagram)) (open-network-stream "dns" (current-buffer) server "domain")))
When I run just (dns-make-network-process "10.0.0.138") in the *scratch*
buffer, I get the following stack trace:
Debugger entered--Lisp error: (error "Unsupported connection type")
make-network-process(:name "dns" :coding binary :buffer #<buffer *scratch*> :host "10.0.0.138" :service "domain" :type datagram)
(if (fboundp (quote make-network-process)) (make-network-process :name "dns" :coding (quote binary) :buffer (current-buffer) :host server :service "domain" :type (quote datagram)) (open-network-stream "dns" (current-buffer) server "domain"))
(let ((server "10.0.0.138") (coding-system-for-read ...) (coding-system-for-write ...)) (if (fboundp ...) (make-network-process :name "dns" :coding ... :buffer ... :host server :service "domain" :type ...) (open-network-stream "dns" ... server "domain")))
(dns-make-network-process "10.0.0.138")
eval((dns-make-network-process "10.0.0.138"))
eval-last-sexp-1(t)
eval-last-sexp(t)
eval-print-last-sexp()
call-interactively(eval-print-last-sexp)
recursive-edit()
byte-code("ऀ䀀윀=Ħ
No :type datagram in emacs on Windows...?
next prev parent reply other threads:[~2008-12-28 14:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 20:31 Steinar Bang
2008-12-25 13:07 ` Reiner Steib
2008-12-25 14:40 ` Steinar Bang
2008-12-25 17:52 ` Reiner Steib
2008-12-26 9:18 ` Steinar Bang
2008-12-26 10:45 ` Steinar Bang
2008-12-26 11:10 ` Steinar Bang
2008-12-26 17:38 ` Reiner Steib
2008-12-27 13:30 ` Steinar Bang
2008-12-27 13:55 ` Steinar Bang
2008-12-28 11:20 ` Steinar Bang
2008-12-28 14:03 ` Steinar Bang [this message]
2009-01-18 14:29 ` Lars Magne Ingebrigtsen
2009-01-18 18:48 ` Steinar Bang
2009-02-08 22:37 ` Lars Magne Ingebrigtsen
2009-02-09 22:44 ` Steinar Bang
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=ueizs9z1x.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.org \
--cc=gmane-discuss@hawk.netfonds.no \
/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.
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 NNTP newsgroup(s).