From: Derrell.Lipman@UnwiredUniverse.com
Subject: Re: [nnimap] Is `A T' supposed to work with nnimap backend
Date: Thu, 20 Nov 2003 09:23:42 -0500 [thread overview]
Message-ID: <islfrudt.fsf@random.localnet.unwireduniverse.com> (raw)
In-Reply-To: <4nhe0zjgm3.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Thu, 20 Nov 2003 08:48:20 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> Because the protocol dump, when enabled, generates lots of data, it is
> disabled by default. You can enable it by toggling `imap-log' as
> follows:
>
> (setq imap-log t)
Nit-picky change. This isn't acually "toggling". How about:
You can enable it by setting the `imap-log' variable as follows:
Derrell
next prev parent reply other threads:[~2003-11-20 14:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 16:56 Harry Putnam
2003-11-20 3:31 ` Simon Josefsson
2003-11-20 4:17 ` Harry Putnam
2003-11-20 4:40 ` Simon Josefsson
2003-11-20 10:54 ` Harry Putnam
2003-11-20 11:57 ` Simon Josefsson
2003-11-20 12:21 ` Harry Putnam
2003-11-20 12:30 ` Simon Josefsson
2003-11-20 13:48 ` Ted Zlatanov
2003-11-20 14:23 ` Derrell.Lipman [this message]
2003-11-20 14:24 ` Simon Josefsson
2003-11-20 16:19 ` Ted Zlatanov
2003-11-20 4:20 ` Harry Putnam
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=islfrudt.fsf@random.localnet.unwireduniverse.com \
--to=derrell.lipman@unwireduniverse.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.
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).