On 2008-03-19, Kyle Wheeler <[EMAIL PROTECTED]> wrote:
> On Wednesday, March 19 at 05:08 PM, quoth Kyle Wheeler:
> > Eh? The new process remains in control of the terminal as long as it
> > wants (i.e. it can't give up control at any point). Here's the thing,
> > though: when you pipe a message t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 19 at 05:08 PM, quoth Kyle Wheeler:
> Eh? The new process remains in control of the terminal as long as it
> wants (i.e. it can't give up control at any point). Here's the thing,
> though: when you pipe a message to a script, you'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 19 at 02:22 PM, quoth Culley Harrelson:
> I am ready to tackle this problem but when you pipe a message to a
> script it looks like a new process is spawned and the new process
> can't remain in control of the terminal. Can anyon
On 19 Mar 2008 14:22 -0700, by [EMAIL PROTECTED] (Culley Harrelson):
> I am ready to tackle this problem but when you pipe a message to a
> script it looks like a new process is spawned and the new process
> can't remain in control of the terminal. Can anyone point me in the
> right direction to m
I would like to set customize mutt for my tech support email for my business.
I have a bunch of shell scripts that do things like looking up accounts,
changing account statuses, issuing refunds, looking up payments etc. In
general, the key used for looking up accounts is the email address (though
On 19.03.08 15:29:20, Chris G wrote:
> On Wed, Mar 19, 2008 at 03:14:43PM +, Michael Kjorling wrote:
> > On 19 Mar 2008 15:02 +, by [EMAIL PROTECTED] (Chris G):
> > > Does something, somewhere *guess* the character set from the stream of
> > > characters it sees?
> >
> > Mutt looks at the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 19 at 03:42 PM, quoth Chris G:
>> http://www.mutt.org/doc/devel/manual.html#send-charset
>
> On reading the manual I'm not sure I'm any the wiser, it says "Mutt
> will use the first character set into which the text can be converte
On Wed, Mar 19, 2008 at 10:51:55AM -0500, Kyle Wheeler wrote:
> On Wednesday, March 19 at 03:29 PM, quoth Chris G:
> >On Wed, Mar 19, 2008 at 03:14:43PM +, Michael Kjorling wrote:
> >> On 19 Mar 2008 15:02 +, by [EMAIL PROTECTED] (Chris G):
> >> > Does something, somewhere *guess* the chara
On 19.03.08 15:29:20, Chris G wrote:
> On Wed, Mar 19, 2008 at 03:14:43PM +, Michael Kjorling wrote:
> > On 19 Mar 2008 15:02 +, by [EMAIL PROTECTED] (Chris G):
> > > Does something, somewhere *guess* the character set from the stream of
> > > characters it sees?
> >
> > Mutt looks at the
On Wed, Mar 19, 2008 at 03:14:43PM +, Michael Kjorling wrote:
> On 19 Mar 2008 15:02 +, by [EMAIL PROTECTED] (Chris G):
> > Does something, somewhere *guess* the character set from the stream of
> > characters it sees?
>
> Mutt looks at the message and picks the first charset from
> $send_
On Wed, Mar 19 2008, Chris G wrote:
>
>
Only the subject line is wrong ;)
Peter
--
http://pmrb.free.fr/contact/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 19 at 03:29 PM, quoth Chris G:
>On Wed, Mar 19, 2008 at 03:14:43PM +, Michael Kjorling wrote:
>> On 19 Mar 2008 15:02 +, by [EMAIL PROTECTED] (Chris G):
>> > Does something, somewhere *guess* the character set from the strea
* Chris G <[EMAIL PROTECTED]> [03-19-08 11:37]:
> On Wed, Mar 19, 2008 at 11:09:46AM -0400, Patrick Shanahan wrote:
> > * Chris G <[EMAIL PROTECTED]> [03-19-08 11:07]:
> > >
> > >
> > >
> >
> > this one displays correctly,
> > Content-Type
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 19 at 03:15 PM, quoth Chris G:
> How does mutt set about deciding what charset header to add?
Like this: mutt assumes that the file output by your editor conforms
to $attach_charset. It then uses iconv to convert that character se
On Wed, Mar 19, 2008 at 03:14:43PM +, Michael Kjorling wrote:
> On 19 Mar 2008 15:02 +, by [EMAIL PROTECTED] (Chris G):
> > Does something, somewhere *guess* the character set from the stream of
> > characters it sees?
>
> Mutt looks at the message and picks the first charset from
> $send_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 19 at 03:02 PM, quoth Chris G:
> On Wed, Mar 19, 2008 at 02:57:19PM +, Chris G wrote:
>> If you look in the header of this message I *fear* you will see that
>> the charset is set to iso-8859-1. It's not my muttrc that's doing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 19 at 02:14 PM, quoth Chris G:
>Well I'm still not sure things are right, even after getting my
>editor to do (approximately) the right thing.
>
>Here are some incorrect pound signs:-
Those are all encoded as three bytes: 0xEF 0xB
On Wed, Mar 19, 2008 at 11:09:46AM -0400, Patrick Shanahan wrote:
> * Chris G <[EMAIL PROTECTED]> [03-19-08 11:07]:
> >
> >
> >
>
> this one displays correctly,
> Content-Type: text/plain; charset=iso-8859-1
>
Yes, it does for me too
On Wed, Mar 19, 2008 at 03:02:17PM +, Chris G wrote:
> Not even that, something has set the charset to us-ascii.
>
> Does something, somewhere *guess* the character set from the stream of
> characters it sees?
>From my muttrc (which comes from debian):
# Name: send_charset
# Type: string
# D
On 19 Mar 2008 15:04 +, by [EMAIL PROTECTED] (Chris G):
>
These came through correctly.
--
Michael Kjörling .. [EMAIL PROTECTED] .. http://michael.kjorling.se
* . No bird soars too high if he soars with his own wings . *
* ENCR
On 19 Mar 2008 15:02 +, by [EMAIL PROTECTED] (Chris G):
> Does something, somewhere *guess* the character set from the stream of
> characters it sees?
Mutt looks at the message and picks the first charset from
$send_charset that allows an exact encoding.
http://www.mutt.org/doc/devel/manual.h
On Wed, Mar 19, 2008 at 03:10:03PM +, Chris G wrote:
> On Wed, Mar 19, 2008 at 03:03:46PM +, Chris G wrote:
> > �
> >
> Well that's clever, the mystery charset adder has decided this is
> utf-8 even though the characters I entered were iso-8859-1 pounds!
>
On Wed, Mar 19, 2008 at 03:03:46PM +, Chris G wrote:
> �
>
Well that's clever, the mystery charset adder has decided this is
utf-8 even though the characters I entered were iso-8859-1 pounds!
Aarrgghh!! So when I compose a message with iso-8859-1 in it
(incor
* Chris G <[EMAIL PROTECTED]> [03-19-08 11:07]:
>
>
>
this one displays correctly,
Content-Type: text/plain; charset=iso-8859-1
--
Patrick Shanahan Plainfield, Indiana, USAHOG # US1244711
http://wahoo.no-ip.org
* Chris G <[EMAIL PROTECTED]> [03-19-08 11:04]:
> �
no change.
header reports: Content-Type: text/plain; charset=utf-8
--
Patrick Shanahan Plainfield, Indiana, USAHOG # US1244711
http://wahoo.no-ip.org Photo Album: http://wahoo.no-
--
Chris Green
�
--
Chris Green
On Wed, Mar 19, 2008 at 02:57:19PM +, Chris G wrote:
> If you look in the header of this message I *fear* you will see that
> the charset is set to iso-8859-1. It's not my muttrc that's doing
> that, so what is setting it to that, incorrectly! I suspect that it's
> probably this that is the f
If you look in the header of this message I *fear* you will see that
the charset is set to iso-8859-1. It's not my muttrc that's doing
that, so what is setting it to that, incorrectly! I suspect that it's
probably this that is the fundamental problem (apart from getting my
editor to enter the cor
On 19.03.08 14:37:58, Michael Kjorling wrote:
> On 19 Mar 2008 14:14 +, by [EMAIL PROTECTED] (Chris G):
> > Here are some incorrect pound signs:-
> >
> > ?�
>
> This shows up to me (on a thoroughly UTF-8 system) as 56 undisplayable
>
On Wed, Mar 19, 2008 at 10:34:36AM -0400, Patrick Shanahan wrote:
> * Chris G <[EMAIL PROTECTED]> [03-19-08 10:16]:
> > Well I'm still not sure things are right, even after getting my editor
> > to do (approximately) the right thing.
> >
> > Here are some incorrect pound signs:-
> >
> > �
On 19 Mar 2008 14:14 +, by [EMAIL PROTECTED] (Chris G):
> Here are some incorrect pound signs:-
>
> ?�
This shows up to me (on a thoroughly UTF-8 system) as 56 undisplayable
glyps, one question mark, and one more undisplayable glyph.
* Chris G <[EMAIL PROTECTED]> [03-19-08 10:16]:
> Well I'm still not sure things are right, even after getting my editor
> to do (approximately) the right thing.
>
> Here are some incorrect pound signs:-
>
> ?�
>
> Here are some correct
On Wed, Mar 19, 2008 at 09:47:41AM -0400, Ken Weingold wrote:
> On Wed, Mar 19, 2008, Chris G wrote:
> > Yes, that's it, *everything* was actually alright except my editor
> > wasn't entering UTF-8 pounds signs (etc.). The rest of the system
> > just did its best to work around the resulting confu
On Wed, Mar 19, 2008 at 08:47:51AM -0500, Kyle Wheeler wrote:
> On Wednesday, March 19 at 12:53 PM, quoth Chris G:
> > It seems to me that mutt is actually *encoding* the characters wrong
> > (or it's using a library that's doing that) as even if I save the
> > sentmail copy of a message with (fo
On Wed, Mar 19, 2008, Chris G wrote:
> Yes, that's it, *everything* was actually alright except my editor
> wasn't entering UTF-8 pounds signs (etc.). The rest of the system
> just did its best to work around the resulting confusion.
What editor are you using?
-Ken
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 19 at 12:53 PM, quoth Chris G:
> It seems to me that mutt is actually *encoding* the characters wrong
> (or it's using a library that's doing that) as even if I save the
> sentmail copy of a message with (for example) pounds signs
On Wed, Mar 19, 2008 at 01:10:29PM +, Chris G wrote:
> On Wed, Mar 19, 2008 at 01:54:15PM +0100, Peter Münster wrote:
> > On Wed, Mar 19 2008, Chris G wrote:
> >
> > > However I can't seem to get mutt set up correctly, if I enter symbols
> > > like GB pound signs or accented characters in an E
On Wed, Mar 19, 2008 at 01:54:15PM +0100, Peter Münster wrote:
> On Wed, Mar 19 2008, Chris G wrote:
>
> > However I can't seem to get mutt set up correctly, if I enter symbols
> > like GB pound signs or accented characters in an E-Mail then when I
> > view the E-Mail using mutt I see reverse vide
On Wed, Mar 19 2008, Chris G wrote:
> However I can't seem to get mutt set up correctly, if I enter symbols
> like GB pound signs or accented characters in an E-Mail then when I
> view the E-Mail using mutt I see reverse video ? instead of the
> correct characters.
Hello Chris,
Does the terminal
On Wed, Mar 19, 2008 at 12:13:39PM +, Chris G wrote:
> On Wed, Mar 19, 2008 at 11:03:14AM +, Michael Kjorling wrote:
> > On 19 Mar 2008 10:40 +, by [EMAIL PROTECTED] (Chris G):
> > > in mutt I have "set charset=utf-8".
> > >
> > > What am I doing wrong?
> >
> > There was a discussion
On Wed, Mar 19, 2008 at 11:03:14AM +, Michael Kjorling wrote:
> On 19 Mar 2008 10:40 +, by [EMAIL PROTECTED] (Chris G):
> > in mutt I have "set charset=utf-8".
> >
> > What am I doing wrong?
>
> There was a discussion about this just recently, starting with
> message-ID <[EMAIL PROTECTED]
On 19 Mar 2008 10:40 +, by [EMAIL PROTECTED] (Chris G):
> in mutt I have "set charset=utf-8".
>
> What am I doing wrong?
There was a discussion about this just recently, starting with
message-ID <[EMAIL PROTECTED]>. In short, first off, try
to avoid setting $charset and see what that does.
-
I am trying to move everthing I do to utf-8. Most things seem to be
working well, I can enter utf-8 characters using my editor and they
display correctly on all the systems I use (mostly Linux but a couple
of Solaris ones as well).
However I can't seem to get mutt set up correctly, if I enter sym
44 matches
Mail list logo
