Re: lbdb & m_gpg
Roland and Dave -- ...and then Roland Rosenfeld said... % On Fri, 25 Aug 2000, David T-G wrote: % % > $collection after lbdbq calls m_gpg_query and that they get stripped % > by munge and munge-keeporder. % % That's the point. Gotcha. % % > I'm not exactly sure what's going on in munge-keeporder, but munge % > appears to be building an array (named "line") indexed by email % > address -- only. % % Yes. This is a feature :-) Hokay :-) % % > Have I stumbled on a limitation of lbdbq and munge, or has my habit % > of keeping keys to decrypt old messages messed me up unlike anyone % > else? % % Don't forget that lbdb isn't used for decrypting mail but only for % collecting mail addresses and attached user names. It is intended to Hmmm... Well, that is a good point. I was thinking of it perhaps as a little DB of more things, like not just email addresses but also what keys are available and so on (more that I had not yet dreamed up ;-) % find hopefully all matching addresses/user names and to offer not too % many duplicates, which would make it useless. Gotcha. % % But I added a line to the TODO list to think about changing this % behavior... In retrospect I now understand this, so perhaps it needs not a change in behavior but a change in level of expectation or perception (or maybe just a change of user! :-) % % Tscho % % Roland % % -- % * [EMAIL PROTECTED] * http://www.spinnaker.de/ * ...and then Dave Pearson said... % On Fri, Aug 25, 2000 at 01:21:00PM -0400, David T-G wrote: % % > Any idea what's up this time? I don't think I could be storing my keys in % > the wrong format ;-) % % The only "problem" here is that you're focusing on keys when you really % should be concerning yourself with email addresses. That makes sense, especially in retrospect. While not worrying about using lbdb for decrypting, I was thinking of how it would be used to select keys, and the answers is that it probably won't... % % -- % Take a look in Hagbard's World: | mutt.octet.filter - autoview octet-streams % http://www.hagbard.demon.co.uk/ | mutt.vcard.filter - autoview simple vcards % http://www.acemake.com/hagbard/ | muttrc2html - muttrc -> HTML utility % Free software, including| muttrc.sl - Jed muttrc mode :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: lbdb & m_muttalias -- my questions now :-)
Roland ( & Brian) -- ...and then Roland Rosenfeld said... % On Fri, 25 Aug 2000, David T-G wrote: % % > alias me-bigfoot <[EMAIL PROTECTED]> (David @ BigFoot) % % As you can see, this is a simple grep output but sed didn't convert it % to the mutt query format, that's why the above (second) grep wipes % these lines out. Gotcha. % % m_muttalias only understands the following formats of aliases: % % alias foo User Name % alias foo foo@bar (User Name) Aha! Well, that would do it, then :-) % % and converts them both to % % foo@bar User Name alias foo % % Other alias syntax (like your combination of <...> and (...)) isn't % supported yet, because they don't make much sense to me and I don't I could probably go about redoing all of my aliases, but I still like the elm aliases lookup format. Perhaps once I fully make the move to lbdbq I'll start keeping my aliases in my mutt file only and use lbdbq to do my queries. Still, though, nobody does comments (anything after a comma in the alias definition, as in alias foo = Foo, lots of commentary for me (even here) = [EMAIL PROTECTED] for example) like elm supported... % see a canonical way to realize this (if you have patches against % m_muttalias to work around the problem, let me know). I'll work one up and forward it on unless I see something from you or Brian first. % % > but the grep -v seems to throw away these results. % % Yes, that's intended, because the syntax of these lines isn't % recognized. Gotcha. % % > SO... As far as I can read the grep regexp, grep is going to % > filter out anything like ... % % The trick here is the combination of grep, grep, sed, sed, grep -v: % % - I first grep selects all lines, which match the search string. % - The second grep tries to detect alias lines % - The first sed converts lines with <...> syntax to mutt query format % - The second sed converts lines with (...) syntax to mutt query format Oh; I get it! % - The grep -v wipes out all lines, which are still in the alias % format. This is necessary, because we need the lines in mutt query % format and if this conversion isn't possible, wiping out all lines, % which couldn't be converted, is the only chance. Yep; that's the key. % % If you provide a sed expression which converts aliases in your unusual % format (without changing other aliases!), I could add it above. Thanks, as always! % % > My question is "why is m_muttalias doing this?" so that I can figure % > out if I just want to junk that last grep % % This isn't a good idea, because converting these lines to mutt query % format before is necessary. Hokay. Time to start sedding, then. % % > or rewrite it to fit my alias format % % Adding a line for your alias format would do the job. Thanks! % % Tscho % % Roland % % -- % * [EMAIL PROTECTED] * http://www.spinnaker.de/ * :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: edit alias problem solved!
My problem here was I didn't have an editor specified in .bashrc. I just added export EDITOR=vim in .bashrc and alias editing works fine. Amazing what you can find in the manual.. Dale L . Morris ([EMAIL PROTECTED]) wrote: > When I try Esc a to edit my alias file, I receive the following: > /home/dlm/.mutt/aliases: line 2: syntax error near unexpected token >`<[EMAIL PROTECTED]>' > /home/dlm/.mutt/aliases: line 2: `alias spamSpam Recycle Bin ><[EMAIL PROTECTED]>' > Press any key to continue... > > I probably have something setup wrong in my .muttrc/settings file, but > I'm not sure what. Any ideas? > thanks > > > "Make voyages, attempt them, there's nothing else." > > -- "Make voyages, attempt them, there's nothing else." --Tennessee Williams
Re: lbdb & m_muttalias -- my questions now :-)
On Sun, 27 Aug 2000, David T-G wrote: > % m_muttalias only understands the following formats of aliases: > % > % alias foo User Name > % alias foo foo@bar (User Name) > Aha! Well, that would do it, then :-) > % and converts them both to > % > % foo@bar User Name alias foo > % > % Other alias syntax (like your combination of <...> and (...)) isn't > % supported yet, because they don't make much sense to me and I don't > I could probably go about redoing all of my aliases, but I still > like the elm aliases lookup format. Okay, then please try the attached diff against m_muttalias, which should support your converted elm aliases, but it is not fully tested (I don't know whether there are other side effects). > Still, though, nobody does comments (anything after a comma in the > alias definition, as in > > alias foo = Foo, lots of commentary for me (even here) = [EMAIL PROTECTED] > > for example) like elm supported... AFAIK Mutt doesn't support comments in the aliases. So you should think about writing a m_elm (or m_elmalias) module like m_pine to directly use the elm aliases with lbdb instead of converting them to the less powerful mutt alias format. This m_elm module may write the alias to the 3rd column of the mutt query format. Tscho Roland -- * [EMAIL PROTECTED] * http://www.spinnaker.de/ * Index: m_muttalias.sh.in === RCS file: /var/cvs/lbdb/m_muttalias.sh.in,v retrieving revision 1.3 diff -u -r1.3 m_muttalias.sh.in --- m_muttalias.sh.in 2000/06/23 10:20:13 1.3 +++ m_muttalias.sh.in 2000/08/26 15:02:32 @@ -35,7 +35,8 @@ then grep -i "$@" $file \ | grep '^alias[ ][ ]*[^,][^,]*[][ ]*[^,]*$' \ - | sed -e 's/^alias[ ][ ]*\([^ ][^ ]*\)[ ][ ]*\([^<>()]*\)<\([^<>()]*\)>[^()<>]*$/\3\2 alias \1/' \ + | sed -e 's/^alias[ ][ ]*\([^ ][^ ]*\)[ ][ +]*<\([^ >][^>]*\)>[ ][ ]*(\([^<>()]*\))[^()<>]*$/\2\3 + alias \1/' \ + -e 's/^alias[ ][ ]*\([^ ][^ ]*\)[ ][ +]*\([^<>()]*\)<\([^<>()]*\)>[^<>]*$/\3 \2 alias \1/' \ -e 's/^alias[ ][ ]*\([^ ][^ ]*\)[ ][ ]*\([^<>()]*\)(\([^<>()]*\))[^()<>]*$/\2\3 alias \1/' \ | grep -v '^alias[ ][ ]*[^,][^,]*[][ ]*[^,]*$' fi PGP signature
Re: edit alias problem solved!
Hi Dale! On Sun, 27 Aug 2000, Dale L . Morris wrote: > My problem here was I didn't have an editor specified in .bashrc. I > just added export EDITOR=vim in .bashrc and alias editing works fine. > Amazing what you can find in the manual.. > > Dale L . Morris ([EMAIL PROTECTED]) wrote: > > When I try Esc a to edit my alias file, I receive the following: > > /home/dlm/.mutt/aliases: line 2: syntax error near unexpected token >`<[EMAIL PROTECTED]>' > > /home/dlm/.mutt/aliases: line 2: `alias spamSpam Recycle Bin ><[EMAIL PROTECTED]>' > > Press any key to continue... > > > > I probably have something setup wrong in my .muttrc/settings file, but > > I'm not sure what. Any ideas? > > thanks Hey, thanks. This is a problem I've had for a while but never had the time to try to fix. -- B. L. Jilek <[EMAIL PROTECTED]> | ICQ: 83785391 GPG key: DSS 420837E6 | Linux user: 163800 PGP key: DSS 0x59D04FF1 RSA 0x83C89D21 | OS: SuSE Linux 6.3/2.2.16 Homepage: http://www.geocities.com/bljilek
Re: lbdb & m_muttalias -- my questions now :-)
Just to add a small point to this discussion. In the greps and seds in m_muttalias it is necessary to make sure as now that group aliases are rejected. This is why we do not just take lines that start with alias. Cheers, Brian. On Sun, Aug 27, 2000 at 04:54:54PM +0200, Roland Rosenfeld wrote: > On Sun, 27 Aug 2000, David T-G wrote: > > > % m_muttalias only understands the following formats of aliases: > > % > > % alias foo User Name > > % alias foo foo@bar (User Name) > > > Aha! Well, that would do it, then :-) > > > % and converts them both to > > % > > % foo@bar User Name alias foo > > % > > % Other alias syntax (like your combination of <...> and (...)) isn't > > % supported yet, because they don't make much sense to me and I don't > > > I could probably go about redoing all of my aliases, but I still > > like the elm aliases lookup format. > > Okay, then please try the attached diff against m_muttalias, which > should support your converted elm aliases, but it is not fully tested > (I don't know whether there are other side effects). > > > Still, though, nobody does comments (anything after a comma in the > > alias definition, as in > > > > alias foo = Foo, lots of commentary for me (even here) = [EMAIL PROTECTED] > > > > for example) like elm supported... > > AFAIK Mutt doesn't support comments in the aliases. So you should > think about writing a m_elm (or m_elmalias) module like m_pine to > directly use the elm aliases with lbdb instead of converting them to > the less powerful mutt alias format. This m_elm module may write > the alias to the 3rd column of the mutt query format. > > Tscho > > Roland patch deleted. -- Associate Professor Brian Salter-Duke (Brian Duke) [EMAIL PROTECTED] School of Biological, Environmental and Chemical Sciences, SITE, Northern Territory University, Darwin, NT 0909, Australia. Phone 08-89466702. Fax 08-89466847 http://www.smps.ntu.edu.au/school/compchem.html
pine2mutt_aliases.pl
Today I switched from Pine to mutt. According to homepage of mutt you had pine2mutt_aliases.pl available here: http://www.diku.dk/~pink/pine2mutt_aliases.pl But where the fsck it is now? -- Juhapekka "naula" Tolvanen * * * U of Jyväskylä * * [EMAIL PROTECTED] http://www.cc.jyu.fi/~juhtolv/index.html * "STRAIGHT BUT NOT NARROW!" - "so impressed with all you do. tried so hard to be like you. flew too high and burnt the wing. lost my faith in everything" nine inch nails
! question
I have a question. When I get new mail, much of the time it is marked with a ! but I don't know why. I've looked through the manual and see no reason new mail should be marked or tagged. There's probably an obvious answer, but I don't see it.. thanks --
Re: pine2mutt_aliases.pl
Juhapekka Tolvanen muttered: > > Today I switched from Pine to mutt. According to homepage of mutt you had > pine2mutt_aliases.pl available here: > > http://www.diku.dk/~pink/pine2mutt_aliases.pl > > But where the fsck it is now? look in the 'contrib' dir of the tarball there you'll find a 'Pine.rc'. Source that file in your .muttrc HTH, Michael -- If graphics hackers are so smart, why can't they get the bugs out of fresh paint? PGP-fingerprint: DECA E9D2 EBDD 0FE0 0A65 40FA 5967 ACA1 0B57 7C13
Re: Color in telnet sessions to mutt
On Sat, Aug 26, 2000 at 01:54:29PM +0930, Brian Salter-Duke wrote: : : On the Mac I use Microphone to connect to my machine. This does not : support color. Does anyone have any suggestions how I can support color : when connecting from a Mac? Try NCSA Telnet or its successor, MacTelnet: http://home.austin.rr.com/telnet/ I think dataComet and BetterTelnet also support ANSI color sequences. -- Eugene Lee [EMAIL PROTECTED]
Re: ! question
*[Dale L . Morris on Sun, Aug 27, 2000 at 04:59:39PM -0700]: > I have a question. When I get new mail, much of the time it is marked > with a ! but I don't know why. I've looked through the manual and see That's the way outhouse sexpress tags mail which is flagged 'urgent' (X-Priority and X-MS-Mail-Priority: - both of which are unnecessary when there's a valid 'priority:' header btw). Maybe you have a rule in your .muttrc which does this? > no reason new mail should be marked or tagged. There's probably an > obvious answer, but I don't see it.. -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI HELP! Man trapped in a human body!
