Re: disk full - Gnus fetching mail
Bruno Hertz wrote on 14 Apr 2005 01:25:27 MET: Patrick Drechsler [EMAIL PROTECTED] writes: which files can I delete without running into too much trouble after running into one of those `end of file during parsing errors'? Using the agent, my candidates are: ~/News/agent/nnimap/.agent* ~/News/agent/nnimap/.overview* ~/.newsrc* Background: Gnus is always active (fetching Mails/NG every 10-30 min). If I fill the rest of the free space on my HD with data (the command `df' on unix will show 0) during that time Gnus will screw up one of the files above. Resulting in the End-of-file-during-parsing-error... somewhere ... Since my mails are on an IMAP-server I know that nothing is lost (except for marking). Are there further files to include in a potential clean-up-after-disk-is-full script (it has taken me quite some time to find ~/News.agent* with filesize *0k*. Deleting it solved my problem. Finding it took quite a lot of time)? First: don't delete .newsrc.eld (!) Since I have a daily backup I would only lose marks of a few hours. Second: I don't really understand what your purpose is - remove possibly corrupted files Sorry for not being clear: This is what I am after. If the former, I frankly don't know how to recognize corrupted files other than examine them one by one and see whether they look 'good'. Ok. I will have to find corrupted files manually then. [...further tipps on saving disk space...] Thanks for your feedback Bruno! Cheers Patrick -- Computers are good at following instructions, but not at reading your mind.-- Donald Knuth ___ Info-gnus-english mailing list Info-gnus-english@gnu.org http://lists.gnu.org/mailman/listinfo/info-gnus-english
Re: Killing unwanted post
On Thu, 14 Apr 2005, [EMAIL PROTECTED] wrote: I don't use CVS, but I tried adding the line (setq message-kill-buffer-query-if-modified nil) to message.el, then ran byte-compile-file on it. But it didn't seem to make any difference. I'm using Gnus v10.5.6. You need to get message.el (or all of Gnus) from CVS, or wait for the next release. It's a new feature so I don't think it should go into the maintenance trunk, where only bug fixes are supposed to go. Do you need help with that? Ted == Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News== http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups = East and West-Coast Server Farms - Total Privacy via Encryption = ___ Info-gnus-english mailing list Info-gnus-english@gnu.org http://lists.gnu.org/mailman/listinfo/info-gnus-english
Re: Killing unwanted post
Ted Zlatanov [EMAIL PROTECTED] writes: On Thu, 14 Apr 2005, [EMAIL PROTECTED] wrote: I don't use CVS, but I tried adding the line (setq message-kill-buffer-query-if-modified nil) to message.el, then ran byte-compile-file on it. But it didn't seem to make any difference. I'm using Gnus v10.5.6. You need to get message.el (or all of Gnus) from CVS, or wait for the next release. It's a new feature so I don't think it should go into the maintenance trunk, where only bug fixes are supposed to go. Do you need help with that? I'd probably need quite a bit of help. I might try for just the message.el bit, just to give me the idea. I've never used CVS in anger! If it's not too much trouble, perhaps you could give me a brief step-by-step guide. I'd be very grateful, but don't worry if you don't think it's practical. David -- David Sumbler Please reply with a followup to the newsgroup. However, if you _really_ want to send me an e-mail, replace nospam in my address with aeolia. ___ Info-gnus-english mailing list Info-gnus-english@gnu.org http://lists.gnu.org/mailman/listinfo/info-gnus-english
Re: new articles in a thread - how to auto-expand the thread?
* Peter Petersen [EMAIL PROTECTED] schrieb: How can I make Gnus automatically expand an otherwise collapsed thread (with let's say 4 articles) when another, new, fifth article arrives. The intention is clear: I would like to easily see (when entering the group buffers) where the new articles have gone, and especially whether there have been replies to my own posts in a long, but collapsed thread. With Forte Agent an existing thread has the colour blue when all its articles have been seen or marked read, and as most of us know, read and unread articles are always visible when entering a group. When this thread gets new articles (be it one or more) the colour turns from blue to red, even if the thread still remains collapsed. So how could one make Gnus behave in a comparable way? - either by having the thread collapsed, but see a different font or colour or - (as I asked above) have Gnus automatically expand the thread Doesn't anyone have an idea? What I also noticed is that in threads with ticked articles I _normally_ (= most often) can easily see a newly inserted article because the thread gets expanded, indeed! On the other hand, this doesn't happen in 100% of the cases for threads with ticked articles!? What appears to be strange is that the last line in a summary buffer (= the last thread) of article headers doesn't get expanded (when one or more new articles have been inserted)! Earlier threads, however, get expanded... As to the last thread, one more observation: If all threads before this last thread are ticked, the last thread will be expanded, too, once a new article for this thread has arrived. If, however, there is one single (or more) thread(s) in the entire summary buffer that is _unread_ (but not ticked!), then the last thread will not get expanded, if it has new articles! Can anyone follow my maybe slightly chaotical description? Here is an illustration: !ticked thread !another ticked thread !another ticked thread the last thread - with new articles arriving will get expanded versus: !ticked thread an unticked and unread thread !ticked thread the last thread - with new articles arriving will NOT be expanded Since I would really like to have a way to easily see whether the threads I try to watch have something new I now use 2 work-arounds: 1) I use the dormant mark ? because when I see the corresponding thread appear I know that a new article has arrived 2) I use /. in order to quickly see the articles marked unseen Is there no easier and more satisfying solution? Like a changed colour (see my remarks about Forte Agent) as soon as a (collapsed) thread has new articles. thanks again Peter ___ Info-gnus-english mailing list Info-gnus-english@gnu.org http://lists.gnu.org/mailman/listinfo/info-gnus-english
？？？
$B%a!<%k$7$^$7$?!):G6aM'?M0J30$+$i%a!<%k$,FO$/$s$G$9$,$"$J$?$b$G$9$+!)(B $B;d$O>>2
