Re: Oort "/ N" doesn't mark articles scored lower than mark

Re: Oort "/ N" doesn't mark articles scored lower than mark

[Lars Magne Ingebrigtsen]

Nimar Arora <nimar_arora@yahoo.com> writes:

> When I refresh the summary buffer using E-g the right thing happens
> but when I type / N the mails sent by me don't get marked.

`/ N' is designed to be fast.  I you want thorough, use `M-g'
instead. 

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Oort "/ N" doesn't mark articles scored lower than mark

[Lars Magne Ingebrigtsen]

Nimar Arora <nospam_nimar_arora@yahoo.com> writes:

> But I did notice that '/ N' does compute the score correctly of the new
> mails. So, if it goes that far why not mark them as read as well? One
> would think that scoring which might involve multiple regexp string
> comparisons might be far more expensive than a simple numeric comparison
> against the mark value?

Yes, I should probably remove the scoring from the `/ N' command
altogether, I guess...

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: oort compute bound since 12/6 nntp.el changes

[Lars Magne Ingebrigtsen]

Anne & Lynn Wheeler <lynn@garlic.com> writes:

> i switch back and forth between 0.08 and 0.13 and the elapsed time for
> doing things take the same amount of time ....

So it isn't CPU bound, really.

> but for 0.08 the cpu meter shows very little activity and 0.13 pegs
> the meter.

Sure.

I've now added the variable `nntp-read-timeout' to the current CVS to
let you tweak this behavior.  It defaults to 0.1; you might want to
set it to 1 if you have a slow line.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: oort compute bound since 12/6 nntp.el changes

[Anne & Lynn Wheeler]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Sure.
>
> I've now added the variable `nntp-read-timeout' to the current CVS to
> let you tweak this behavior.  It defaults to 0.1; you might want to
> set it to 1 if you have a slow line.

just tried 0.09 & 0.10 ... and they are ok also ... but 0.13 seems to
be spinning someplace.

-- 
Anne & Lynn Wheeler | http://www.garlic.com/~lynn/ 
Internet trivia 20th anv http://www.garlic.com/~lynn/rfcietff.htm

Re: oort compute bound since 12/6 nntp.el changes

[Anne & Lynn Wheeler]

Anne & Lynn Wheeler <lynn@garlic.com> writes:
> also ... if i load nntp.el from 0.08 before starting 0.13 ... it
> doesn't have the problem. i was hoping that it was something that was
> going to get fixed w/o having to delve into it further.

ok using ognus-0.14 ... if i have the nntp-read-timeout value at
default 0.1 or set to 0.9 ... it uses 100 percent of the cpu during
startup of the newsgroups from the nttp server.

if i set the value to 1.0, it uses less than 2 percent of the cpu and
startup takes the same elapsed time.

possibly 21.2 emacs or 21.2 emacs on nt/2k issue?

i'll try and report on linux (redhat 7.3) later (same server, same
newsgroups, same dial-up link).

-- 
Anne & Lynn Wheeler | http://www.garlic.com/~lynn/ 
Internet trivia 20th anv http://www.garlic.com/~lynn/rfcietff.htm