Imap Idle Launcher
Hi, I have made a little program to handle imap idle. It just connect to the imap server, send the idle command, and when it receives the message informing about new mail, launches the app of your choice (eg. getmail, mbsync or offlineimap). Maybe there already exist such an app ? If yes I could not find it... Anyway, if not, I would like to know if anyone other than me would be interested in it. Right now I just plan to use it for personnal use. But if a few other people also want it, I would work a little more to make it publicly available. Cheers, -- Vincent Aravantinos PhD Student - LIG - CAPP Team Grenoble, France 06.11.23.34.72 [EMAIL PROTECTED] http://membres-lig.imag.fr/aravantinos/
Re: Imap Idle Launcher
Quoting Vincent Aravantinos ([EMAIL PROTECTED]): > Anyway, if not, I would like to know if anyone other than me would > be interested in it. Right now I just plan to use it for personnal use. > But if a few other people also want it, I would work a little more to > make it publicly available. I'm not interested in such a tool, but i do know from experience that 'just putting it online somewhere' with some descriptive text beside it is the easiest way for people to find it. I do that with some of the tools i create for my own use. For example 'irssi-rss' is quite popular but i made no effort on distributing it other than some info on my site ;-) -Sndr. -- | A calendar's days are numbered. | 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D
How to prevent recoding of attachments?
Hi, when sending LaTeX files or translations of program strings mutt recodes them and breaks them. How can I prevent mutt sends the attachment with a different encoding as the local? In the LaTeX file I define the encoding of the file as option of the package inputenc. If I say utf8 there, mutt can't tell the recipient of the mail the file is encoded in latin1 or something else. For po files I've added the following line to ~/.mime.types, but I don't want to add an entry for all file types. How can I tell mutt not to change the encoding of attachments except for texts, i.e. files having the ending .txt. application/x-gettext po Bye, Jörg. -- Diskusion „Pascal vs. Rest der Welt“: 30 Aug 2000 00:13:11 GMT, Adrian Knoth <[EMAIL PROTECTED]> Und selbst wenn eure 10 Zeilen‐Programme noch so oft unter Windows verwendet werden: mit einem Handwagen fährt man nicht Formel‐1.
Re: How to prevent recoding of attachments?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday, October 9 at 02:27 PM, quoth Jörg Sommer: > when sending LaTeX files or translations of program strings mutt > recodes them and breaks them. How can I prevent mutt sends the > attachment with a different encoding as the local? In the LaTeX file > I define the encoding of the file as option of the package inputenc. > If I say utf8 there, mutt can't tell the recipient of the mail the > file is encoded in latin1 or something else. The easiest way is to compress them first. The fundamental problem is that text attachments get labeled with a character set, and mutt has to make sure that this label is correct. Your solution for po files solves this problem by tricking mutt into believing that it's not actually a text file. Mutt *can* attempt to guess what character set text file attachments are in, using the $attach_charset setting. Here's the snippet from the manual: attach_charset Type: string Default: "" This variable is a colon-separated list of character encoding schemes for text file attachments. If unset, the value of $charset will be used instead. For example, the following configuration would work for Japanese text handling: set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8" Note: for Japanese users, "iso-2022-*" must be put at the head of the value as show above if included. If you don't want mutt guessing, or if mutt proves to be pretty bad at guessing, the easiest workaround is to simply gzip your files before sending them - then mutt won't touch their insides. ~Kyle - -- Last comes the beverage of the Orient shore, Mocha, far off, the fragrant berries bore. Taste the dark fluid with a dainty lip, Digestion waits on pleasure as you sip. -- Pope Leo XII -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkjuNz4ACgkQBkIOoMqOI15hrwCgy8hskcOT2mZ/JM6SrZZl6grA nVsAoIwIHhFeBU/SK2LfnGPqNAuZZxAp =o20X -END PGP SIGNATURE-
Re: selecting "from" when sending an email
On Tue, Oct 07, 2008 at 12:14:57AM -0500, Kyle Wheeler wrote: > (and/or signatures), the answer is usually to create a macro that will > change all the necessary settings. For example: > > macro compose "set signature=~/.mutt/wifesig; my_hdr From: <[EMAIL > PROTECTED]>" Wait - does tell mutt that the F1 key is used to activate this macro? Yes, I'm really asking this, never saw saw mutt use the function keys. --
Re: selecting "from" when sending an email
Hi Jeff! On Thu, 09 Oct 2008, Jeff Kinz wrote: > On Tue, Oct 07, 2008 at 12:14:57AM -0500, Kyle Wheeler wrote: > > > > macro compose "set signature=~/.mutt/wifesig; my_hdr From: <[EMAIL > > PROTECTED]>" > > Wait - does tell mutt that the F1 key is used to activate > this macro? Yes. regards, Christian -- • If you need more than 3 levels of indentation, you're screwed anyway, and should fix your program. Linus Torvalds: Linux 1.3.53 CodingStyle documentation.
