Thread management in kmail
Is it possible to either: - Move to the next unread thread - Mark the current thread as read - Ignore the current thread When I'm reading a high volume mailing list like this one, I'd like to skip threads that are of no interest to me, but I don't think I can do that in kmail. Can I? And if not, is there another mail client that would allow me to? Dougie -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Thread management in kmail
Hi, * Dougie Nisbet [EMAIL PROTECTED] [02-04-24 09:59]: - Move to the next unread thread - Mark the current thread as read is there another mail client that would allow me to? The answer is Mutt, as always. - Ignore the current thread What do you mean by 'ignore'? Thorsten -- Profanity is the inevitable linguistic crutch of the inarticulate motherfucker. - Bruce Sherrod -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Thread management in kmail
On Wed, Apr 24, 2002 at 10:16:59AM +0200, Thorsten Haude wrote: Hi, * Dougie Nisbet [EMAIL PROTECTED] [02-04-24 09:59]: - Move to the next unread thread - Mark the current thread as read is there another mail client that would allow me to? The answer is Mutt, as always. Mutt is a fine text mode client, but some people like a graphical client. Personally I tend towards Evolution, but if you don't want to install a substantial chunk of GNOME infrastructure on your computer then it's not a runner. Depends: gtkhtml (= 1.0.0), libcamel0 (= 1.0.3-2), bonobo (= 1.0.19), bonobo-conf (= 0.14), e2fsprogs (= 1.27-2), gdk-imlib1, libart2 (= 1.2.13-5), libaudiofile0 (= 0.2.3-4), libbonobo-conf0 (= 0.14), libbonobo2 (= 1.0.19), libc6 (= 2.2.4-4), libcamel0 (= 1.0.3), libcomerr2, libdb3 (= 3.2.9-15), libesd0 (= 0.2.23-1) | libesd-alsa0 (= 0.2.23-1), libfreetype6, libgal19 (= 0.19), libgconf11 (= 1.0.7), libgdk-pixbuf-gnome2 (= 0.16.0-1), libgdk-pixbuf2 (= 0.16.0-1), libglade-gnome0, libglade0, libglib1.2 (= 1.2.0), libgnome-pilot1 (= 0.1.63), libgnome-vfs0 (= 1.0.5), libgnome32 (= 1.2.13-5), libgnomeprint15 (= 0.29-1), libgnomesupport0 (= 1.2.13-5), libgnomeui32 (= 1.2.13-5), libgtk1.2 (= 1.2.10-4), libgtkhtml20 (= 1.0.2), libkrb53, libkrb53 (= 1.2.3-2), libldap2 (= 2.0.23-1), liboaf0 (= 0.6.7), liborbit0 (= 0.5.15), libpisock4, libpopt0 (= 1.6.2-1), libsasl7, libwrap0, libxml1 (= 1:1.8.14-3), oaf (= 0.6.7), xlibs ( 4.1.0), zlib1g (= 1:1.1.4) Doesn't bother me (I'm a GNOMEie) but a KDE user may balk at installing that lot. - Ignore the current thread What do you mean by 'ignore'? I think that he wants to be able to automatically hide or mark as read a thread and any new replies to it. Annoyingly enough, you can do this in Outlook Express (Message-Ignore Conversation). I can't see this functionality in Evolution. Shame. Regards Peter. -- Peter Whysall [EMAIL PROTECTED] The TLD in my email address is sdrawkcab. Debian GNU/Linux 3.0 sid -- kernel 2.4.18 pgpUOFHwJSd43.pgp Description: PGP signature
Re: Thread management in kmail
On Wednesday 24 April 2002 9:16 am, Thorsten Haude wrote: Hi, * Dougie Nisbet [EMAIL PROTECTED] [02-04-24 09:59]: - Move to the next unread thread - Mark the current thread as read is there another mail client that would allow me to? The answer is Mutt, as always. Perhaps. I dip into Mutt from time to time, and like its speed. I've just had another session. One problem I often found with Mutt is that it is in a console or xterm window, but after a bit of experimentation I find if I kick it off with 'xterm -fn 10x20 -e mutt' I can read the messages much better. I had a problem trying to look at my existing message base. I think this is because under kmail I use child folders a lot - e.g. I have a linux folder with sub-folders for laptop, and one for user. In mutt if I hit 'c' to change folders, it can't see the linux folder. Perhaps the way to go would be to flatten out my folder hierarchy, but having multiple depths is useful for organising stuff. I've been skimming the Mutt documentation and although I can see lots of references to folders, I can't see how to create them. Is that taken care of by something like procmail? I use filters a lot in kmail, but have often thought of getting procmail to do the filtering. I had a look at my inbox using mutt, and when I quit, and restarted kmail, my inbox was corrupt! - Ignore the current thread What do you mean by 'ignore'? Mark as read, including any further new messages in the thread. Dougie -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Thread management in kmail
On Wednesday 24 April 2002 9:55 am, [EMAIL PROTECTED] wrote: On Wed, Apr 24, 2002 at 10:16:59AM +0200, Thorsten Haude wrote: Hi, * Dougie Nisbet [EMAIL PROTECTED] [02-04-24 09:59]: - Move to the next unread thread - Mark the current thread as read is there another mail client that would allow me to? The answer is Mutt, as always. Mutt is a fine text mode client, but some people like a graphical client. Personally I tend towards Evolution, but if you don't want to install a substantial chunk of GNOME infrastructure on your computer then it's not a runner. I have evolution installed and have had a bit of play with it. I didn't pursue it too far because I couldn't import my existing mail base into it very easily. Quite liked evolution but it seemed a bit new and flakey. This is v1.0.3 under Woody. Dougie -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Thread management in kmail
Hi, * [EMAIL PROTECTED] [EMAIL PROTECTED] [02-04-24 10:55]: On Wed, Apr 24, 2002 at 10:16:59AM +0200, Thorsten Haude wrote: * Dougie Nisbet [EMAIL PROTECTED] [02-04-24 09:59]: - Move to the next unread thread - Mark the current thread as read is there another mail client that would allow me to? The answer is Mutt, as always. Mutt is a fine text mode client, but some people like a graphical client. He asked for functionality, so I had hopes he would want it. - Ignore the current thread What do you mean by 'ignore'? I think that he wants to be able to automatically hide or mark as read a thread and any new replies to it. Mutt alone can't do this, but could work with a filter. Thorsten -- As far as the USA is concerned, it has both an absolute right for its citizens to live in peace and safety, and also an absolute right to protect its valid strategic interests. Unfortunately, the second of these rights prevents any other country from enjoying the first. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Thread management in kmail
Hi, * Dougie Nisbet [EMAIL PROTECTED] [02-04-24 12:35]: On Wednesday 24 April 2002 9:16 am, Thorsten Haude wrote: * Dougie Nisbet [EMAIL PROTECTED] [02-04-24 09:59]: - Move to the next unread thread - Mark the current thread as read is there another mail client that would allow me to? The answer is Mutt, as always. Perhaps. I dip into Mutt from time to time, and like its speed. I've just had another session. One problem I often found with Mutt is that it is in a console or xterm window, but after a bit of experimentation I find if I kick it off with 'xterm -fn 10x20 -e mutt' I can read the messages much better. Yes, run it with whatever font you like best. Maybe you want to get a terminal which knows themes, which allows you to keep a set of terminal settings only for Mutt. I had a problem trying to look at my existing message base. I think this is because under kmail I use child folders a lot - e.g. I have a linux folder with sub-folders for laptop, and one for user. In mutt if I hit 'c' to change folders, it can't see the linux folder. You have to use Mutt's 'mailboxes' command to tell Mutt what your folders are. You may use a process for this: mailboxes `find ~/Mail -type f -print | grep -Ev '(admin|postponed)' | xargs` /var/mail/hde The find/grep/xargs combo lists all files in the ~/Mail hierarchy except for those whose name contains (admin|postponed). You would have to look for file names that are not mailboxes (or you don't want to check, like I do with 'postponed'), like KMail's index files and include them here. After that, my system spool file is just appended. Perhaps the way to go would be to flatten out my folder hierarchy, but having multiple depths is useful for organising stuff. Of course! I have far too much mail boxes to keep them flat. I've been skimming the Mutt documentation and although I can see lots of references to folders, I can't see how to create them. You generally don't need to create them. Just let your MDA (or KMail) create them for you and Mutt will be able to read them. If you set $confirmcreate in your mutt.rc, Mutt will ask you before it creates a new mailbox, but the default is 'yes', so Mutt will create merrily along if need arises. (I use 'ask-yes'.) I use filters a lot in kmail, but have often thought of getting procmail to do the filtering. I don't recommend Procmail, the syntax is really ugly. Use Maildrop. You can see right here why an external MDA like Maildrop is a huge advantage: You don't even have to *touch* your filters when you change from Mutt to KMail or from KMail tp Sylpheed or from Evolution to Netscape. If both MUAs know the same mail box format, you can run them in parallel. I had a look at my inbox using mutt, and when I quit, and restarted kmail, my inbox was corrupt! Seen from where? If Mutt would corrupt mboxes, you should definitely contact the developers, I'm sure this would get top priority. The only problem I'm aware of is that pre-3.0 KMails don't see if their mboxes are changed externally. (I don't use KMail, I only heard about this.) - Ignore the current thread What do you mean by 'ignore'? Mark as read, including any further new messages in the thread. Can't be done out of the box, but you can feed the Msg-IKD to a process which adds it to a file which is read by your MDA. Thorsten -- The history of Liberty is a history of the limitation of government power. - Woodrow Wilson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Thread management in kmail
On Wed Apr 24, 2002 at 02:59:11PM +0200, Thorsten Haude wrote: * Dougie Nisbet [EMAIL PROTECTED] [02-04-24 12:35]: On Wednesday 24 April 2002 9:16 am, Thorsten Haude wrote: * Dougie Nisbet [EMAIL PROTECTED] [02-04-24 09:59]: The answer is Mutt, as always. another session. One problem I often found with Mutt is that it is in a console or xterm window, but after a bit of experimentation I find if I kick it off with 'xterm -fn 10x20 -e mutt' I can read the messages much better. here' my recipe: rxvt -g 100x60+50+50 -bg black -fg green -T 'mail' -e mutt I had a problem trying to look at my existing message base. I think this is because under kmail I use child folders a lot - e.g. I have a linux folder with sub-folders for laptop, and one for user. In mutt if I hit 'c' to change folders, it can't see the linux folder. mutt shouldn't have any trouble traversing directory structures. I can hit 'c' and travel from ~/Mail to /var/spool/mail if I want You have to use Mutt's 'mailboxes' command to tell Mutt what your folders are. You may use a process for this: -(some good stuff snipped in the interest of brevity) I've been skimming the Mutt documentation and although I can see lots of references to folders, I can't see how to create them. I make folders with mkdir and let mutt create mailboxes. Mutt has many capablilities in folder management, discussed in another thread this week, but I haven't bothered. I had a look at my inbox using mutt, and when I quit, and restarted kmail, my inbox was corrupt! Seen from where? If Mutt would corrupt mboxes, you should definitely contact the developers, I'm sure this would get top priority. The only problem I'm aware of is that pre-3.0 KMails don't see if their mboxes are changed externally. (I don't use KMail, I only heard about this.) I suspect it is a kmail problem. I have always set up mutt kmail to share mailboxes, and use kmail occasionally when I feel like a graphical client. The only problem I ever had in a couple years of this with the KDE-1 kmail is read messages that weren't marked read. However, a couple days ago I built KDE3 from source, with kmail 1.2, and seems to be doing what you describe. If I go into the Mail directory and delete every file whose name begins with a dot, then restart kmail, all is well again. Since mutt is by far my preferred MUA and kmail only gets used very occasionally, this is a solution that doesn't bother me. The mailbox index corruption does not seem to affect mutt in any way. -- -CraigW You stole fizzy lifting drinks! You bumped into the ceiling which now has to be washed and sterilized, so you get nothing! You lose! Good day sir! -Willy Wonka -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
