Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Cc: ding@gnus.org
Subject: Re: Bug in nnmaildir?
Date: Tue, 29 Jun 2004 16:09:34 -0400	[thread overview]
Message-ID: <m3r7ry6s8b.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <87n02m16up.fsf@seamus.arnested.dk> (Arne =?iso-8859-1?Q?J=F8rgensen's?= message of "Tue, 29 Jun 2004 21:50:38 +0200")

Arne Jørgensen <arne@arnested.dk> wrote:
> prj@po.cwru.edu (Paul Jarc) writes:
>> Ouch.  Does anyone know if there's a way to get at the localization
>> bits from Elisp?  So I could look for
>> (locale-translation "no such file or directory") or some such?
>
> Isn't the text coming from some library and not from emacs code?

Maybe.  But I think it's possible for Emacs to expose the translation
function anyway - which is not to say that it actually does.

> How about checking the existence of the file or directory before
> accessing it instead of the depending on the error message afterwards?

That's what it did before; I changed it to make it faster.

Does anyone know any other way of getting the errno information?


paul



  reply	other threads:[~2004-06-29 20:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-29  6:52 Another newbie question Ding Lei
2004-06-03  0:16 ` Chris Ball
2004-06-04  1:01 ` Ding Lei
2004-06-26 20:12 ` Bug in nnmaildir? (was: Another newbie question...) Arne Jørgensen
2004-06-26 20:37   ` Bug in nnmaildir? Arne Jørgensen
2004-06-28 17:19     ` Paul Jarc
2004-06-29 19:50       ` Arne Jørgensen
2004-06-29 20:09         ` Paul Jarc [this message]
2004-06-29 20:49           ` Arne Jørgensen
2004-06-29 21:16             ` Paul Jarc
2004-06-29 21:51               ` Arne Jørgensen
2004-06-29 22:14               ` Arne Jørgensen
2004-06-30 15:45                 ` Paul Jarc
2004-06-28  8:20   ` Florian Dufour

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=m3r7ry6s8b.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    --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).