Re: S/MIME patch for Mutt-1.3.26
I know nothing about Ncurses, not even how to see it's version, but tried to link with it: The indicator seems to react well. It takes the reversed colors the current index line should be. But, for an unrelated to your patch reason, the color scheme of all the screen is messed up: in foreground what should be white appears black, red appears cyan, yellow is green, and blue is magenta... I have the same problems with slang, regardless of whether the indicator patch is applied. Is there a fix for this, or is it a limitation of slang? -- Mike Schiraldi VeriSign Applied Research smime.p7s Description: application/pkcs7-signature
Re: S/MIME patch for Mutt-1.3.26
On Mon, 28 Jan 2002, Mike Schiraldi wrote: I know nothing about Ncurses, not even how to see it's version, but tried to link with it: The indicator seems to react well. It takes the reversed colors the current index line should be. But, for an unrelated to your patch reason, the color scheme of all the screen is messed up: in foreground what should be white appears black, red appears cyan, yellow is green, and blue is magenta... I have the same problems with slang, regardless of whether the indicator patch is applied. Is there a fix for this, or is it a limitation of slang? I'm currently using debian, so I don't know about other distros. What I've found is that with debian, there is mutt (linked with slang), and mutt.curses (linked with ncurses). As I use kbd shortcuts anyway, I simply set up a shortcut to mutt.curses and it took care of the problems that I was having with the color. And setting up an alias named mutt to point to /usr/bin/mutt.curses isn't to hard either. 8o) Knute msg23905/pgp0.pgp Description: PGP signature
Re: S/MIME patch for Mutt-1.3.26
* Knute ([EMAIL PROTECTED]) [Jan 28. 2002 11:04]: I'm currently using debian, so I don't know about other distros. What I've found is that with debian, there is mutt (linked with slang), and mutt.curses (linked with ncurses). As I use kbd shortcuts anyway, I simply set up a shortcut to mutt.curses and it took care of the problems that I was having with the color. And setting up an alias named mutt to point to /usr/bin/mutt.curses isn't to hard either. 8o) What version/release of Debian are you using? I'm running a mix of woody and sid and my mutt is using ncurses rather than slang, and I didn't have to download any special version: (~)% ldd `which mutt` libncurses.so.5 = /lib/libncurses.so.5 (0x4001e000) (There is no mutt.curses on my machine) The package I'm using is mutt_1.3.27-1_i386.deb from sid. Not being a smart arse, g just pointing out that there may be differences in stable/testing/unstable. -- Brian Clark | Avoiding the general public since 1805! Fingerprint: 07CE FA37 8DF6 A109 8119 076B B5A2 E5FB E4D0 C7C8 It's been lovely, but I have to scream now.
Re: S/MIME patch for Mutt-1.3.26
On Mon, 28 Jan 2002, Brian Clark wrote: * Knute ([EMAIL PROTECTED]) [Jan 28. 2002 11:04]: I'm currently using debian, so I don't know about other distros. What I've found is that with debian, there is mutt (linked with slang), and mutt.curses (linked with ncurses). As I use kbd shortcuts anyway, I simply set up a shortcut to mutt.curses and it took care of the problems that I was having with the color. And setting up an alias named mutt to point to /usr/bin/mutt.curses isn't to hard either. 8o) What version/release of Debian are you using? I'm running a mix of woody and sid and my mutt is using ncurses rather than slang, and I didn't have to download any special version: (~)% ldd `which mutt` libncurses.so.5 = /lib/libncurses.so.5 (0x4001e000) (There is no mutt.curses on my machine) The package I'm using is mutt_1.3.27-1_i386.deb from sid. Not being a smart arse, g just pointing out that there may be differences in stable/testing/unstable. The name is mutt.ncurses, and I didn't have do dl anything extra to have it on here. Don't actually know where it came from to be honest with you. I do have both slang and ncurses on my machine. And I am using unstable as well. And I'm using the same package version as well, I am also using the urf8 one as well. (Don't quite know the diff atm, but it's there.) When I do a dpkg -S mutt.ncurses it was the mutt-utf8 package that created it. Since that is the one that is linked to slang. msg23921/pgp0.pgp Description: PGP signature
Re: S/MIME patch for Mutt-1.3.26
* Knute ([EMAIL PROTECTED]) [Jan 28. 2002 16:26]: [...] The name is mutt.ncurses, and I didn't have do dl anything extra to have it on here. Don't actually know where it came from to be honest with you. I do have both slang and ncurses on my machine. And I am using unstable as well. And I'm using the same package version as well, I am also using the urf8 one as well. (Don't quite know the diff atm, but it's there.) When I do a dpkg -S mutt.ncurses it was the mutt-utf8 package that created it. Since that is the one that is linked to slang. OK, here's what I get: (~)% dpkg -S mutt.ncurses dpkg: *mutt.ncurses* not found. (~)% dpkg -l mutt | egrep ii ii mutt 1.3.27-1 Text-based mailreader supporting MIME, GPG, Maybe what you decribe is done when one installs both packages (mutt and mutt-utf8) on the same machine. -- Brian Clark | Avoiding the general public since 1805! Fingerprint: 07CE FA37 8DF6 A109 8119 076B B5A2 E5FB E4D0 C7C8 Paralysis through analysis.
Re: S/MIME patch for Mutt-1.3.26
[followups set to users list only] Hello Mike, On Friday, January 18, 2002 at 2:34:51 PM -0500, Mike Schiraldi wrote: indicator.patch changes the behavior of the indicator bar when it is defined as mono indicator reverse (the default). [...] With this patch, the indicator bar, when set to reverse, will have a foreground color set to the background color that the current message would have if it were not selected, and a background color set to the foreground color that the current message would have if it were not selected. This context colored indicator patch seems to have no effect when Mutt (versions 1.2.5 and 1.3.27) is linked with slang (version 1.4.4). Tested on 2 different terminals (directly on Linux console and from Cygwin's telnet), the indicator is simply black ink on white paper as without the patch. I know nothing about Ncurses, not even how to see it's version, but tried to link with it: The indicator seems to react well. It takes the reversed colors the current index line should be. But, for an unrelated to your patch reason, the color scheme of all the screen is messed up: in foreground what should be white appears black, red appears cyan, yellow is green, and blue is magenta... Green, magenta, cyan and white appear correctly. Background colors are also messed up, but not in the same way. And sometimes changing an item color (let's say quoted4) will also change in some way the color of another item (say status). What have they put in my glass? Quick come back to Slang! And noted somewhere to not try again drugs too strong for me. ;-) Someone knows how to make indicator.patch work with Slang? Bye!Alain.
Re: S/MIME patch for Mutt-1.3.26
This context colored indicator patch seems to have no effect when Mutt (versions 1.2.5 and 1.3.27) is linked with slang (version 1.4.4). Yow! I'll take a look and post my findings. -- Mike Schiraldi VeriSign Applied Research smime.p7s Description: application/pkcs7-signature
Re: S/MIME patch for Mutt-1.3.26
The S/MIME patch i posted for 1.3.26 also works with 1.3.27. -- Mike Schiraldi VeriSign Applied Research smime.p7s Description: application/pkcs7-signature
Re: S/MIME patch for Mutt-1.3.26
[18.01.02 14:34 -0500] Mike Schiraldi -- : Attached is a version of the S/MIME patch that will work with mutt-1.3.26. (Or at least it appears to work -- let me know if you have any problems) Yes, I have dam.. fu... problems with it !!! Did you ever hear that you do not post thousands of lines for patches ??? What the hell do you think URLs are for ??? And do you really expect me to apply a patch from someone who is already violating the simplest rules - god knows what is coming up with the patch then ... - except the extra costs for my bill (no, not everyone has a backbone downstairs). Sorry all, but after those 2 digests I am really more than angry about people who do not care about anything than themselves and think polluting the net is normal behaviour. ;)) -- for all of you others. Erika
Re: S/MIME patch for Mutt-1.3.26
Works well for me. The patches didn't apply without some offsets, but they all applied with no rejs. Thanks, pete On Fri, 18 Jan 2002, Schiraldi, Mike wrote: Attached is a version of the S/MIME patch that will work with mutt-1.3.26. (Or at least it appears to work -- let me know if you have any problems) If this is your first time using the S/MIME patch, visit the project page at http://elmy.myip.org/mutt/smime.html and download the smime-keys.pl script so you can import your keys. Also attached are two patches you can optionally apply afterward. They work best together: color4.patch adds a new pattern, ~V, which returns true if the message has a verified signature (i.e. shows up with an S in the index). This works for both PGP and S/MIME. I suggest using it with the following .muttrc lines: color index yellow default ~g color index green default ~V indicator.patch changes the behavior of the indicator bar when it is defined as mono indicator reverse (the default). Usually it would always make the indicator bar have a foreground that is set to the default background color and a background that is set to the default foreground color. With this patch, the indicator bar, when set to reverse, will have a foreground color set to the background color that the current message would have if it were not selected, and a background color set to the foreground color that the current message would have if it were not selected. In summary, if you apply all three patches and add those two lines to your .muttrc, you'll see signed messages in yellow and verified messages in green. The indicator bar will also turn these colors to reflect the status of the currently selected message. If you use pager_index_lines to keep part of the index onscreen while reading messages, you'll be able to clearly see, by looking at the indicator bar, whether or not the message you are currently reading is signed, and whether or not that signature is valid. -- Pete Toscano[EMAIL PROTECTED]703.948.3364
