date:20010906


so this is a bit off topic, but does anyone have a simple set of vim
macros to interface with ispell (or an easy way to spellcheck a file
after editing without leaving mutt)?  i'm usually a decent speller but
it is annoying not to be able to check a particular word or paragraph.

i downloaded one such set of macros (from i forget where) but it was a
bit complex for my needs.

w

-- 
Sintax error in config file! (line 378)
aborted!

PGP Public Key:
http://infinitejazz.net/will/pgp/

Re: GnuPG + Mutt and Outlook + PGP-7.0 recipient and reverse.

2001-09-06 Thread Thomas Roessler


On 2001-09-06 03:12:36 -0400, David T-G wrote:

% How can I make PGP 7.0 messages readable by mutt? (I saw a procmail recipe
% once, even had it in my .prcmailrc once, but accidentally deleted it :-()

Are you perhaps looking for the recipes in PGP-Notes.txt in the distro?

The procmail recipe given there is just one possible solution. I'd 
suggest that you try Esc-P instead.

-- 
Thomas Roesslerhttp://log.does-not-exist.org/

 PGP signature

Re: vim / ispell


 * Will Yardley [EMAIL PROTECTED] [09-Thu-01 02:13 -0700]:
 
 so this is a bit off topic, but does anyone have a simple
 set of vim macros to interface with ispell (or an easy way
 to spellcheck a file after editing without leaving mutt)?
 i'm usually a decent speller but it is annoying not to be
 able to check a particular word or paragraph.

i wonder if this is what you are looking for :

http://users.erols.com/astronaut/vim/#Spelling

hth,

denis

-- 
// mailto: Denis Perelyubskiy [EMAIL PROTECTED]
// icq   : 12359698
// PGP   : http://www.cs.ucla.edu/~denisp/files/pgp.asc

[william+mutt@hq.newdream.net: iconv etc]


woah - just as i was about to delete this message, i noticed that there
are two User-Agent: headers.  

i accidentally responded off list at first, which bounced, and i then
forwarded the resulting message to the list.  mutt should remove the old
User-Agent header though, right?

From: Will Yardley [EMAIL PROTECTED]
To: Mutt Users [EMAIL PROTECTED]
Subject: iconv etc
Date: Wed, 5 Sep 2001 05:19:41 -0700
User-Agent: Mutt/1.3.22.1i
User-Agent: Mutt/1.3.22.1i
Message-ID: [EMAIL PROTECTED]

in the actual meessage file:

Received: by mail.hq.newdream.net (Postfix, from userid 1012)
id 405103B37D; Wed,  5 Sep 2001 05:19:41 -0700 (PDT)
Date: Wed, 5 Sep 2001 05:19:41 -0700
From: Will Yardley [EMAIL PROTECTED]
To: Mutt Users [EMAIL PROTECTED]
Subject: iconv etc
Message-ID: [EMAIL PROTECTED]
Mail-Followup-To: Mutt Users [EMAIL PROTECTED]
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary=QTprm0S8XgL7H0Dt
Content-Disposition: inline
User-Agent: Mutt/1.3.22.1i
User-Agent: Mutt/1.3.22.1i
Sender: [EMAIL PROTECTED]
Precedence: bulk
Lines: 140

in my sent-mail folder:

From: Will Yardley [EMAIL PROTECTED]
To: Lars Hecking [EMAIL PROTECTED]
Subject: Re: [[EMAIL PROTECTED]: Undelivered Mail Returned to 
Sender]
Date: Wed, 5 Sep 2001 05:18:13 -0700
User-Agent: Mutt/1.3.22.1i
Message-ID: [EMAIL PROTECTED]

same message-id, same message 

From: Will Yardley [EMAIL PROTECTED]
To: Mutt Users [EMAIL PROTECTED]
Subject: Re: iconv etc
Date: Wed, 5 Sep 2001 05:47:52 -0700
User-Agent: Mutt/1.3.22.1i
Message-ID: [EMAIL PROTECTED]


-w

-- 
Sintax error in config file! (line 378)
aborted!

PGP Public Key:
http://infinitejazz.net/will/pgp/

Re: wierd new mail problem

2001-09-06 Thread Brendan Cully


On Thursday, 06 September 2001 at 00:51, Derek Martin wrote:
 Hey all,
 
 I'm using mutt 1.2.5i, and I've got a very strange problem with new
 mail.  I'm using mutt to access IMAP folders, and the binary and
 shared data reside on NFS.  Here's the problem:
 
 On some systems where I run mutt, it works as you would expect.  On
 others, after I read all the new messages in a folder which it marked
 as having new mail, and then try to change to the next folder with new
 mail, but it would send me back into the same folder, thinking that
 there was still new mail there.  Going back out to the index also
 reveals that mutt thinks there's still new mail in the folder, but
 re-entering the folder shows that there isn't any new mail.

First of all, for anything IMAP-related I'd strongly recommend you pick
up the latest mutt beta (currently 1.3.22.1), since that code has
changed quite a lot.

Second, what do you mean by 'shared data'? Are the mailboxes you're
accessing all on IMAP?

And finally, what server are you using? (you can find this out by
telnetting to the host and port (143 by default) of your server and
reading the welcome line).

-Brendan

Re: vim / ispell

2001-09-06 Thread Ken Weingold


On Thu, Sep  6, 2001, Will Yardley wrote:
 so this is a bit off topic, but does anyone have a simple set of vim
 macros to interface with ispell (or an easy way to spellcheck a file
 after editing without leaving mutt)?  i'm usually a decent speller but
 it is annoying not to be able to check a particular word or paragraph.
 
 i downloaded one such set of macros (from i forget where) but it was a
 bit complex for my needs.

Will, I think you are looking for 'i' in the Compose menu, after you
leave your editor.  It will run ispell on the email.


-Ken

Re: Make it simple?

2001-09-06 Thread Adam Shostack


mea culpa.

It was not mutt that was causing the coloring I was seeing, it was the
effects of /etc/emacs/site-start.el including a (setq font-lock-mode)

But life is so much nicer with that turned off. :)

Adam


On Tue, Aug 21, 2001 at 10:03:24AM -0400, Adam Shostack wrote:
 Thats what I started with (well, grey on black), but I'd really like
 to end up with ugly-black-on-white.  I can get that by seting my term
 to something stupid, but unless it gets really stupid, I can't get
 rid of the quote_regexp effects.  Does unset quote_regexp work for
 others, or is there a bug that I'm encountering?
 
 Adam
 
 On Tue, Aug 21, 2001 at 11:46:32AM +0200, Thomas Roessler wrote:
  Just remove all the color statements from your configuration files. 
  You should end up with ugly white-on-black. ;-)
  
  On 2001-08-17 17:17:40 -0400, Adam Shostack wrote:
  Date: Fri, 17 Aug 2001 17:17:40 -0400
  From: Adam Shostack [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Subject: Make it simple?
  User-Agent: Mutt/1.2.5i
  
  Hi,
  
  I just upgraded to mutt 1.2.5, and its insisting on coloring
  everything.  I managed to get close to what I want by commenting
  HAVE_COLOR out of config.h, but now I still get things like
  underlining quoted text, boldface in headers, etc.  I want plain
  text.  Suggestions for how to get there?
  
  Adam
  
  
  
  -- 
  Thomas Roesslerhttp://log.does-not-exist.org/
 
 -- 
 It is seldom that liberty of any kind is lost all at once.
  -Hume
 
 

-- 
It is seldom that liberty of any kind is lost all at once.
   -Hume

Re: vim / ispell

2001-09-06 Thread Andy Smith


On Thu, Sep 06, 2001 at 10:20:41AM -0400, Ken Weingold wrote:

 Will, I think you are looking for 'i' in the Compose menu, after you
 leave your editor.  It will run ispell on the email.

Is it possible to make this ignore quoted text and perhaps
headers/attributions too?

Color

2001-09-06 Thread Dave Spracklen


I understand how to use the color settings in the configuration file. My
problem is that although I use color_xterm which is fully color compatible
(including using color0 etc) I can't figure out how I convince mutt to use
color. At first I thought I was doing something wrong, but when I added in some
'mono' configuration options these immediately began working. I don't see
anything in the manual or man pages related to forcing mutt to use the color
options rather than the mono ones. I've tried switching my TERM from xterm to
vt100 just out of curiosity, but of course that didn't do anything. What's up? 
How can I get this going?

Dave

Re: Color

2001-09-06 Thread Ken Weingold


On Thu, Sep  6, 2001, Dave Spracklen wrote:
 I understand how to use the color settings in the configuration file. My
 problem is that although I use color_xterm which is fully color compatible
 (including using color0 etc) I can't figure out how I convince mutt to use
 color. At first I thought I was doing something wrong, but when I added in some
 'mono' configuration options these immediately began working. I don't see
 anything in the manual or man pages related to forcing mutt to use the color
 options rather than the mono ones. I've tried switching my TERM from xterm to
 vt100 just out of curiosity, but of course that didn't do anything. What's up? 
 How can I get this going?

I don't know what OS you are on, but under Solaris, the only term that
would work to get color was dtterm.  I figured this out since color
would work in the CDE Terminal, but not under any other, with whatever
other term settings I tried.

HTH...


-Ken

Re: Color

2001-09-06 Thread Tim Whitehead



this is actually a reply to the original message which I (unfortunately)
deleted.

try TERM=xterm-color

I just had to write a wrapper so I could have gkrellm call mutt. Originally mutt
would pop up, but be in mono. So my wrapper is as follows

#!/bin/bash

wait 1;
export TERM=xterm-color;
/usr/bin/mutt;


seems to work...

tw


Le jour Thu Sep 06, 2001 at 11:36:49AM -0400, Ken Weingold ([EMAIL PROTECTED]) a 
écrit...

 On Thu, Sep  6, 2001, Dave Spracklen wrote:
  I understand how to use the color settings in the configuration file. My
  problem is that although I use color_xterm which is fully color compatible
  (including using color0 etc) I can't figure out how I convince mutt to use
  color. At first I thought I was doing something wrong, but when I added in some
  'mono' configuration options these immediately began working. I don't see
  anything in the manual or man pages related to forcing mutt to use the color
  options rather than the mono ones. I've tried switching my TERM from xterm to
  vt100 just out of curiosity, but of course that didn't do anything. What's up? 
  How can I get this going?
 
 I don't know what OS you are on, but under Solaris, the only term that
 would work to get color was dtterm.  I figured this out since color
 would work in the CDE Terminal, but not under any other, with whatever
 other term settings I tried.
 
 HTH...
 
 
 -Ken

-- 
Timothy Mark Whitehead  // Sophomore, UW - Madison  
tmwhitehead(at)students.wisc.edu// Intended Major: Computer Engineering 
tigmoid(at)146.151.75.25// SUPPORT YOUR LOCAL COLLEGE STUDENT!! 
whitehea(at)cs.wisc.edu // -- UW-Navs, UW-Band, UW-Trumpet
tigmoid(at)jps.net  // Do you, eh, look at headers? 
public static String sig(String sig) { if(sig.equals(this.sig))sig = sig(sig); }

Re: vim / ispell

2001-09-06 Thread Byrial Jensen


On Thu, Sep 06, 2001 at 16:11:50 +0100, Andy Smith wrote:
 On Thu, Sep 06, 2001 at 10:20:41AM -0400, Ken Weingold wrote:
 
  Will, I think you are looking for 'i' in the Compose menu, after you
  leave your editor.  It will run ispell on the email.
 
 Is it possible to make this ignore quoted text and perhaps
 headers/attributions too?

Yes, I made a program to do excatly this.

Find it at http://home.worldonline.dk/~byrial/spellutils/.

Re: Color


 * Tim Whitehead [EMAIL PROTECTED] [09-Thu-01 09:05 -0700]:
 
 this is actually a reply to the original message which I (unfortunately)
 deleted.
 
 try TERM=xterm-color
 
 I just had to write a wrapper so I could have gkrellm call mutt. Originally mutt
 would pop up, but be in mono. So my wrapper is as follows
 
 #!/bin/bash
 
 wait 1;
 export TERM=xterm-color;
 /usr/bin/mutt;

it almost sounds like this could be set in the .bashrc,
.tcshrc, or whatever the shell that you are using, no?

i've never used gkrellm, but does it not set TERM variable
at all? if it does, then you can put it a small condition to
reset it to something more appropriate in your startup file.

just a suggestion,

denis

-- 
// mailto: Denis Perelyubskiy [EMAIL PROTECTED]
// icq   : 12359698
// PGP   : http://www.cs.ucla.edu/~denisp/files/pgp.asc

Re: Color

2001-09-06 Thread Tim Whitehead



I think that the problem is in my /etc/profile 

if [ $COLORTERM = Eterm ]; then
TERM=xterm-color
else
TERM=linux
fi

This may be what is throwing off the TERM var. Because when I comment out the
wait line, mutt comes up in mono again. 

any suggestions?


tw


Le jour Thu Sep 06, 2001 at 09:59:48AM -0700, Denis Perelyubskiy ([EMAIL PROTECTED]) 
a écrit...

  * Tim Whitehead [EMAIL PROTECTED] [09-Thu-01 09:05 -0700]:
  
  this is actually a reply to the original message which I (unfortunately)
  deleted.
  
  try TERM=xterm-color
  
  I just had to write a wrapper so I could have gkrellm call mutt. Originally mutt
  would pop up, but be in mono. So my wrapper is as follows
  
  #!/bin/bash
  
  wait 1;
  export TERM=xterm-color;
  /usr/bin/mutt;
 
 it almost sounds like this could be set in the .bashrc,
 .tcshrc, or whatever the shell that you are using, no?
 
 i've never used gkrellm, but does it not set TERM variable
 at all? if it does, then you can put it a small condition to
 reset it to something more appropriate in your startup file.
 
 just a suggestion,
 
 denis
 
 -- 
 // mailto: Denis Perelyubskiy [EMAIL PROTECTED]
 // icq   : 12359698
 // PGP   : http://www.cs.ucla.edu/~denisp/files/pgp.asc

-- 
Timothy Mark Whitehead  // Sophomore, UW - Madison  
tmwhitehead(at)students.wisc.edu// Intended Major: Computer Engineering 
tigmoid(at)146.151.75.25// SUPPORT YOUR LOCAL COLLEGE STUDENT!! 
whitehea(at)cs.wisc.edu // -- UW-Navs, UW-Band, UW-Trumpet
tigmoid(at)jps.net  // Do you, eh, look at headers? 
public static String sig(String sig) { if(sig.equals(this.sig))sig = sig(sig); }

Re: fcc

2001-09-06 Thread Vineet Kumar


* Will Yardley ([EMAIL PROTECTED]) [010905 12:27]:
 Vineet Kumar wrote:
This command specifies folders which can receive mail and which will
be checked for new messages.  By default, the main menu status bar
displays how many of these folders have new messages.
  
  You don't want mutt to let you know of new mail in sent-mail? don't
  include it in your mailboxes line.
 
 yes  but on other machines mutt doesn't do this. i like having sent-mail
 in the mailboxes list so that it's included in my default folder list.
 i was hoping there was another way to do this.  no worries though.

Gotcha. 'fraid I don't know how to make that happen. I could point out,
though, that '' is a shorthand for your sent-mail folder (or, more
precisely, for the folder named in the $record variable.)

So it mightn't show up in the list, but you can always just use 'c' to
get there quickly.

 
 -- 
 Sintax error in config file! (line 378)
 aborted!

D'oh! Totally got me -- I thought it was an automated sig-generator
pooping out. (Though I didn't think till now 378 lines for a sig
generator?! It had better make coffee, too...)

-- 
Vineet   http://www.anti-dmca.org
Unauthorized use of this .sig may constitute violation of US law.
echo Qba\'g gernq ba zr\! |tr 'a-zA-Z' 'n-za-mN-ZA-M'

 PGP signature

Re: wierd new mail problem

2001-09-06 Thread Derek Martin


On Thu, Sep 06, 2001 at 11:07:41AM +0200, Thomas Roessler wrote:
 On 2001-09-06 00:51:56 -0400, Derek Martin wrote:
 
 On some systems where I run mutt, it works as you would expect. 
 On others, after I read all the new messages in a folder which it 
 marked as having new mail, and then try to change to the next 
 folder with new mail, but it would send me back into the same 
 folder, thinking that there was still new mail there.  Going back 
 out to the index also reveals that mutt thinks there's still new 
 mail in the folder, but re-entering the folder shows that there 
 isn't any new mail.
 
 Are the clocks on all computers involved synchronized using ntp?

Well... from my original post:

On Thu, Sep 06, 2001 at 12:51:56AM -0400, Derek Martin wrote:
 Hey all,
[SNIP]
 All machines are running with the same binary from NFS, accessing the
 same IMAP server.  No two clients are started at the same time, so
 it's not a locking problem.  All machines are synchronized via NTP, so
 the system time on all 5 machines is within about 10 ms.


On Thu, Sep 06, 2001 at 07:51:41AM -0400, Brendan Cully wrote:
 First of all, for anything IMAP-related I'd strongly recommend you pick
 up the latest mutt beta (currently 1.3.22.1), since that code has
 changed quite a lot.

Thanks.   I'll give that a shot...  How do I get it though?  I only see links
for the stable 1.2 tree.

 Second, what do you mean by 'shared data'? 

I mean stuff that mutt's make install would ordinarily put in /etc
is in /nfs/etc (shared), and anything it would usually put in
/usr/share is in /nfs/share (shared).

 Are the mailboxes you're accessing all on IMAP?

Yes.


 And finally, what server are you using? (you can find this out by
 telnetting to the host and port (143 by default) of your server and
 reading the welcome line).

UW IMAP.  Or, if the actual welcome line makes a difference to you,
it's here:

  * OK myhostname IMAP4rev1 v12.264 server ready


-- 
---
Derek Martin  |   Unix/Linux geek
[EMAIL PROTECTED]|   GnuPG Key ID: 0x81CFE75D
Retrieve my public key at http://pgp.mit.edu



-- 
---
Derek Martin  |   Unix/Linux geek
[EMAIL PROTECTED]|   GnuPG Key ID: 0x81CFE75D
Retrieve my public key at http://pgp.mit.edu

Re: Getting the name of the current folder for macros

2001-09-06 Thread Vineet Kumar

* Alexander Skwar ([EMAIL PROTECTED]) [010829 15:18]:
So sprach ?Alexander 'Digital Projects' Skwar? am 2001-08-25 um 11:30:50 +0200 :
I'd like to assign a macro to a key, which allows me to easily store all
the messages of a folder in another folder.

I normally archive all the messages I get. To do so for this list, I'd
tag all the messages in the current folder (which only contains messages
from this list), clear the old flag of all the messages and save all the
messages in =Old/ML-MUTT.bz2. The current folder is named ML-MUTT.

What I can't seem to figure out, is how I can get the name of the
current folder. If I had this, I'd write in my muttrc:

macro index \Co

tag-pattern.entertag-prefixclear-flagotag-prefixsave-message=Old/NAME_OF_CURRENT_FOLDER.bz2enter

How can I get the name of the current folder so that I can assign it in
a macro?

Is this really impossible to do?

You could hack it by setting the value of record or mbox based on
folder-hook and then referencing that value in your macro. Be careful
that you don't need the value before you clobber it with this hack,
though (i.e. use mbox if you're not using move, or record if you're not
using copy).

It would basically look like this:

# THIS IS A DIRTY, DIRTY HACK. PROCEED WITH CAUTION
set copy=no
folder-hook mutt-user 'set record==Old/mutt-user'
macro index \Co
tag-pattern.entertag-prefixclear-flagotag-prefixsave-message.bz2enter

I also don't know about how the '' might need to be quoted in the macro
statement. This is totally untested, and just off the top of my head
(and I'm no expert). As always, YMMV.

--
Vineet http://www.anti-dmca.org
Unauthorized use of this .sig may constitute violation of US law.
echo Qba\'g gernq ba zr\! |tr 'a-zA-Z' 'n-za-mN-ZA-M'

PGP signature

Wierd mbox/IMAP behavior

2001-09-06 Thread Louis LeBlanc


Wierd behavior here.  I use IMAP, and don't move mail I've read to
another mailbox.  I usually have it delivered right where I want it.

Anyway, I found that when I set mbox in my muttrc to point to my INBOX
on the IMAP server, it would often not save the status or flags for
more recent messages - a read message would be marked new next time I
got on, a message I replied to didn't have the r flag, etc.

Anyway, I found that I could fix this by unsetting the mbox directive
in my muttrc.

Now something wierd happened.  I just did a c to change to the main
folder (folder and spoolfile directives both point to the INBOX).
Anyway, when it changes, I see multiple copies of every message in my
INBOX, plus copies of every other message I've read in other
mailboxes.

Here is what I've got for relevant config directives (I think):
set folder={[EMAIL PROTECTED]}INBOX
set spoolfile={[EMAIL PROTECTED]}INBOX
set mbox={acadia.ne.mediaone.net}INBOX

As near as I could tell, this was the way to do it for IMAP, but it
looks like I'm doing something wrong.

Can someone toss me a clue?

Thanks

Lou
-- 
Louis LeBlanc   [EMAIL PROTECTED]
Fully Funded Hobbyist, KeySlapper Extrordinaire :)
http://acadia.ne.mediaone.net ԿԬ

... an experienced, industrious, ambitious, and often quite often
picturesque liar.
-- Mark Twain

Re: vim / ispell


Byrial Jensen wrote:
 On Thu, Sep 06, 2001 at 16:11:50 +0100, Andy Smith wrote:
  On Thu, Sep 06, 2001 at 10:20:41AM -0400, Ken Weingold wrote:

   Will, I think you are looking for 'i' in the Compose menu, after
   you leave your editor.  It will run ispell on the email.

duh! that's exactly what i wanted.

  Is it possible to make this ignore quoted text and perhaps
  headers/attributions too?
 
 Yes, I made a program to do excatly this.
 
 Find it at http://home.worldonline.dk/~byrial/spellutils/.

and that's even better.  seems to work well so far.

w

-- 
Sintax error in config file! (line 378)
aborted!

PGP Public Key:
http://infinitejazz.net/will/pgp/

Re: Wierd mbox/IMAP behavior

2001-09-06 Thread Brendan Cully


On Thursday, 06 September 2001 at 15:33, Louis LeBlanc wrote:
 Wierd behavior here.  I use IMAP, and don't move mail I've read to
 another mailbox.  I usually have it delivered right where I want it.
 
 Anyway, I found that when I set mbox in my muttrc to point to my INBOX
 on the IMAP server, it would often not save the status or flags for
 more recent messages - a read message would be marked new next time I
 got on, a message I replied to didn't have the r flag, etc.
 
 Anyway, I found that I could fix this by unsetting the mbox directive
 in my muttrc.

I think what you want is the $move option, which you should set to
'no'. Also keep an eye out for any mbox-hooks you might have lying
around.

 Now something wierd happened.  I just did a c to change to the main
 folder (folder and spoolfile directives both point to the INBOX).

the ''  switches to $mbox, which you aren't interested in. To get back
to the spoolfile, use '!'.

 Anyway, when it changes, I see multiple copies of every message in my
 INBOX, plus copies of every other message I've read in other
 mailboxes.

I don't know exactly what's happening here. Frankly I'm like you and
have $move perpetually turned off (everything's already filtered to the
right place), so bugs seem to crop up here more often than usual.

 Here is what I've got for relevant config directives (I think):
 set folder={[EMAIL PROTECTED]}INBOX
 set spoolfile={[EMAIL PROTECTED]}INBOX
 set mbox={acadia.ne.mediaone.net}INBOX
 
 As near as I could tell, this was the way to do it for IMAP, but it
 looks like I'm doing something wrong.

If you have $move off, $mbox shouldn't even be used. But, one thing I
can say is mutt's mailbox comparison is exceedingly stupid (basically
just a strcmp), so to it your $mbox and $spoolfile appear to be
different mailboxes even though they're not. This is probably what's
gotten mutt confused and acting weird.

I'd written about half of a proper mailbox comparison function a couple
days ago (for a very similar problem), but scrapped it a couple of days
ago for a less reliable fix (I tried to canonify paths when they were
entered, so we could use the less expensive strcmp later). It may be
that was the wrong approach.

But on the other hand, you might try current CVS and see if it works out
for you. Oh, one final note: using the imap URL format
(eg imap:[EMAIL PROTECTED]/INBOX) tends to work a bit
better, since that's what mutt uses internally.

In short, I don't really know what happened :)

-Brendan

Re: Color


 * Tim Whitehead [EMAIL PROTECTED] [09-Thu-01 10:18 -0700]:
 
 I think that the problem is in my /etc/profile 
 
 if [ $COLORTERM = Eterm ]; then
 TERM=xterm-color
 else
 TERM=linux
 fi
 
 This may be what is throwing off the TERM var. Because
 when I comment out the wait line, mutt comes up in mono
 again. 
 
 any suggestions?

maybe something along the lines of 

if [ $COLORTERM = Eterm ]; then
  TERM=xterm-color
elif [ $TERM = gkrellm ]; then
  TERM=xterm-color
else
  TERM=linux
fi

i am not too good with bash in general. i just go try to
figure out things i need wheni need them :)

also, check what $TERM var says when you log in using your
gkrellm. that test in 'elif' may need to be modified if TERM
is not gkrellm

also, neither do i know if this is an *official* bash way,
but things like these work in my startup files, even though
maybe they disgust people who really know bash :)

denis

-- 
// mailto: Denis Perelyubskiy [EMAIL PROTECTED]
// icq   : 12359698
// PGP   : http://www.cs.ucla.edu/~denisp/files/pgp.asc

[ot?] - is there a human admin on this list


hello,

sorry, but could not find answer to this on a web page.
every time i mail the list, i get one of the auto-responders
replying that such and such person is not with the company
anymore, and i should contact someone else for questions.
(i wont mention that i think whoever set that thing up
screwed up, but anyway...)

so, i was wondering if there is a 'human' i could mail to
see if they could get the person of the list? 

thanks,

denis

-- 
// mailto: Denis Perelyubskiy [EMAIL PROTECTED]
// icq   : 12359698
// PGP   : http://www.cs.ucla.edu/~denisp/files/pgp.asc

Re: Color


Denis Perelyubskiy wrote:
 maybe something along the lines of 
 
 if [ $COLORTERM = Eterm ]; then
   TERM=xterm-color
 elif [ $TERM = gkrellm ]; then
   TERM=xterm-color
 else
   TERM=linux
 fi

i only use xterm-color when i have to - apparently it's a bad setting to
use for some reason (maybe someone else can clarify this).  if you're
using XFree86, xterm-xfree86 might be a better setting if it works.

w

-- 
Sintax error in config file! (line 378)
aborted!

PGP Public Key:
http://infinitejazz.net/will/pgp/

Re: Color


On Thu, Sep 06, 2001 at 02:05:34PM -0700, Will Yardley wrote:
 Denis Perelyubskiy wrote:
  maybe something along the lines of 
  
  if [ $COLORTERM = Eterm ]; then
TERM=xterm-color
  elif [ $TERM = gkrellm ]; then
TERM=xterm-color
  else
TERM=linux
  fi
 
 i only use xterm-color when i have to - apparently it's a bad setting to
 use for some reason (maybe someone else can clarify this).  if you're
 using XFree86, xterm-xfree86 might be a better setting if it works.

ditto for Eterm (it comes with its own terminfo entry, which also is in
ncurses).

-- 
Thomas E. Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net

Re: wierd new mail problem

2001-09-06 Thread Derek Martin


On Thu, Sep 06, 2001 at 12:51:56AM -0400, Derek Martin wrote:
 On some systems where I run mutt, it works as you would expect.  On
 others, after I read all the new messages in a folder which it marked
 as having new mail, and then try to change to the next folder with new
 mail, but it would send me back into the same folder, thinking that
 there was still new mail there.  Going back out to the index also
 reveals that mutt thinks there's still new mail in the folder, but
 re-entering the folder shows that there isn't any new mail.

I think I've narrowed down the cause of the problem to one (or more)
of the Red Hat update RPMs.  I installed all of the update RPMs for
RH7.1 on the one system that was working, and now it doesn't.

I'm thinking I need to re-compile on a machine with the update
rpms...  Unfortunately this means not all of our users will be able to
run it off NFS. 

-- 
---
Derek Martin  |   Unix/Linux geek
[EMAIL PROTECTED]|   GnuPG Key ID: 0x81CFE75D
Retrieve my public key at http://pgp.mit.edu

Re: Color

2001-09-06 Thread David Champion


On 2001.09.06, in [EMAIL PROTECTED],
Denis Perelyubskiy [EMAIL PROTECTED] wrote:
 
 also, neither do i know if this is an *official* bash way,
 but things like these work in my startup files, even though
 maybe they disgust people who really know bash :)

What bothers me about this approach, in general, is that it's not
supposed to depend on your shell -- you're not supposed to need to make
tests and reset $TERM accordingly at all. The point of terminfo/termcap
and the $TERM variable is that the terminal emulator application should
tell the shell what terminal it's emulating by means of $TERM, and
everything should work.

If it doesn't, then something is wrong with your terminfo library or
your termcap file, or your terminal emulator is lying.
needs new options or resources.


That said, I occasionally change my $TERM from xterm to something I
like, just to get rid of the alternate (application-mode?) screen
setting. But there are better ways of doing this (xterm -ti vt100, or
modifying a private copy in $TERMINFO); I'm just lazy.

I suspect that there's always a better approach than shell-rc case
switching. If not, then your terminal emulator needs new options or
resources.

-- 
 -D.[EMAIL PROTECTED]NSITUniversity of Chicago

Re: Color


 * David Champion [EMAIL PROTECTED] [09-Thu-01 14:59 -0700]:
 
 What bothers me about this approach, in general, is that it's not
 supposed to depend on your shell -- you're not supposed to need to make
 tests and reset $TERM accordingly at all. The point of terminfo/termcap
 and the $TERM variable is that the terminal emulator application should
 tell the shell what terminal it's emulating by means of $TERM, and
 everything should work.

this makes sense to me
 
 If it doesn't, then something is wrong with your terminfo library or
 your termcap file, or your terminal emulator is lying.
 needs new options or resources.

perhaps. i do this in particular for cygwin terminal type,
since that's the type you get if you try to ssh (using ssh
that comes with cygwin) from win2k shell prompt.

denis

-- 
// mailto: Denis Perelyubskiy [EMAIL PROTECTED]
// icq   : 12359698
// PGP   : http://www.cs.ucla.edu/~denisp/files/pgp.asc

Re: Color


On Thu, Sep 06, 2001 at 04:56:58PM -0500, David Champion wrote:
 That said, I occasionally change my $TERM from xterm to something I
 like, just to get rid of the alternate (application-mode?) screen
 setting. But there are better ways of doing this (xterm -ti vt100, or
 modifying a private copy in $TERMINFO); I'm just lazy.

or better yet, it's a popup entry in XFree86 xterm.
I set my $TERM manually for one of these reasons:

a) the actual $TERM isn't propagated to the shell from where I'm
   logged in.

b) to work around broken applications/libraries that can't handle
   the terminfo.

c) testing...
 
-- 
Thomas E. Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net

Sort reverse-thread but within thread by date?

2001-09-06 Thread Graham Williams


I'm playing around with sort= and sort_aux= trying to sort by
reverse-thread and then to sort within a thread by date.  I've tried
various combinations to no avail so far. Usually within the thread the
messages also come out in reverse order of date.  Any hints?

Regards,
Graham

Re: Color


On Thu, Sep 06, 2001 at 06:07:20PM -0500, David Champion wrote:
 I see the Show Alternate Screen item, but that seems just to toggle
 whether I currently see the alternate screen. My problem is that with
 TERM=xterm, applications will use the alternate screen, then flip back
 when they suspend or terminate. I don't like that - I want applications
 and shell in the standard screen, with no automatic toggling of the
 alternate screen. Is there a way to force that without editing the
 terminfo or changing $TERM?

There's also Enable Alternate Screen Switching.  Just glancing at the
changelog, it appears I added that around patch #90.

  I set my $TERM manually for one of these reasons:
  
  a) the actual $TERM isn't propagated to the shell from where I'm
 logged in.
 
 Isn't that (arguably) a flaw in your communications application or
 protocol? I thought that all the standard daemons supported this --
 well, as of about 1991, anyway. I don't recall exactly when it showed up
 in telnetd.

sure - but in the cases where it breaks, it's usually on someone else's network
(I can't fix those ;-)
 
 
  b) to work around broken applications/libraries that can't handle
 the terminfo.
  
  c) testing...
 
 Which make sense, of course, but are more of a one-off event than
 something to keep in your .profile.
 
 -- 
  -D.  [EMAIL PROTECTED]NSITUniversity of Chicago

-- 
Thomas E. Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net

Re: Color

2001-09-06 Thread Tim Whitehead


I think you're confused as to what gkrellm is. The website is www.gkrellm.net

Essentially it's a system monitor that has the capability to check mail (as well
as a few other things), either locally or remotely. In my case I have it call
'fetchmail' every 10 minutes. It checks my local mailbox every 5 seconds for new
mail. When there's mail I have the option of calling a mail reader. So I pop up
an Eterm and run mutt.  

Thus, there would not be a TERM=gkrellm; it doesn't make sense. 


tw


Le jour Thu Sep 06, 2001 at 01:55:34PM -0700, Denis Perelyubskiy ([EMAIL PROTECTED]) 
a écrit...

  * Tim Whitehead [EMAIL PROTECTED] [09-Thu-01 10:18 -0700]:
  
  I think that the problem is in my /etc/profile 
  
  if [ $COLORTERM = Eterm ]; then
  TERM=xterm-color
  else
  TERM=linux
  fi
  
  This may be what is throwing off the TERM var. Because
  when I comment out the wait line, mutt comes up in mono
  again. 
  
  any suggestions?
 
 maybe something along the lines of 
 
 if [ $COLORTERM = Eterm ]; then
   TERM=xterm-color
 elif [ $TERM = gkrellm ]; then
   TERM=xterm-color
 else
   TERM=linux
 fi
 
 i am not too good with bash in general. i just go try to
 figure out things i need wheni need them :)
 
 also, check what $TERM var says when you log in using your
 gkrellm. that test in 'elif' may need to be modified if TERM
 is not gkrellm
 
 also, neither do i know if this is an *official* bash way,
 but things like these work in my startup files, even though
 maybe they disgust people who really know bash :)
 
 denis
 
 -- 
 // mailto: Denis Perelyubskiy [EMAIL PROTECTED]
 // icq   : 12359698
 // PGP   : http://www.cs.ucla.edu/~denisp/files/pgp.asc

-- 
Timothy Mark Whitehead  // Sophomore, UW - Madison  
tmwhitehead(at)students.wisc.edu// Intended Major: Computer Engineering 
tigmoid(at)146.151.75.25// SUPPORT YOUR LOCAL COLLEGE STUDENT!! 
whitehea(at)cs.wisc.edu // -- UW-Navs, UW-Band, UW-Trumpet
tigmoid(at)jps.net  // Do you, eh, look at headers? 
public static String sig(String sig) { if(sig.equals(this.sig))sig = sig(sig); }

Re: Color


ok, my mistake. i thought it was a type of an xterm. clearly
that was wrong :)

denis
 
 * Tim Whitehead [EMAIL PROTECTED] [09-Thu-01 16:47 -0700]:
 
 I think you're confused as to what gkrellm is. The website is www.gkrellm.net
 
 Essentially it's a system monitor that has the capability to check mail (as well
 as a few other things), either locally or remotely. In my case I have it call
 'fetchmail' every 10 minutes. It checks my local mailbox every 5 seconds for new
 mail. When there's mail I have the option of calling a mail reader. So I pop up
 an Eterm and run mutt.  
 
 Thus, there would not be a TERM=gkrellm; it doesn't make sense. 
 
 
 tw
 
 
 Le jour Thu Sep 06, 2001 at 01:55:34PM -0700, Denis Perelyubskiy ([EMAIL PROTECTED]) 
 a écrit...
 
   * Tim Whitehead [EMAIL PROTECTED] [09-Thu-01 10:18 -0700]:
   
   I think that the problem is in my /etc/profile 
   
   if [ $COLORTERM = Eterm ]; then
   TERM=xterm-color
   else
   TERM=linux
   fi
   
   This may be what is throwing off the TERM var. Because
   when I comment out the wait line, mutt comes up in mono
   again. 
   
   any suggestions?
  
  maybe something along the lines of 
  
  if [ $COLORTERM = Eterm ]; then
TERM=xterm-color
  elif [ $TERM = gkrellm ]; then
TERM=xterm-color
  else
TERM=linux
  fi
  
  i am not too good with bash in general. i just go try to
  figure out things i need wheni need them :)
  
  also, check what $TERM var says when you log in using your
  gkrellm. that test in 'elif' may need to be modified if TERM
  is not gkrellm
  
  also, neither do i know if this is an *official* bash way,
  but things like these work in my startup files, even though
  maybe they disgust people who really know bash :)
  
  denis
  
  -- 
  // mailto: Denis Perelyubskiy [EMAIL PROTECTED]
  // icq   : 12359698
  // PGP   : http://www.cs.ucla.edu/~denisp/files/pgp.asc
 
 -- 
 Timothy Mark Whitehead// Sophomore, UW - Madison  
 tmwhitehead(at)students.wisc.edu  // Intended Major: Computer Engineering 
 tigmoid(at)146.151.75.25  // SUPPORT YOUR LOCAL COLLEGE STUDENT!! 
 whitehea(at)cs.wisc.edu   // -- UW-Navs, UW-Band, UW-Trumpet
 tigmoid(at)jps.net// Do you, eh, look at headers? 
 public static String sig(String sig) { if(sig.equals(this.sig))sig = sig(sig); }

denis

-- 
// mailto: Denis Perelyubskiy [EMAIL PROTECTED]
// icq   : 12359698
// PGP   : http://www.cs.ucla.edu/~denisp/files/pgp.asc

Re: Color

2001-09-06 Thread David Champion


On 2001.09.06, in [EMAIL PROTECTED],
Thomas Dickey [EMAIL PROTECTED] wrote:
 
 There's also Enable Alternate Screen Switching.  Just glancing at the
 changelog, it appears I added that around patch #90.

Hmm, I'm using patch 150, but I don't see that in my menu. I did find
the titeInhibit resource, though: good enough for me.


 sure - but in the cases where it breaks, it's usually on someone else's network
 (I can't fix those ;-)

OK, fair enough. I get a warped viewpoint from owning all the systems
I have user rights on. :)

-- 
 -D.[EMAIL PROTECTED]NSITUniversity of Chicago

Re: Archivation through mutt?

2001-09-06 Thread Piet Delport



--M9NhX3UHpAaciwkO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, 05 Sep 2001 at 14:39:40 -0400, Matej Cepl wrote:
[...mail archival script...]
=20
 However, I am really not a programmer and I am still slightly scare of
 Bash. Could you comment, please, on the attached script and tell me
 whether I am to shoot off my foot with this script?

Some quick comments:

- The ${foo} syntax expands to the contents of variable foo, not to
  the output of command foo.  For command substitution, either use
  $(foo), or `foo` (note the backticks).  The $(foo) form nests easier
  than the `foo` form, but the latter is more common between shells.

- In your -e strings for mutt, you must remember to insert the enter
  keypress after commands like tag-message, as mutt doesn't do it
  for you.  enter won't do though, you either need a \n or a
  literal carriage return (which can be gotten in vi by pressing ^V followed
  by ^M, for example).

- You also need to surround push's arguments with quotes of some kind,
  otherwise it complains about having too many arguments.

- Unless this is really what you intended, you probably want to add a
  quit to the end of each -e string, otherwise mutt will wait
  interactively for you to quit each time.

- ... and, a minor quibble, it's a good idea to use tag-prefix in
  place of ;, in case you ever decide to remap ;.

- For find, you should escape the parentheses to prevent the shell from
  interpreting them.  Also, it's safer to quote the
-name sent-*
  bit as
-name 'sent-*'
  just in case your current directory happens to contain a file starting
  with sent-.

Portability issues:

- Declare functions without the leading function, as the latter is a
  bash thing.

- For find, instead of -not, use !.  And, like the parens, it's best
  to escape this too.

Then, about the find statement in the script...

Currently, you have:

 find $MAILDIR/ \
  -not ( -name sent-* -o -name trash -o -name draft ) \
  -printf %P\n | xargs process

where process is a shell function that takes care of archiving all old
mail in the folder named by its first argument ($1).

The find statement will fail to work for two reasons:

1.  xargs foo takes its input and gives *all of them at once* as
arguments for foo.  So process would only ever affect the first
folder found, the rest would be ignored.
2.  xargs will never even find process in the first place, as it's a
shell function.  It can only see and call `real' programs.

To get around this, you can do something like the following (sorry for
the long line):

find $MAILDIR/ \
\! \( -name 'sent-*' -o -name trash -o -name draft \) \
-exec mutt -f {} \
  -e 'push tag-message~d -'`date --date=3D$ARCHDATE '+%d/%m/%Y'`=0D=
tag-prefixsave-message{}=0Dquit\ \;
   =20
Don't panic. :-) Basically, this does the find, and just directly
executes mutt on each of the matching folders.

I've attached my version of your script with all of the above worked in.
Warning: it's still totally untested.  Comments welcome.

[ One minor problem so far is that the FreeBSD date(1) doesn't
understand the --date option, but has a -v option rather, with:
-v -3m
meaning 3 months ago, and
-v +7d
meaning 7 days from now, etc.  Does GNU date(1) support the -v option? ]

--=20
Piet Delport [EMAIL PROTECTED]
Today's subliminal thought is:

--M9NhX3UHpAaciwkO
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE7mBMYzRUP82sZFCcRAktzAKClfCT7VwcBMjqTY8jprNK3xKoRgQCeOVIx
oBNzxtYl8c0Go51IZExr6rQ=
=5pLQ
-END PGP SIGNATURE-

--M9NhX3UHpAaciwkO--

Re: Color