unsubscribe [EMAIL PROTECTED]
unsubscribe [EMAIL PROTECTED]

mutt-users-digest wrote:
> 
> mutt-users-digest     Thursday, December 20 2001     Volume 01 : Number 899
> 
> Today's Topics:
> 
>     Re: Sending multipart/alternative attachments
>     Re: Sending multipart/alternative attachments
>     Re: Sending multipart/alternative attachments
>     Re: Sending multipart/alternative attachments
>     national chars in subject
>     Re: Quoting when replying
>     Re: Quoting when replying
>     Re: process substitution (was: Re: Searching big gobs of e-mail)
>     Re: problems with non a-z chars and my_hdr (1.3.24i)
>     Re: national chars in subject
>     Re: Quoting when replying
>     Charset problem
>     Re: Charset problem
>     Re: Charset problem
>     Re: filters
>     Re: Charset problem
>     Re: Charset problem
>     Re: Quoting when replying
>     html mails and mutt (was: utf-8 display problem index vs. pager)
>     Re: html mails and mutt (was: utf-8 display problem index vs. pager)
>     Re: Changing file browser settings for Mail folder
>     Problems installing MUTT
>     Re: Problems installing MUTT
>     Re: Charset problem
> 
> ----------------------------------------------------------------------
> 
> Date: Wed, 19 Dec 2001 11:55:31 -0800
> From: Gary Johnson <[EMAIL PROTECTED]>
> Subject: Re: Sending multipart/alternative attachments
> 
> On Wed, Dec 19, 2001 at 11:21:00AM -0800, Will Yardley wrote:
> > well in the compose screen, you can attach as many documents as you
> > like, and they'll show up as MIME multipart.  so compose your message,
> > then exit the editor and hit 'a' to attach the first document, rinse,
> > lather, repeat.
> >
> > that should do what you want, no?
> That will give me multiple attachments, which may be good enough, but I
> was hoping to use the "alternative" tag to allow each recipient's MUA to
> display only one version of the attachment, the one with the user's
> preferred Content-Type.  I was also hoping this would cue the recipients
> that there really is only one form they need to fill out, without me
> having to spell it out in the cover letter.  On the other hand, maybe
> giving them an explicit choice of formats would be better.
> Gary
> - --
> Gary Johnson                               | Agilent Technologies
> [EMAIL PROTECTED]                   | Spokane, Washington, USA
> http://www.spocom.com/users/gjohnson/mutt/ |
> 
> ------------------------------
> 
> Date: Wed, 19 Dec 2001 19:59:23 +0000
> From: Thomas Hurst <[EMAIL PROTECTED]>
> Subject: Re: Sending multipart/alternative attachments
> 
> Ooops, proof that that X-Uptime header's not entirely useless.  Just
> noticed I had a locked-up proftpd process that's been there for the last
> 4 hours :)
> * Gary Johnson ([EMAIL PROTECTED]) wrote:
> > I've RTFM and haven't seen a way for mutt to send (not display)
> > multipart/alternative attachments.  Is there an external program that
> > can be used with mutt to do this?  I was considering using an existing
> > message as a template, but I thought I read where the boundary string
> > has to be unique and I'd rather not have to guess at a unique sequence
> > and edit the boundary manually.  Besides, it would be much easier to
> > have the attachments assembled automatically and after all, that's
> > what computers are for.
> Have mutt generate the MIME stuff, then post-filter the message to alter
> the headers to make it mutlipart/alternative?
> It should be specified in an rfc anyway; good idea to read that if you
> can't have something else generate it for you.
> - --
> Thomas 'Freaky' Hurst  -  [EMAIL PROTECTED]  -  http://www.aagh.net/
> 
> ------------------------------
> 
> Date: Wed, 19 Dec 2001 20:02:03 +0000
> From: Thomas Hurst <[EMAIL PROTECTED]>
> Subject: Re: Sending multipart/alternative attachments
> 
> * Gary Johnson ([EMAIL PROTECTED]) wrote:
> > On the other hand, maybe giving them an explicit choice of formats
> > would be better.
> Personally I'd multipart/alternate the Word version so even if word
> breaks they can still read the message, and give a choice of not
> including the word version at signup.  Same with HTML; I may well be
> able to read HTML messages, but if lynx breaks I'd still like to be able
> to read it, if only to find how to change it :)
> - --
> Thomas 'Freaky' Hurst  -  [EMAIL PROTECTED]  -  http://www.aagh.net/
> 
> ------------------------------
> 
> Date: Wed, 19 Dec 2001 12:12:54 -0800
> From: Gary Johnson <[EMAIL PROTECTED]>
> Subject: Re: Sending multipart/alternative attachments
> 
> On Wed, Dec 19, 2001 at 08:02:03PM +0000, Thomas Hurst wrote:
> > * Gary Johnson ([EMAIL PROTECTED]) wrote:
> >
> > > On the other hand, maybe giving them an explicit choice of formats
> > > would be better.
> >
> > Personally I'd multipart/alternate the Word version so even if word
> > breaks they can still read the message, and give a choice of not
> > including the word version at signup.  Same with HTML; I may well be
> > able to read HTML messages, but if lynx breaks I'd still like to be able
> > to read it, if only to find how to change it :)
> What I meant was that maybe I should send the attachments to everyone as
> multipart/mixed so that they would see two attachments, form.doc and
> form.txt, and could decide when they respond which version they want to
> fill out.  I would prefer not to keep track of which recipients prefer
> which version, but I suppose that really wouldn't be that much extra
> work.
> Gary
> - --
> Gary Johnson                               | Agilent Technologies
> [EMAIL PROTECTED]                   | Spokane, Washington, USA
> http://www.spocom.com/users/gjohnson/mutt/ |
> 
> ------------------------------
> 
> Date: Wed, 19 Dec 2001 23:13:03 +0200
> From: Paulius Bulotas <[EMAIL PROTECTED]>
> Subject: national chars in subject
> 
> Hello,
> today I installed my locale and I'm trying to get mutt to work with
> it... but ;) there is one problem - I could not use national chars in
> subject (To and so on), because instead of them mutt produces other ascii
> chars (I could not type them).
> My OS is FreeBSD 4.4-Release, mutt 1.3.24i compile options are:
> System: FreeBSD 4.4-RELEASE (i386) [using ncurses 5.1]
> Compile options:
> - -DOMAIN
> +DEBUG
> +HOMESPOOL  -USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE
> - -USE_FCNTL  +USE_FLOCK
> - -USE_POP  -USE_IMAP  -USE_GSS  -USE_SSL  -USE_SASL
> +HAVE_REGCOMP  -USE_GNU_REGEX
> +HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET
> +HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM
> +HAVE_PGP  -BUFFY_SIZE -EXACT_ADDRESS  -SUN_ATTACHMENT
> +ENABLE_NLS  +LOCALES_HACK  -HAVE_WC_FUNCS  -HAVE_LANGINFO_CODESET
> - -HAVE_LANGINFO_YESEXPR
> +HAVE_ICONV  -ICONV_NONTRANS  +HAVE_GETSID  -HAVE_GETADDRINFO
> TIA
> Regards,
> Paulius
> 
> ------------------------------
> 
> Date: Wed, 19 Dec 2001 09:13:38 +0100
> From: Thorsten Haude <[EMAIL PROTECTED]>
> Subject: Re: Quoting when replying
> 
> Hi,
> * David T-G <[EMAIL PROTECTED]> [01-12-18 13:32]:
> >Hey, he said it happenned with Crosspoint, and I'd never heard of it
> >until we traded some email recently.  If something of which I've never
> >heard can do that, surely something of which I have might have the same
> >shot!
> Wrong network, wrong country, wrong OS, wrong decade.
> Crosspoint was successful with BBS nets in Germany and it run on DOS.
> Thorsten
> - --
> The history of Liberty is a history of the limitation of government power.
>         - Woodrow Wilson
> 
> ------------------------------
> 
> Date: Wed, 19 Dec 2001 09:08:42 +0100
> From: Thorsten Haude <[EMAIL PROTECTED]>
> Subject: Re: Quoting when replying
> 
> Hi,
> * Rob 'Feztaa' Park <[EMAIL PROTECTED]> [01-12-18 00:02]:
> >It's a quote string! Get over it!
> My thoughts exactly.
> Thorsten
> - --
> Question Authority!
> 
> ------------------------------
> 
> Date: Wed, 19 Dec 2001 17:38:28 -0800
> From: Vineet Kumar <[EMAIL PROTECTED]>
> Subject: Re: process substitution (was: Re: Searching big gobs of e-mail)
> 
> - --HlL+5n6rz5pIUxbD
> Content-Type: text/plain; charset=unknown-8bit
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> 
> * Gregor Zattler ([EMAIL PROTECTED]) [011218 03:44]:
> > Hi Peter,
> > hi mutt users,
> > * Peter Poeml <[EMAIL PROTECTED]> [Mon 10 Dez 2001 20:04:17 GMT]:
> > [...]
> > > As mentioned before, grepmail can jump in because mutt works on single
> > > mail boxes. Now I was curious and figured out the command for your real
> > > example:
> > >=20
> > > mutt -f <(grepmail -huqd "between 2001-09-01 and 2001-10-01" \
> > >     "^From.*frob@(foo|bar).net" mbox1 mbox2 mbox3)
> >=20
> > This seems cool but when i gave it a (much more simppler) try:
> >=20
> > mutt -f <(grepmail -h cco@ *)
> >=20
> > i see mutt reading messages from "/dev/fd/63", a few messages from
> > grepmaiol and then:=20
> >=20
> > the mutt index which first looks fine but when I hit <enter> to read a
> > message the pager was empty...
> >=20
> > also=20
> >=20
> > ae <(ls)
> > emacs <(ls)
> > jed <(ls)
> >=20
> > did not work.
> >=20
> >=20
> > Any hints?
> 
> Well, it won't help the bash-users out there, but anyone willing to give
> zsh a try will benefit from this excerpt from the Process substitution
> of the zshexpn manpage:
> 
>            Both  the  /dev/fd  and the named pipe implementation have
>            drawbacks.  In the former case, some programmes may automatically
>            close the file descriptor in question before examining the file
>            on the  command line, particularly if this is necessary for
>            security reasons such as when the pro=AD gramme is running setuid.
>            In the second case, if the programme  does  not  actually  open
>            the file,  the subshell attempting to read from or write to the
>            pipe will (in a typical implementa=AD tion, different operating
>            systems may have different behaviour) block for ever and have  to
>            be killed explicitly.  In both cases, the shell actually supplies
>            the information using a pipe, so that programmes that expect to
>            lseek (see lseek(2)) on the file will not work.
> 
> =2E..
> 
>            If =3D is used, then the file passed as an argument will be the
>            name of a temporary file contain=AD ing  the output of the list
>            process.  This may be used instead of the < form for a program
>            that expects to lseek (see lseek(2)) on the input file.
> 
> So this works for me:
> 
> mutt -f =3D(mboxgrep -mmaildir '^From:.*callahan@homicide\.SFPD\.gov' $MAIL)
> 
> mboxgrep even adds the wicked ^From_  lines!
> Really, though, zsh effectively does the same thing as what grepm does,
> with the temp file.
> 
> Vineet
> 
> - --=20
> Satan laughs when      #  "I disapprove of what you say, but I will
> we kill each other.    #   defend to the death your right to say it."
> Peace is the only way. #  --Beatrice Hall, The Friends of Voltaire, 1906
> - --HlL+5n6rz5pIUxbD
> Content-Type: application/pgp-signature
> Content-Disposition: inline
> 
> - -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iEYEARECAAYFAjwhQRQACgkQ7z3S33fUb9E2lwCfafgXGRb2aiYk6xm38/5haNS8
> w0sAoMZAl5SOfQOKXYhjzcL9FNzVsC5Q
> =a4oh
> - -----END PGP SIGNATURE-----
> 
> - --HlL+5n6rz5pIUxbD--
> 
> ------------------------------
> 
> Date: Thu, 20 Dec 2001 02:52:39 +0100
> From: Andreas Landmark <[EMAIL PROTECTED]>
> Subject: Re: problems with non a-z chars and my_hdr (1.3.24i)
> 
> On Wed, Dec 19, 2001 at 03:44:27PM +0100, Vincent Lefevre wrote:
> >
> > So, perhaps you should quote the name:
> >
> > my_hdr From: "Christian Kjønsvik" <[EMAIL PROTECTED]>
> >
> > (I haven't tried and don't know if this works.)
> It doesn't, same result, the From-field is perverted in a slightly
> different way, it doesn't split it as before, but it still appends the
> real hostname twice (which it doesn't if you remove the ø).
> I told the user to change his name, and luckily for me he didn't
> complain (so from now on, he's known as Kjonsvik ;-).
> I'll do some more research later on and submit something through flea or
> actually take the time to workout the patch myself (if the rush before
> xmas allows me...)
> - --
> Andreas D Landmark / noXtension
> "Our vision is to speed up time, eventually eliminating it."
>                 -- Alex Schure
> 
> ------------------------------
> 
> Date: Thu, 20 Dec 2001 02:57:28 +0100
> From: Andreas Landmark <[EMAIL PROTECTED]>
> Subject: Re: national chars in subject
> 
> On Wed, Dec 19, 2001 at 11:13:03PM +0200, Paulius Bulotas wrote:
> > Hello,
> >
> > today I installed my locale and I'm trying to get mutt to work with
> > it... but ;) there is one problem - I could not use national chars in
> > subject (To and so on), because instead of them mutt produces other ascii
> > chars (I could not type them).
> >
> <snip-system-config>
> What's your locale in the spawning shell?
> (try export LC_ALL=XX where XX is your countrycode, you might want to
> finegrain which locale-variable you set as you might not want your shell
> to be translated aswell (and all the other locale-supporting applics).
> - --
> Andreas D Landmark / noXtension
> Try to get all of your posthumous medals in advance.
> 
> ------------------------------
> 
> Date: Wed, 19 Dec 2001 19:18:22 -0700
> From: Rob 'Feztaa' Park <[EMAIL PROTECTED]>
> Subject: Re: Quoting when replying
> 
> - --gKMricLos+KVdGMg
> Content-Type: text/plain; charset=iso-8859-1
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> 
> On Wed, Dec 19, 2001 at 08:49:47AM +0100, Thorsten Haude (dis)graced my inb=
> ox with:
> > defeat the very purpose of the quote signs. Wenn ich auf einmal die
> > Sprache wecheln w=FCrde, nur damit es f=FCr *mich* klarer ist was ich
> > schreibe, h=E4tten die meisten anderen ebenfalls nichts davon.
> 
> I'm a little rusty on my german, but I think this means:
> 
> If I decide to speak a different language, it is only clearer for *me*
> to write, but it screws everything up for everybody else.
> 
> I know that's not _quite_ right, but I'm too lazy to get out my
> dictionary :)
> 
> > Thorsten
> > --=20
> > Intolerant people should be shot.
> 
> Too ironic!! We have to shoot you now, Thorsten :)
> 
> - --=20
> Rob 'Feztaa' Park
> [EMAIL PROTECTED]
> - --
> "I chased a girl for two years only to discover that her tastes=20
> were exactly like mine: We were both crazy about girls."
>                 -- Groucho Marx
> 
> - --gKMricLos+KVdGMg
> Content-Type: application/pgp-signature
> Content-Disposition: inline
> 
> - -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iD8DBQE8IUptPTh2iSBKeccRAluAAJ9qsF54zTDYh/Asi2Zxy+9tTXvGbQCeKYLg
> 1W/46dDB408rEukE5PsDz98=
> =Id+P
> - -----END PGP SIGNATURE-----
> 
> - --gKMricLos+KVdGMg--
> 
> ------------------------------
> 
> Date: Wed, 19 Dec 2001 19:25:01 -0700
> From: Rob 'Feztaa' Park <[EMAIL PROTECTED]>
> Subject: Charset problem
> 
> - --+QahgC5+KEYLbs62
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> 
> Hello all, I'm having a problem with my charset in mutt 1.3.24 on Debian
> Woody.
> 
> I've set my charset to iso-8859-1, but many characters display as a ?. I
> had a similar problem on mandrake, but I fixed it by setting the charset
> to what it is now. It's no longer working.
> 
> Any suggestions?
> 
> - --=20
> Rob 'Feztaa' Park
> [EMAIL PROTECTED]
> - --
> "In short, just as the Multics mentality of careful access controls shows
> up throughout Unix, the cretinous CP/M mentality of uncontrolled havoc shows
> up in DOS and all it's mutant children."
>                 -- Tom Christiansen
> 
> - --+QahgC5+KEYLbs62
> Content-Type: application/pgp-signature
> Content-Disposition: inline
> 
> - -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iD8DBQE8IUv9PTh2iSBKeccRAiEcAJ9hyjeoUtPs+4qJwuCvQkphPqBnhwCeIDS+
> FtpHjGAufMBeAEUpvWCKD+8=
> =ZP0I
> - -----END PGP SIGNATURE-----
> 
> - --+QahgC5+KEYLbs62--
> 
> ------------------------------
> 
> Date: Wed, 19 Dec 2001 21:39:32 -0500
> From: Brian Clark <[EMAIL PROTECTED]>
> Subject: Re: Charset problem
> 
> Hi Rob,
> * Rob 'Feztaa' Park ([EMAIL PROTECTED]) [Dec 19. 2001 21:25]:
> > Hello all, I'm having a problem with my charset in mutt 1.3.24 on Debian
> > Woody.
> Using woody, too. Make sure you have the locales package installed.
> > I've set my charset to iso-8859-1, but many characters display as a ?. I
> > had a similar problem on mandrake, but I fixed it by setting the charset
> > to what it is now. It's no longer working.
> I fixed this problem by setting my locales (LC_*) in my shell's rc
> file(s), then adding that information to /etc/environment. I would get
> the ?'s if I started an `aterm -e mutt' from a bbkeys key binding, but I
> didn't get the ?' if I started an xterm, then manually typed in `mutt'
> Also, you might have to:
> cd /usr/lib/locale
> then run:
> localedef -c -i en_US -f ISO-8859-1 en_US
> (or whatever..)
> And of course set up your LC_* environment in your shell rc file and
> /etc/environment.
> Mine looks like:
> (~)% locale
> LANG=en_US
> LC_CTYPE="en_US"
> LC_NUMERIC="en_US"
> LC_TIME="en_US"
> LC_COLLATE="en_US"
> LC_MONETARY="en_US"
> LC_MESSAGES="en_US"
> LC_PAPER="en_US"
> LC_NAME="en_US"
> LC_ADDRESS="en_US"
> LC_TELEPHONE="en_US"
> LC_MEASUREMENT="en_US"
> LC_IDENTIFICATION="en_US"
> LC_ALL=en_US
> > Any suggestions?
> I'm no expert, by any means, but that solved my problem. If that doesn't
> work, email me off list and we'll try to figure it out -- unless of course
> another Debian user on this list knows more about locales.
> - --
> Brian Clark | Avoiding the general public since 1805!
> Fingerprint: 07CE FA37 8DF6 A109 8119 076B B5A2 E5FB E4D0 C7C8
> Imminent Death of the Net Predicted. GIFs at 11.
> 
> ------------------------------
> 
> Date: Wed, 19 Dec 2001 21:16:36 -0700
> From: Rob 'Feztaa' Park <[EMAIL PROTECTED]>
> Subject: Re: Charset problem
> 
> - --FkmkrVfFsRoUs1wW
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> 
> On Wed, Dec 19, 2001 at 09:39:32PM -0500, Brian Clark (dis)graced my inbox =
> with:
> > Hi Rob,
> 
> hello.
> 
> > > Hello all, I'm having a problem with my charset in mutt 1.3.24 on Debian
> > > Woody.
> >=20
> > Using woody, too. Make sure you have the locales package installed.
> 
> Which one? There are many, for different purposes. These ones might be
> relevant:
> 
> icu-locales 1.8.1-2 (not installed)
> locales 2.2.4-7 (installed)
> util-linux-locales 2.11n-2 (installed)
> 
> > > I've set my charset to iso-8859-1, but many characters display as a ?. I
> > > had a similar problem on mandrake, but I fixed it by setting the charset
> > > to what it is now. It's no longer working.
> >=20
> > I fixed this problem by setting my locales (LC_*) in my shell's rc
> > file(s), then adding that information to /etc/environment. I would get
>                                            ^^^^^^^^^^^^^^^^
> I don't have this file.
> 
> > the ?'s if I started an `aterm -e mutt' from a bbkeys key binding, but I
> > didn't get the ?' if I started an xterm, then manually typed in `mutt'
> >=20
> > Also, you might have to:
> >=20
> > cd /usr/lib/locale
> >=20
> > then run:
> >=20
> > localedef -c -i en_US -f ISO-8859-1 en_US
> >=20
> > (or whatever..)
> 
> Ok, did that.
> 
> Before I ran it, /usr/lib/locales was empty, now there's a
> /usr/lib/locales/en_US.
> 
> Does that mean I should configure all my LC_* variables to be "en_US"?
> 
> > And of course set up your LC_* environment in your shell rc file and
> > /etc/environment.
> >=20
> > Mine looks like:
> >=20
> > (~)% locale
> > LANG=3Den_US
> > LC_CTYPE=3D"en_US"
> > LC_NUMERIC=3D"en_US"
> =2E..
> > LC_ALL=3Den_US
> 
> Mines like this:
> 
> LANG=3DPOSIX
> LC_CTYPE=3D"POSIX"
> LC_NUMERIC=3D"POSIX"
> LC_TIME=3D"POSIX"
> LC_COLLATE=3D"POSIX"
> LC_MONETARY=3D"POSIX"
> LC_MESSAGES=3D"POSIX"
> LC_PAPER=3D"POSIX"
> LC_NAME=3D"POSIX"
> LC_ADDRESS=3D"POSIX"
> LC_TELEPHONE=3D"POSIX"
> LC_MEASUREMENT=3D"POSIX"
> LC_IDENTIFICATION=3D"POSIX"
> LC_ALL=3D
> 
> After I ran that other command, I just tested it and it isn't working.
> 
> Could you provide a little more details about where I configure those
> LC_* variables? Just in ~/.bashrc? or somewhere special?
> 
> - --=20
> Rob 'Feztaa' Park
> [EMAIL PROTECTED]
> - --
> "In Australia, not reading poetry is the national pastime."
>                 -- Phyllis McGinley
> 
> - --FkmkrVfFsRoUs1wW
> Content-Type: application/pgp-signature
> Content-Disposition: inline
> 
> - -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iD8DBQE8IWYkPTh2iSBKeccRAix2AJ4ypu4xr/OaZJlx9FIMEPv84X/7GwCeMivq
> DJA3QY55AZy6JIhl05wbFD8=
> =j0HI
> - -----END PGP SIGNATURE-----
> 
> - --FkmkrVfFsRoUs1wW--
> 
> ------------------------------
> 
> Date: Wed, 19 Dec 2001 22:46:17 +0530
> From: Prahlad Vaidyanathan <[EMAIL PROTECTED]>
> Subject: Re: filters
> 
> - --pWyiEgJYm5f9v55/
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> 
> Hi,
> 
> On Wed, 19 Dec 2001 giorgian spewed into the ether:
> > hi all,
> > i have been using mutt for three days, and there are tons of things i
> > haven't figured out yet.
> >=20
> > i haven't found anything in the man pages about mail filters;
> > initially i decided to try procmail, but it is decisely too much
> > insane for me: i'm a member of at least 15 MLs (plus this one :) ),
> > and my .procmailrc is an awful mess, so i gave up.
> 
> Check out :
> 
>     http://www.symonds.net/~prahladv/files/procmailrc
> 
> pv.
> 
> - --=20
> Regression analysis:
>         Mathematical techniques for trying to understand why things are
>         getting worse.
> - --=20
> 
> - --pWyiEgJYm5f9v55/
> Content-Type: application/pgp-signature
> Content-Disposition: inline
> 
> - -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.4 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iD8DBQE8IMthIKhjOSElu4YRAo2aAKChyDCTDpOJ2w1wGGwAsdiKwvVoPgCeKjlS
> EwM7gSmD4lBknKxKl5l9PxA=
> =8WA3
> - -----END PGP SIGNATURE-----
> 
> - --pWyiEgJYm5f9v55/--
> 
> ------------------------------
> 
> Date: Wed, 19 Dec 2001 23:33:31 -0500
> From: Brian Clark <[EMAIL PROTECTED]>
> Subject: Re: Charset problem
> 
> * Rob 'Feztaa' Park ([EMAIL PROTECTED]) [Dec 19. 2001 23:17]:
> > > Using woody, too. Make sure you have the locales package installed.
> > Which one? There are many, for different purposes. These ones might be
> > relevant:
> > icu-locales 1.8.1-2 (not installed)
> > locales 2.2.4-7 (installed)
> That one ^^ I think. That's what I have installed. I just did a
> `dpkg-reconfigure locales' and chose my preference.
> [...]
> > > I fixed this problem by setting my locales (LC_*) in my shell's rc
> > > file(s), then adding that information to /etc/environment. I would get
> >                                            ^^^^^^^^^^^^^^^^
> > I don't have this file.
> Huh? Well it's there in a default setup in my woody. I have no idea
> what's going on there.
> [...]
> > > localedef -c -i en_US -f ISO-8859-1 en_US
> > > (or whatever..)
> > Ok, did that.
> > Before I ran it, /usr/lib/locales was empty, now there's a
> > /usr/lib/locales/en_US.
> > Does that mean I should configure all my LC_* variables to be "en_US"?
> Yep, that's what I meant by "or whatever" -- if you wanted something
> else other than en_US
> Just out of curiosity, do you have the file /usr/share/i18n/locales/en_US?
> [...]
> > Mines like this:
> > LANG=POSIX
> > LC_CTYPE="POSIX"
> > LC_NUMERIC="POSIX"
> > LC_TIME="POSIX"
> > LC_COLLATE="POSIX"
> > LC_MONETARY="POSIX"
> > LC_MESSAGES="POSIX"
> > LC_PAPER="POSIX"
> > LC_NAME="POSIX"
> > LC_ADDRESS="POSIX"
> > LC_TELEPHONE="POSIX"
> > LC_MEASUREMENT="POSIX"
> > LC_IDENTIFICATION="POSIX"
> > LC_ALL=
> > After I ran that other command, I just tested it and it isn't working.
> > Could you provide a little more details about where I configure those
> > LC_* variables? Just in ~/.bashrc? or somewhere special?
> Yeah I use bash, so I set my ~/.bashrc with the correct LC_* settings
> (you could set yours to en_US if that's what you wanted.)
> Set those in your ~/.bashrc, source your .bashrc (% . ~/.bashrc) then
> type in mutt and look at an email where you get the ? marks and see if
> it's "right." (open a shell and type in mutt manually to make sure it
> *is* working from there before you try it from a menu, key-binding, etc.)
> - --
> Brian Clark | Avoiding the general public since 1805!
> Fingerprint: 07CE FA37 8DF6 A109 8119 076B B5A2 E5FB E4D0 C7C8
> STATUS QUO is Latin for the mess we're in.
> 
> ------------------------------
> 
> Date: Wed, 19 Dec 2001 22:24:56 -0700
> From: Rob 'Feztaa' Park <[EMAIL PROTECTED]>
> Subject: Re: Charset problem
> 
> - --bg08WKrSYDhXBjb5
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> 
> On Wed, Dec 19, 2001 at 11:33:31PM -0500, Brian Clark (dis)graced my inbox =
> with:
> > > icu-locales 1.8.1-2 (not installed)
> > > locales 2.2.4-7 (installed)
> >=20
> > That one ^^ I think. That's what I have installed. I just did a
> > `dpkg-reconfigure locales' and chose my preference.
> 
> I figured that was the one, but wasn't sure.
> 
> I did the dpkg thing, and chose en_US ISO-8859-1. Still not working.
> 
> > > > I fixed this problem by setting my locales (LC_*) in my shell's rc
> > > > file(s), then adding that information to /etc/environment. I would get
> > >                                            ^^^^^^^^^^^^^^^^
> > > I don't have this file.
> >=20
> > Huh? Well it's there in a default setup in my woody. I have no idea
> > what's going on there.=20
> 
> Me either.
> 
> > > > localedef -c -i en_US -f ISO-8859-1 en_US
> >=20
> > > > (or whatever..)
> >=20
> > > Ok, did that.
> >=20
> > > Before I ran it, /usr/lib/locales was empty, now there's a
> > > /usr/lib/locales/en_US.
> >=20
> > > Does that mean I should configure all my LC_* variables to be "en_US"?
> >=20
> > Yep, that's what I meant by "or whatever" -- if you wanted something
> > else other than en_US
> 
> en_US is fine. I'm Canadian, but it's not like there's a difference that
> anybody cares about.
> 
> > Just out of curiosity, do you have the file /usr/share/i18n/locales/en_US?
> 
> Yup.
> 
> There's a ton of others in that folder, too.
> 
> > > After I ran that other command, I just tested it and it isn't working.
> >=20
> > > Could you provide a little more details about where I configure those
> > > LC_* variables? Just in ~/.bashrc? or somewhere special?
> >=20
> > Yeah I use bash, so I set my ~/.bashrc with the correct LC_* settings
> > (you could set yours to en_US if that's what you wanted.)
> 
> I set them in my ~/.bashrc file and it didn't change anything (yes, I
> sourced the config file. The "locale" command still shows the "POSIX"
> stuff.)
> 
> - --=20
> Rob 'Feztaa' Park
> [EMAIL PROTECTED]
> - --
> "When I was a kid I used to pray every night for a new=20
> bicycle. Then I realized that the Lord doesn't work that=20
> way, so I stole one and asked Him to forgive me."
>                 -- Emo Philips
> 
> - --bg08WKrSYDhXBjb5
> Content-Type: application/pgp-signature
> Content-Disposition: inline
> 
> - -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iD8DBQE8IXYoPTh2iSBKeccRAp1cAJ9moJQ/4vMCxgmYZw9AuhL+guJ4EgCcCESw
> qg9TKj8hCq4YLzAHDz+wfwQ=
> =UuYu
> - -----END PGP SIGNATURE-----
> 
> - --bg08WKrSYDhXBjb5--
> 
> ------------------------------
> 
> Date: Thu, 20 Dec 2001 09:17:39 +0100
> From: Thorsten Haude <[EMAIL PROTECTED]>
> Subject: Re: Quoting when replying
> 
> Moin,
> * Rob 'Feztaa' Park <[EMAIL PROTECTED]> [01-12-20 03:18]:
> >On Wed, Dec 19, 2001 at 08:49:47AM +0100, Thorsten Haude (dis)graced my inbox with:
> >> defeat the very purpose of the quote signs. Wenn ich auf einmal die
> >> Sprache wecheln würde, nur damit es für *mich* klarer ist was ich
> >> schreibe, hätten die meisten anderen ebenfalls nichts davon.
> >I'm a little rusty on my german, but I think this means:
> >
> >If I decide to speak a different language, it is only clearer for *me*
> >to write, but it screws everything up for everybody else.
> I'm not the only German on the list, so the purpose of this sentence
> was not to be *totally* obscure, just obscure enough for some.
> >> Intolerant people should be shot.
> >Too ironic!! We have to shoot you now, Thorsten :)
> So you noticed that some of my sigs are ambigious?
> Thorsten
> - --
> Fear leads to anger. Anger leads to hate. Hate leads to
> using Windows NT for mission-critical applications.
> 
> ------------------------------
> 
> Date: Thu, 20 Dec 2001 10:50:23 +0100
> From: Stephan Seitz <[EMAIL PROTECTED]>
> Subject: html mails and mutt (was: utf-8 display problem index vs. pager)
> 
> - --EVF5PPMfhYS0aIcm
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> 
> Hi!
> 
> On Tue, Dec 18, 2001 at 08:30:05PM +0530, Prahlad Vaidyanathan wrote
> > > PS: How do you call w3m to display html mails?=20
> > <mailcap>
> > text/html; w3m -T text/html %s
> > </mailcap>
> 
> Fine, this is working for html files very good, but the mutt pager
> deletes the HREF links, so you only see something like "click here for
> more information" but you can't "klick" or see the address.
> lynx produces footnotes for every HREF link, but it doesn't work well
> in an utf-8 environment.
> 
> Shade and sweet water!
> 
>         Stephan
> 
> - --=20
> | Stephan Seitz                   E-Mail: [EMAIL PROTECTED] |
> |          WWW: http://fsing.fs.uni-sb.de/~stse/            |
> | PGP Public Keys: http://fsing.fs.uni-sb.de/~stse/pgp.html |
> 
> - --EVF5PPMfhYS0aIcm
> Content-Type: application/pgp-signature
> Content-Disposition: inline
> 
> - -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: Weitere Infos: siehe http://www.gnupg.org
> 
> iEYEARECAAYFAjwhtF4ACgkQ0QHLTu/TGQFYowCePn9eo1tktOujwSu6gDqOhI0x
> mysAoJqGXfidF3283JURA/88yMiFqz9F
> =oWn0
> - -----END PGP SIGNATURE-----
> 
> - --EVF5PPMfhYS0aIcm--
> 
> ------------------------------
> 
> Date: Thu, 20 Dec 2001 05:38:18 -0500 (EST)
> From: "Thomas E. Dickey" <[EMAIL PROTECTED]>
> Subject: Re: html mails and mutt (was: utf-8 display problem index vs. pager)
> 
> On Thu, 20 Dec 2001, Stephan Seitz wrote:
> > lynx produces footnotes for every HREF link, but it doesn't work well
> > in an utf-8 environment.
> I ought to write a lynx faq... (the utf-8 stuff works well enough with
> current code compiled against libncursesw).
> - --
> T.E.Dickey <[EMAIL PROTECTED]>
> http://invisible-island.net
> ftp://invisible-island.net
> 
> ------------------------------
> 
> Date: Thu, 20 Dec 2001 13:28:01 +0100
> From: Balazs Javor <[EMAIL PROTECTED]>
> Subject: Re: Changing file browser settings for Mail folder
> 
> Hi,
> No, unfortunatelly not :(
> Balazs
> On Mon, Dec 17, 2001 at 03:30:16PM +0100, Roman Neuhauser wrote:
> >> Date: Wed, 12 Dec 2001 22:27:48 +0100
> >> From: Balazs Javor <[EMAIL PROTECTED]>
> >> To: MUTT Users <[EMAIL PROTECTED]>
> >> Subject: Changing file browser settings for Mail folder
> >>
> >> Hi,
> >>
> >> I was trying to change the folder_format for just my
> >> ~/Mail folder where I store my mailboxes.
> >
> >    Hi Balazs,
> >
> >    have you received a reply to your question off-list perhaps?
> >
> >--
> >FreeBSD 4.4-STABLE
> >3:28PM up 2:24, 7 users, load averages: 0.16, 0.07, 0.02
> >
> >
> >
> 
> ------------------------------
> 
> Date: Thu, 20 Dec 2001 09:39:59 -0400
> From: "Ivan Castillo Escobar" <[EMAIL PROTECTED]>
> Subject: Problems installing MUTT
> 
> Hi, I'm trying to install and configure MUTT 1.3.24 in Tru64UNIX 4.0F.
> I have the tar file, I did extract all files, but when I try to run (#
> configure ) command the system returns the following message:
> # ./configure
> configure: error: can not find sources in . or ..
> Somebody knows how to correct this problem???
> Please send any suggestions.
> Very thanks and regards,
>  =20
> Ivan Castillo Escobar
> Sistemas y Redes
> DIMA LTDA.
> Tel: 591-3-3525200 Ext:333
> Fax:591-3-3525220
>  =20
> 
> ------------------------------
> 
> Date: Thu, 20 Dec 2001 13:46:45 +0000
> From: Lars Hecking <[EMAIL PROTECTED]>
> Subject: Re: Problems installing MUTT
> 
> Ivan Castillo Escobar writes:
> > Hi, I'm trying to install and configure MUTT 1.3.24 in Tru64UNIX 4.0F.
> > I have the tar file, I did extract all files, but when I try to run (#
> > configure ) command the system returns the following message:
> > # ./configure
> > configure: error: can not find sources in . or ..
> >
> > Somebody knows how to correct this problem???
> 
>  No idea, but there is absolutely NO reason nor requirement to run
>  configure as root!
> 
> ------------------------------
> 
> Date: Thu, 20 Dec 2001 09:08:21 -0500
> From: Brian Clark <[EMAIL PROTECTED]>
> Subject: Re: Charset problem
> 
> * Rob 'Feztaa' Park ([EMAIL PROTECTED]) [Dec 20. 2001 00:25]:
> > > Just out of curiosity, do you have the file /usr/share/i18n/locales/en_US?
> > Yup.
> > There's a ton of others in that folder, too.
> Same here, but they didn't make any difference for me. Admittedly,
> before I started digging into the `?' problem, I didn't know anything
> about locales and I still don't.
> > > > After I ran that other command, I just tested it and it isn't working.
> > > > Could you provide a little more details about where I configure those
> > > > LC_* variables? Just in ~/.bashrc? or somewhere special?
> > > Yeah I use bash, so I set my ~/.bashrc with the correct LC_* settings
> > > (you could set yours to en_US if that's what you wanted.)
> > I set them in my ~/.bashrc file and it didn't change anything (yes, I
> > sourced the config file. The "locale" command still shows the "POSIX"
> > stuff.)
> Are you using `export' in your .bashrc? From bash(1):
> "Executed commands inherit the environment. The
>  export and declare -x commands allow parameters
>  and functions to be added to and deleted from
>  the environment."
> So this is what I have:
> export LANG="en_US"
> export LC_CTYPE="en_US"
> export LC_NUMERIC="en_US"
> export LC_TIME="en_US"
> export LC_COLLATE="en_US"
> export LC_MONETARY="en_US"
> export LC_MESSAGES="en_US"
> export LC_PAPER="en_US"
> export LC_NAME="en_US"
> export LC_ADDRESS="en_US"
> export LC_TELEPHONE="en_US"
> export LC_MEASUREMENT="en_US"
> export LC_IDENTIFICATION="en_US"
> export LC_ALL="en_US"
> - --
> Brian Clark | Avoiding the general public since 1805!
> Fingerprint: 07CE FA37 8DF6 A109 8119 076B B5A2 E5FB E4D0 C7C8
> Shopping increases the owezone.
> 
> ------------------------------
> 
> End of mutt-users-digest V1 #899
> ********************************
begin:vcard 
n:Mercado;Marjo
tel;pager:(415) 260-9431
tel;cell:(415) 260-9431
tel;fax:(650) 228-5001
tel;home:(415) 682-7892
tel;work:(650) 228-5225
x-mozilla-html:FALSE
url:http://www.turbolinux.com
org:Turbolinux, Inc.;R&D
version:2.1
email;internet:[EMAIL PROTECTED]
title:Sr. Director of Solutions and Support
adr;quoted-printable:;;8000 Marina Boulevard=0D=0ASuite 300		;Brisbane;CA;94005;U.S.A.
x-mozilla-cpt:;-26688
fn:Marjo F. Mercado
end:vcard


Reply via email to