From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: New feature: De-IDNA
Date: Sun, 16 Jan 2005 19:58:29 +0100 [thread overview]
Message-ID: <ilusm51p5ey.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3zmz9dygq.fsf@pigpen.waxrat.com> (Michael Cook's message of "Sun, 16 Jan 2005 13:24:05 -0500")
Michael Cook <michael@waxrat.com> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> Michael Cook <michael@waxrat.com> writes:
>>
>>> Simon Josefsson <jas@extundo.com> writes:
>>>
>>>> Xavier Maillard <zedek@gnu-rox.org> writes:
>>>>
>>>>> On 15 jan 2005, Simon Josefsson wrote:
>>>>>
>>>>>> Hi. I added a new binding `W i' in summary buffers, that decode
>>>>>> IDNA names inside articles. It works if you have GNU Libidn
>>>>>> installed ("idn" command line tool.)
>>>>>
>>>>> Is it normal that my gnus is trying to fire up "idna" ?
>>>>
>>>> You mean "idn"? If so, yes.
>>>
>>> i get an error message:
>>>
>>> gnus-summary-idna-message: Cannot open load file: idna
>>
>> Ouch, yes. Better now?
>
> a little, i suppose. now i get:
>
> GNU Libidn not installed properly (`idn' or `idna.el' missing)
>
> maybe the help text for `gnus-summary-idna-message' should something
> about what libidn is and how to install it (e.g., maybe a URL)?
I've added an URL to the docstring, manual and GNUS-NEWS now, thanks.
next prev parent reply other threads:[~2005-01-16 18:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 19:55 Simon Josefsson
2005-01-16 10:47 ` Xavier Maillard
2005-01-16 12:24 ` Simon Josefsson
2005-01-16 16:35 ` Michael Cook
2005-01-16 17:37 ` Simon Josefsson
2005-01-16 18:24 ` Michael Cook
2005-01-16 18:58 ` Simon Josefsson [this message]
2005-01-17 0:11 ` Katsumi Yamaoka
2005-01-17 0:43 ` Simon Josefsson
2006-04-15 8:36 ` Lars Magne Ingebrigtsen
2006-04-18 10:44 ` Simon Josefsson
2006-04-18 15:29 ` Lars Magne Ingebrigtsen
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=ilusm51p5ey.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.org \
/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).