* imap-debug buffer exceeds maximum size
@ 2008-01-08 16:17 Ted Zlatanov
2008-01-15 20:46 ` Ted Zlatanov
0 siblings, 1 reply; 4+ messages in thread
From: Ted Zlatanov @ 2008-01-08 16:17 UTC (permalink / raw)
To: Ding Mailing List
If you turn imap-debug on, the imap-debug buffer keeps growing and
eventually will get to the max buffer size. If then you try to do any
IMAP operations they will fail; currently you have to kill the
imap-debug buffer or empty it to continue IMAP usage.
I don't know what's the right fix, but I would guess removing half the
imap-debug buffer's contents (with a suitable message) would be a nice
compromise to keep the debug data.
Ted
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: imap-debug buffer exceeds maximum size
2008-01-08 16:17 imap-debug buffer exceeds maximum size Ted Zlatanov
@ 2008-01-15 20:46 ` Ted Zlatanov
2008-01-15 22:59 ` Reiner Steib
0 siblings, 1 reply; 4+ messages in thread
From: Ted Zlatanov @ 2008-01-15 20:46 UTC (permalink / raw)
To: Ding Mailing List
On Tue, 08 Jan 2008 10:17:38 -0600 Ted Zlatanov <tzz@lifelogs.com> wrote:
TZ> If you turn imap-debug on, the imap-debug buffer keeps growing and
TZ> eventually will get to the max buffer size. If then you try to do any
TZ> IMAP operations they will fail; currently you have to kill the
TZ> imap-debug buffer or empty it to continue IMAP usage.
TZ> I don't know what's the right fix, but I would guess removing half the
TZ> imap-debug buffer's contents (with a suitable message) would be a nice
TZ> compromise to keep the debug data.
Anyone with an opinion? nnimap-debug-buffer has the same problem.
Ted
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: imap-debug buffer exceeds maximum size
2008-01-15 20:46 ` Ted Zlatanov
@ 2008-01-15 22:59 ` Reiner Steib
2008-01-16 18:42 ` Ted Zlatanov
0 siblings, 1 reply; 4+ messages in thread
From: Reiner Steib @ 2008-01-15 22:59 UTC (permalink / raw)
To: ding
On Tue, Jan 15 2008, Ted Zlatanov wrote:
> On Tue, 08 Jan 2008 10:17:38 -0600 Ted Zlatanov <tzz@lifelogs.com> wrote:
>
> TZ> If you turn imap-debug on, the imap-debug buffer keeps growing and
> TZ> eventually will get to the max buffer size. If then you try to do any
> TZ> IMAP operations they will fail; currently you have to kill the
> TZ> imap-debug buffer or empty it to continue IMAP usage.
>
> TZ> I don't know what's the right fix, but I would guess removing half the
> TZ> imap-debug buffer's contents (with a suitable message) would be a nice
> TZ> compromise to keep the debug data.
It would be okay, I'd guess. But the debug output is created via the
Emacs functionality `trace.el'. I'm not familiar with this, but
I don't see a possibility to limit the output buffer.
(when imap-debug ; (untrace-all)
(require 'trace)
(buffer-disable-undo (get-buffer-create imap-debug-buffer))
(mapc (lambda (f) (trace-function-background f imap-debug-buffer))
'(
imap-utf7-encode
;; [...]
imap-parse-body
)))
> nnimap-debug-buffer has the same problem.
Maybe `imap-log-buffer', too.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: imap-debug buffer exceeds maximum size
2008-01-15 22:59 ` Reiner Steib
@ 2008-01-16 18:42 ` Ted Zlatanov
0 siblings, 0 replies; 4+ messages in thread
From: Ted Zlatanov @ 2008-01-16 18:42 UTC (permalink / raw)
To: ding; +Cc: emacs-devel
On Tue, 15 Jan 2008 23:59:15 +0100 Reiner Steib <reinersteib+gmane@imap.cc> wrote:
RS> On Tue, Jan 15 2008, Ted Zlatanov wrote:
>> On Tue, 08 Jan 2008 10:17:38 -0600 Ted Zlatanov <tzz@lifelogs.com> wrote:
>>
TZ> If you turn imap-debug on, the imap-debug buffer keeps growing and
TZ> eventually will get to the max buffer size. If then you try to do any
TZ> IMAP operations they will fail; currently you have to kill the
TZ> imap-debug buffer or empty it to continue IMAP usage.
>>
TZ> I don't know what's the right fix, but I would guess removing half the
TZ> imap-debug buffer's contents (with a suitable message) would be a nice
TZ> compromise to keep the debug data.
RS> It would be okay, I'd guess. But the debug output is created via the
RS> Emacs functionality `trace.el'. I'm not familiar with this, but
RS> I don't see a possibility to limit the output buffer.
RS> (when imap-debug ; (untrace-all)
RS> (require 'trace)
RS> (buffer-disable-undo (get-buffer-create imap-debug-buffer))
RS> (mapc (lambda (f) (trace-function-background f imap-debug-buffer))
RS> '(
RS> imap-utf7-encode
RS> ;; [...]
RS> imap-parse-body
RS> )))
>> nnimap-debug-buffer has the same problem.
RS> Maybe `imap-log-buffer', too.
I think this is for the Emacs developers list, since trace.el is in
their tree.
My suggestions for the fix are above; I can write a patch if it's
necessary. Looks like trace.el:trace-make-advice() needs to be adjusted
to check the buffer size. It could set trace-inhibit but I think
trimming the buffer is a nicer solution for the user.
Ted
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-01-16 18:42 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-01-08 16:17 imap-debug buffer exceeds maximum size Ted Zlatanov
2008-01-15 20:46 ` Ted Zlatanov
2008-01-15 22:59 ` Reiner Steib
2008-01-16 18:42 ` Ted Zlatanov
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).