I don't understand why Opera Mail and googlemail would make a simple task (pipe or save message text) as hard as it sounds like the do. As well as my previous three benefits, it also sounds like it would remove one step of ReviewRecipe and the RecipeLint change seems worth doing anyway.
"Jonas Karlsson" <[EMAIL PROTECTED]> > First of all, I couldn't create a recipe from the code you gave me. =20 > Perhaps I did it the wrong way, so if you want to convince me, send me a = > mail with a MailRecipe attachment and a clear description what to do. I don't use Opera Mail, nor googlemail, so it's hard for me to send a clear description of how to do this simple task in those. > Secondly, as I use a graphical mail client it was hard to copy-paste the = > commands to the console. I'd much rather have a file that I save to disk.= Can you save the message body to disk? Then you have a file saved to disk and can feed it to cpio instead of tar: is there much difference? Copy-pasting is quite easy from the graphical mail client I used most recently: triple-click the line with the unpack command, paste it into the terminal, then select-all the mail and paste it into the terminal. > Yes, one of the first things RecipeLint does is to unpack the recipe. Otoh > it does it automagically, so the user isn't aware of this unless he/she > reads the code of RecipeLint. Indeed. Would it be useful to be able to lint recipes before using or packing them? "Lucas C. Villa Real" <[EMAIL PROTECTED]> > If I understood it correctly, I'd need to save the email (or > copy-and-paste it to a file, since I'm using gmail's web interface > here) and process it with a script (such as 'UnpackMailRecipe') in > order to get the recipe available exactly in the same way it's > currently packed, right? Yes. The unpack command is given in the mail. Hopefully, it would work even on a Save Page As... from gmail's web interface, but gmail does like munging mail, so maybe it won't > It's just a lot easier to me to uncompress the tarball, give a look on > each individual file / process the tarball with RecipeLint and upload > exactly the same file which was submitted. Why? You're unpacking it and processing it anyway, after all. Also, I outlined three drawbacks in mailing MIMEd tarball attachments. > > Which package is ReviewRecipes in? > > It's just a simple script I've written and stored at my > /Files/Compile. It just performs RecipeLint and does a 'less' on its > contents. Seems like having a text-like format would remove one of those steps. Puzzled, -- MJ Ray - see http://mjr.towers.org.uk/email.html North End, Lynn, Norfolk, England Work: http://www.ttllp.co.uk/ IRC/Jabber/SIP: on request _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
