From: Ted Zlatanov <tzz@lifelogs.com>
To: Martin Stjernholm <mast@lysator.liu.se>
Cc: ding@gnus.org
Subject: Re: Patch: Support for non-ascii characters in imap group names
Date: Sun, 21 Mar 2010 13:49:37 -0500 [thread overview]
Message-ID: <87iq8p7bni.fsf@lifelogs.com> (raw)
In-Reply-To: <7m1vfdmwxk.fsf@kolon.stjernholm.org> (Martin Stjernholm's message of "Sun, 21 Mar 2010 18:00:55 +0100")
On Sun, 21 Mar 2010 18:00:55 +0100 Martin Stjernholm <mast@lysator.liu.se> wrote:
MS> Ted Zlatanov <tzz@lifelogs.com> wrote:
>> Thank you, it was my fault for ignoring it.
MS> I'm glad it got through. I trust then that my followup patch to improve
MS> the nnimap startup time has reached relevant people even though I have
MS> yet to see it in list archives.
I haven't seen it (which is probably my fault as I was not paying
attention), can you please resend and CC me?
>> I'm not sure why you need
>>
>> (nnimap-close-group): Call `imap-current-mailbox' instead of using the
>> variable `imap-current-mailbox'.
>>
>> but left it in, assuming it was sensible.
MS> The variable is utf-7 encoded while the function returns the decoded
MS> name, so using the variable would make the name would look garbled in
MS> that message. In general, I tried to use the functions in imap.el that
MS> deal with decoded names, to keep it clean. There are a few cases where
MS> the variable is still used, when only nil/non-nil matters.
Interesting. It sounds like we should get rid of the variable in code
completely and always use an accessor function with a "decoding"
parameter (so we can get the encoded or the unencoded name). I don't
like the current hidden behavior. Do you agree?
Thanks
Ted
next prev parent reply other threads:[~2010-03-21 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7mljev50dc.fsf@kolon.stjernholm.org>
[not found] ` <7m635qutf5.fsf@kolon.stjernholm.org>
2010-03-20 15:45 ` Ted Zlatanov
2010-03-21 17:00 ` Martin Stjernholm
2010-03-21 18:49 ` Ted Zlatanov [this message]
2010-03-21 20:26 ` Martin Stjernholm
2010-03-22 10:16 ` Ted Zlatanov
2010-03-22 7:49 ` Reiner Steib
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=87iq8p7bni.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=mast@lysator.liu.se \
/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).