Displaying tar.gz archives
Hey, I would like to add a mailcap entry so that I view the contents of tar.gz archives as a list of filenames, but I'm, not sure how to do it. When I attach one, it is added with the application/octet-streem MIME type. Any thoughts on how to approach this? Thaks, -- Noah Slater, http://tumbolia.org/nslater
Re: Displaying tar.gz archives
On Wed, Jul 22, 2009 at 08:00:47AM +0100, Noah Slater wrote: I would like to add a mailcap entry so that I view the contents of tar.gz archives as a list of filenames, but I'm, not sure how to do it. When I attach one, it is added with the application/octet-streem MIME type. Any thoughts on how to approach this? Look at mime_lookup in the documentation. -- Nicolas Sebrecht
Re: sigdashes
Hi, * Tim Gray wrote: True. I just wanted to make sure that was in fact how mutt was supposed to behaving. Though I would hope that most format=flowed rewrapping engines first strip off the quote characters, and then recognize a -- as a sigdash and leave it alone. That's at least I did with my script for f=f. Mutt does look for -- after logically deleting the quote prefix. I.e. in '-- ' it would recognize it, but not in ' -- '. Stripping the space may be due to compatibility routines. Rocco pgpSGojLsBUAB.pgp Description: PGP signature
Re: program to generate mailboxes lines
* Christian Ebert on Tuesday, July 21, 2009 at 17:55:36 +0100 * lee on Monday, July 20, 2009 at 22:28:25 -0600 On Mon, Jul 20, 2009 at 10:11:15PM -0600, lee wrote: Here's the program. Let me know how you like it :) Nice. Hn, one small adjustment: The recursion level is irrelevant, but I forgot to remove the counter. snip // it's a maildir printf(mailboxes = %s\n, this); Wouldn't it be easier to just print out a list of mailboxes? a) how do you use it in muttrc (without awk, maybe, or most certainly I'm being dense)? mailboxes = `mutt-mb ~/Mail` mailboxes `mutt-mb ~/Mail` grr, mailboxes is a command, not a variable. c -- ich bin eine Null eine Null is eine runde Sache -- http://www.blacktrash.org/hanullmann/
Re: SSL encrypts for recipients only
Hi, * Bertram Scharpf wrote: As I need the same thing with PGP encryption, I just wrote another patch: http://www.bertram-scharpf.de/tmp/encrypt_self.patch So I think somebody should open a ticket (if there isn't one yet) and add both patches as an enhancement along with the patch keyword. If people really want this, we should add a $crypt_encrypt_self quad-option that triggers for PGP/MIME and S/MIME with classic _and_ gpgme backends. Rocco pgpHK9vQQj6jJ.pgp Description: PGP signature
Re: Displaying tar.gz archives
Hi, * Noah Slater wrote: I would like to add a mailcap entry so that I view the contents of tar.gz archives as a list of filenames, but I'm, not sure how to do it. When I attach one, it is added with the application/octet-streem MIME type. Just search the net for mutt.octet.filter. It's a shell script that has useful commands for displaying many MIME types, including listing the contents of a number of archive files. Rocco pgppI5WO9mNSP.pgp Description: PGP signature
Re: split display?
On Tue, 2009-07-14 at 00:31 -0600, lee wrote: Hi, is it possible to somehow create a display that is split up in some way, or is there a way to assign mails to categories and fold these categories? What I want to see as overview of my inbox is something like a number of categories and the number of new messages in each category. I would like to have the mails automatically sorted into categories by criteria like spam score X or sender, and I would like to be able to create new categories and assign messages to them without having to edit my ~/.muttrc. This is different from moving the messages into different folders. Different folders aren't displayed in the message list, and I don't move messages into another folder unless that folder is their final storage. It can take quite a while before I decide what that final storage is going to be, and the list of messages in my inbox gets longer every day. Having foldable categories in the message list would make dealing with the mail much easier. I think you get the idea ... If that isn't possible, it's a feature request. Hm, hasn't that been requested yet? Or is there another MUA which can do this and work on maildir? It may be heresy to say this on a Mutt list, but have you tried Evolution? Evolution has the ability to tag (not in the Mutt sense, but in a categorising sense - with an associated colour) a mail as Important (red), work (orange), personal (green), To Do (blue) or Later (purple) and the inbox can then be limited by these categories. Not quite as flexible as you want but it's a start. Moreover, Evolution has the concept of virtual folders which I'm afraid I don't use so I can't tell you much about them - but it may be worth a look. Of course Evolution is a (very) heavyweight GUI application and if you are used to the agility and flexibility of Mutt it may not be what you want.. Just my £0.02p Regards Mark
Re: [mutt] generating mailboxes command
* Adam Wellings on Tuesday, July 21, 2009 at 20:28:39 +0100 On Tue, 21 Jul 2009, Christian Ebert wrote: Well, your nodes clobber the mailboxes list, don't they. Not that I can see. Do toggle-mailboxes (bound to tab by default) in the browser. This lists your configured mailboxes, and the nodes shouldn't be in there, imho. Anyway, I went back to my previous one with the addition of -prune. It's ~0.5s instead of the ~0.3s that that one came up with. I can live Oh, right, good idea (I don't understand this -prune stuff really, to be honest). This works also for find w/o -printf: find ~/Mail -type d -name cur -prune -execdir pwd \; Another idea: find ~/Mail -type d \( -name cur -o -name new -o -name tmp \) -prune -execdir pwd \; | uniq c -- Was heißt hier Dogma, ich bin Underdogma! [ What the hell do you mean dogma, I am underdogma. ] _F R E E_ _V I D E O S_ http://www.blacktrash.org/underdogma/ http://www.blacktrash.org/underdogma/index-en.html
Re: SSL encrypts for recipients only
Hi, Am Mittwoch, 22. Jul 2009, 11:19:01 +0200 schrieb Rocco Rutte: * Bertram Scharpf wrote: As I need the same thing with PGP encryption, I just wrote another patch: http://www.bertram-scharpf.de/tmp/encrypt_self.patch So I think somebody should open a ticket (if there isn't one yet) and add both patches as an enhancement along with the patch keyword. If people really want this, we should add a $crypt_encrypt_self quad-option that triggers for PGP/MIME and S/MIME with classic _and_ gpgme backends. I'm glad that you like it. I just changed the quad-option name to $crypt_encrypt_self in my patch. Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de
Re: [mutt] generating mailboxes command
On Wed, 22 Jul 2009, Christian Ebert wrote: * Adam Wellings on Tuesday, July 21, 2009 at 20:28:39 +0100 On Tue, 21 Jul 2009, Christian Ebert wrote: Well, your nodes clobber the mailboxes list, don't they. Not that I can see. Do toggle-mailboxes (bound to tab by default) in the browser. This lists your configured mailboxes, and the nodes shouldn't be in there, imho. If I get a few minutes I'll put that back and have a look-see. I may even run it for a day and see if there's any noticeable behavioural problems. Anyway, I went back to my previous one with the addition of -prune. It's ~0.5s instead of the ~0.3s that that one came up with. I can live Oh, right, good idea (I don't understand this -prune stuff really, to be honest). -prune stops the find from descending into the directory. So, without it, if it finds a directory 'cur', it will go into it and look for more subdirectories called 'cur'. As we can (reasonably) assume that there are none, by putting -prune it doesn't do that. prune is a little convoluted (prune the tree at this point, is what I assume it means) as an option name, but I can't think of a better one. This works also for find w/o -printf: find ~/Mail -type d -name cur -prune -execdir pwd \; Another idea: find ~/Mail -type d \( -name cur -o -name new -o -name tmp \) -prune -execdir pwd \; | uniq Ah that's worth a try. I did wonder if checking for one of all three sub-dirs would be quicker. Anyway that's back down to ~0.3s. Nice one. It occurred to me last night, that I could use a combination of the fixed index, and dynamic set. My folder set is generally static except for list folderss - which get automatically created by Procmail and long-term working folders (some jobs take six months, and I don't want the emails from them lying around the inbox) which can be created by one of a number of processes. However as the list maildirs are below a lists folder and the working ones below a working folder, I could use a stable index of the rest, and just search below those two folders, where the depth will also just be one. The index file could also be added to by procmail and the other processes, maybe -though it will create a larger maintenance effort. As this is probably more effort to set-up than the saving will be (at least at the moment), I'll probably set it up when I switch to my new desktop machine. cheers, Adam -- ...one cannot be angry when one looks at a penguin. - John Ruskin
Re: program to generate mailboxes lines
On Tue, Jul 21, 2009 at 05:55:36PM +0100, Christian Ebert wrote: * lee on Monday, July 20, 2009 at 22:28:25 -0600 On Mon, Jul 20, 2009 at 10:11:15PM -0600, lee wrote: Here's the program. Let me know how you like it :) Nice. I put a better version on http://sourceforge.net/projects/mutt-mb/ :) snip // it's a maildir printf(mailboxes = %s\n, this); Wouldn't it be easier to just print out a list of mailboxes? Not if you want to create a file to source or to put the lines into your ~/.muttrc. a) how do you use it in muttrc (without awk, maybe, or most certainly I'm being dense)? Not at all --- I quickly found that I didn't want to use a file but use it directly. I changed it to support different output formats: mailboxes, just a list and a single line. mailboxes = `mutt-mb ~/Mail` would be the easiest, imho. You can do that with the new version: unmailboxes * mailboxes = `mutt-mb -line ~/Mail` b) Mutt might be a tiny bit faster as you only issue 1 command. Possible --- but it depends on what's in the disk cache and/or on how fast your disks are, i. e. it might be a lot faster to read one file and use many mailboxes commands than it is to run only one command that has to scan through your mail storage. Since the new version supports both ways, everyone can use what they like better or is faster. One thing not supported is using relative paths. It can be done, but I don't know how important that is.
Re: program to generate mailboxes lines
On Wed, Jul 22, 2009 at 10:18:14AM +0100, Christian Ebert wrote: mailboxes = `mutt-mb ~/Mail` mailboxes `mutt-mb ~/Mail` grr, mailboxes is a command, not a variable. Both work --- does it make a difference?
Re: program to generate mailboxes lines
Hi, * lee wrote: On Wed, Jul 22, 2009 at 10:18:14AM +0100, Christian Ebert wrote: mailboxes = `mutt-mb ~/Mail` mailboxes `mutt-mb ~/Mail` grr, mailboxes is a command, not a variable. Both work --- does it make a difference? Yes and no. Given 'mutt-mb ~/Mail' prints '~/Mail/foobar' and given that $folder is ~/Mail, you get: mailboxes ~/Mail ~/Mail/foobar with the former and: mailboxes ~/Mail/foobar with the latter. See mailbox shortcuts in the manual. Rocco pgpHl763KK3DZ.pgp Description: PGP signature
Re: program to generate mailboxes lines
On Wed, Jul 22, 2009 at 03:53:20PM +0200, Rocco Rutte wrote: Hi, * lee wrote: On Wed, Jul 22, 2009 at 10:18:14AM +0100, Christian Ebert wrote: mailboxes = `mutt-mb ~/Mail` mailboxes `mutt-mb ~/Mail` grr, mailboxes is a command, not a variable. Both work --- does it make a difference? Yes and no. Given 'mutt-mb ~/Mail' prints '~/Mail/foobar' and given that $folder is ~/Mail, you get: mailboxes ~/Mail ~/Mail/foobar with the former and: mailboxes ~/Mail/foobar with the latter. See mailbox shortcuts in the manual. Ah, I see what you mean. With the first, I'm getting an entry for =/ in the list, with the second version, I don't. So the second one is the one I want. I'll change that in the documentation of mutt-mb.
Re: generating mailboxes command (was: split display?)
On Tue, Jul 21, 2009 at 12:03:03PM +0100, Christian Ebert wrote: Sure, but (my find doesn't have printf): ~$ time find ~/Mail -type d -name cur -execdir pwd \; /dev/null real0m54.973s user0m0.447s sys 0m54.159s ~$ time find ~/Mail -type -d \( \( -name cur -o -name new -o -name tmp \) -prune -o -print \) /dev/null find: -type: -d: unknown type Hm, I think it's find -type d rather than find -type -d.
Re: [mutt] generating mailboxes command (was: split display?)
On Tue, Jul 21, 2009 at 02:52:57PM +0100, Adam Wellings wrote: If the set of maildirs rarely changes, would it be faster to generate a file and just source that in your .muttrc? It depends on what information from the file system is already cached. Assuming that nothing is cached, I would think that a file is faster. I can't do that as I use procmail to sometimes create new maildirs in some situations. Also, I've looked up why my script is no longer used, it took ~8-9s to produce the list. I'm sure it could be improved upon generally, but as find does the job, it'd purely be an academic exercise. Then mutt-mb is for you, it's pretty fast :)
Re: [mutt] generating mailboxes command
On Tue, Jul 21, 2009 at 05:49:13PM +0100, Christian Ebert wrote: lee's little C program mutt-mb that he posted in this thread Message-ID: 20090721042825.gj27...@cat.rubenette.is-a-geek.com It's better to use the version on sourceforge instead. The one posted here doesn't free all the memory it allocates, and there are other improvements in the new version: http://sourceforge.net/projects/mutt-mb/ does the job quite well and reasonably fast. l...@cat:~$ time mutt-mb -line ~/Mail/ /dev/null real0m0.064s user0m0.000s sys 0m0.070s l...@cat:~$ time mutt-mb -check ~/Mail/ check mode enabled, not creating list real0m0.065s user0m0.000s sys 0m0.070s l...@cat:~$ That's on over 700 directories and 20 files. The disk cache helps, I guess. (Using /dev/null is not entirely fair, though; it helps making it fast.) Hm, /usr/bin/find is 230k, mutt-mb is only about 15k.
Re: Automatic thread collapsing
On Tue, Jul 21, 2009 at 04:02:42PM -0500, Kyle Wheeler wrote: On Tuesday, July 21 at 03:03 AM, quoth Noah Slater: Is there any way to get mutt to continually and automatically collapse threads as you move around in the pager? So, if I select a collapsed thread, it should be un-collapsed, but as I move out of it, it is re-collapsed. I think it's probably possible, through creative re-binding of standard navigation keys, but there's no *easy* way to do it. Ah, that's a shame. Obviously, these things are subjective, but as someone who only uses one mailbox, this feature is largely useless to me without automatic thread re-folding. Would the developers be open to a feature request? Thanks, -- Noah Slater, http://tumbolia.org/nslater
Re: split display?
On Wed, Jul 22, 2009 at 10:29:50AM +0100, Arthur Dent wrote: On Tue, 2009-07-14 at 00:31 -0600, lee wrote: Or is there another MUA which can do this and work on maildir? It may be heresy to say this on a Mutt list, but have you tried Evolution? Yes --- it's polluting my mail storage by putting index files (or whatever it is) everywhere. Besides that I don't like that, it probably also means that information is stored which only Evolution can use so that I would be without this information when using another MUA. Evolution has the ability to tag (not in the Mutt sense, but in a categorising sense - with an associated colour) That's probably the kind of information stored in the extra files. Of course Evolution is a (very) heavyweight GUI application and if you are used to the agility and flexibility of Mutt it may not be what you want.. Indeed --- being heavyweight wouldn't matter much, but having to deal with all the different windows or with displaying many things at once and not having enough room for that and the keyboard only half-way supported are some things that make me not like GUI MUAs. The only one I found ok was the built-in one mozilla had, but it was somewhat limited in functionality. And what when I want to read my mails on the console, like when X isn't working or when I feel like doing that? The last one I tried was wanderlust, running in emacs. It's nice but can be awfully slow and doesn't really have advantages over mutt, so I went back to mutt. Gnus didn't want to work, and it seems to be too much a newsreader to make for a good MUA.
Re: Displaying tar.gz archives
=- Rocco Rutte wrote on Wed 22.Jul'09 at 11:26:09 +0200 -= * Noah Slater wrote: I would like to add a mailcap entry so that I view the contents of tar.gz archives as a list of filenames, but I'm, not sure how to do it. When I attach one, it is added with the application/octet-streem MIME type. Just search the net for mutt.octet.filter. It's a shell script that has useful commands for displaying many MIME types, including listing the contents of a number of archive files. There is also mime_lookup application/octet-stream, and then the respective mailcap entry like gzip -dc | tar -tvf - -- © Rado S. -- You must provide YOUR effort for your goal! EVERY effort counts: at least to show your attitude. You're responsible for ALL you do: you get what you give.
Re: Displaying tar.gz archives
On Wed, Jul 22, 2009 at 06:29:57PM +0200, Rado S wrote: There is also mime_lookup application/octet-stream, and then the respective mailcap entry like gzip -dc | tar -tvf - Well, I had considered this, but application/octet-stream is a catch-all MIME type, and I can't blithely assume that it will always be this very specific type of file. So going down this path like the wrong approach. Thanks, -- Noah Slater, http://tumbolia.org/nslater
Re: setting mailboxes from the output of a command
On Tue, Jul 21, 2009 at 04:04:23PM -0500, Kyle Wheeler wrote: mailboxes = `mutt-mb /home/lee/Mail` Just to make sure you notice: mailboxes is a *command*, not a value, so mutt is interpreting that = as a mailbox name to expand (namely, $folder). Thanks, I found it another post here. Before that, I didn't realize that it's a command rather than a variable.
how to prevent external commands from being substituted in macro definitions
Hi, how do I prevent external commands from being processed when mutt is parsing a macro definition in ~/.muttrc? What I'm trying to do is: macro index .a unmailboxes * ; mailboxes `mutt-mb -line ~/Mail`enter macro index .l unmailboxes * ; mailboxes `mutt-mb -line ~/Mail/Lists`enter This gets substituted correctly, but it is not what I want. It creates interesting entries in the help screen and funny effects when the macro is run ... The external command must not be executed before I actually run the macro, i. e. it must be as if I type it on the : commandline inside mutt (When I do that, it works as intended.).
Re: navigation
On Sun, 19 Jul 2009, Tim Tebbit wrote: Robert Holtzman wrote: Running mutt and mutt-patched 1.5.17 with the side panel listing mailboxes on Ubuntu Hardy. I can't find a way to navigate in this list other than by using c and ?. Is the side panel functional or just informative? I run mutt and mutt-patched 1.5.18 in Debian Lenny and it exhibits the same behavior. Possibly # Sidebar keys bind index \CP sidebar-prev bind index \CN sidebar-next bind index \CO sidebar-open bind pager \CP sidebar-prev bind pager \CN sidebar-next bind pager \CO sidebar-open Just got the time to try this. Works great. I can navigate the sidebar but the only way I can navigate the pager is with the arrow keys and that's fine with me. I'll have some more questions shortly. Thanks. -- Bob Holtzman AF9D 8760 0CFA F95A 6C77 E125 BF90 580F 8D54 9279 If you think you're getting free lunch, check the price of the beer
Re: SSL encrypts for recipients only
On Wed, Jul 22, 2009 at 11:19:01AM +0200, Rocco Rutte wrote: * Bertram Scharpf wrote: As I need the same thing with PGP encryption, I just wrote another patch: http://www.bertram-scharpf.de/tmp/encrypt_self.patch So I think somebody should open a ticket (if there isn't one yet) and add both patches as an enhancement along with the patch keyword. If people really want this, we should add a $crypt_encrypt_self quad-option that triggers for PGP/MIME and S/MIME with classic _and_ gpgme backends. I think this things should be handled by programs which are made for this: Simply put encrypt-to YourKeyID into $HOME/.gnupg/gpg.conf sigi
Re: Displaying tar.gz archives
On Wed, Jul 22, 2009 at 11:26:09AM +0200, Rocco Rutte wrote: Just search the net for mutt.octet.filter. It's a shell script that has useful commands for displaying many MIME types, including listing the contents of a number of archive files. Thanks, this works a treat. -- Noah Slater, http://tumbolia.org/nslater
Re: SSL encrypts for recipients only
Hi, Am Mittwoch, 22. Jul 2009, 20:54:30 +0200 schrieb sigi: On Wed, Jul 22, 2009 at 11:19:01AM +0200, Rocco Rutte wrote: * Bertram Scharpf wrote: http://www.bertram-scharpf.de/tmp/encrypt_self.patch So I think somebody should open a ticket (if there isn't one yet) and add both patches as an enhancement along with the patch keyword. I think this things should be handled by programs which are made for this: Simply put encrypt-to YourKeyID into $HOME/.gnupg/gpg.conf First, my original post was about S/MIME, not PGP. Besides that, I really need both. As far as I know, OpenSSL doesn't have such an option. Second, it's just the mails I want to encrypt for myself, not neccessarily something else. I edit the mails in a temporary file that is deleted by Mutt after the mail has been sent. Just for this reason I need to decrypt it later. Third, I use diffent mail adresses private and in business and I want to encrypt for what is mentioned in the From header field. The GnuPG config file cannot make this decision. You're right: this thing should be handled by the program that is made for this, and that's the mail client. I'm a Mutt user now for about eight years and I know what I do when I write a patch. Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de
Re: navigation
On Wed, Jul 22, 2009 at 10:46:12AM -0700, Robert Holtzman wrote: On Mon, 20 Jul 2009, lee wrote: Did you get sidebar-scroll-up and sidebar-scroll-down to work? I can bind them to keys, but mutt says the key isn't bound when I press it. The sidebar scroll works great but the pager scroll doesn't. Not sure why. I can still use the arrow keys for the pager. Hm, I was able to scroll up and down one line after another, but when you bind sidebar-scroll-up and sidebar-scroll-down to keys, you're supposed to be able to scroll the sidebar up or down by a page. That didn't work for me.
Re: Displaying tar.gz archives
On Wed, Jul 22, 2009 at 05:35:02PM +0100, Noah Slater wrote: On Wed, Jul 22, 2009 at 06:29:57PM +0200, Rado S wrote: There is also mime_lookup application/octet-stream, and then the respective mailcap entry like gzip -dc | tar -tvf - Well, I had considered this, but application/octet-stream is a catch-all MIME type, and I can't blithely assume that it will always be this very specific type of file. So going down this path like the wrong approach. Did you actually look up what mime_lookup means? If you would have done, you wouldn't have to worry. mime_lookup and mailcap do exactly the same as the octet filter script. I just find the script more convenient as I don't have to write tons of mailcap entries. Rocco
Re: Displaying tar.gz archives
On Thu, Jul 23, 2009 at 12:11:08AM +0200, Rocco Rutte wrote: Did you actually look up what mime_lookup means? If you would have done, you wouldn't have to worry. mime_lookup and mailcap do exactly the same as the octet filter script. Nope! My bad! I just find the script more convenient as I don't have to write tons of mailcap entries. Yeah, I think I prefer the mime_lookup method actually. Thanks for prodding me, -- Noah Slater, http://tumbolia.org/nslater
urlview problems
Hello, Today after building and installing the latest tip, I find that urlview doesn't work anymore. I hit CTRL-] and I get a list of urls, but when I go to one that I know is valid and hit return, nothing happens. Upon quitting mutt, I see right before my shell prompt: sh: line 1: url_handler.sh: command not found I didn't change anything urlview-related, and as far as I remember everything worked fine until today. All I did was upgrade mutt. Normally, urlview tells Safari to open the url (in .urlview I have COMMAND open %s, which on OSX will open the link in whatever the default browser is). I rebuilt urlview from source, and moved url_handler.sh from the build directory into /usr/local/bin to see if that would help, but all that did was make urlview open the urls in lynx, which is not what it should be doing. What's going on here? -gmn
Re: urlview problems
Today after building and installing the latest tip, I find that urlview doesn't work anymore. I hit CTRL-] and I get a list of urls, but when I go to one that I know is valid and hit return, nothing happens. Upon quitting mutt, I see right before my shell prompt: sh: line 1: url_handler.sh: command not found I didn't change anything urlview-related, and as far as I remember everything worked fine until today. All I did was upgrade mutt. Normally, urlview tells Safari to open the url (in .urlview I have COMMAND open %s, which on OSX will open the link in whatever the default browser is). I rebuilt urlview from source, and moved url_handler.sh from the build directory into /usr/local/bin to see if that would help, but all that did was make urlview open the urls in lynx, which is not what it should be doing. What's going on here? -gmn Never mind, please disregard. Found the problem, and shockingly it was my fault. -gmn
