headers
John Buttery | 1 Apr 2002 03:03
Picon

Re: John's sig

* David T-G <davidtg-muttusers <at> justpickone.org> [2002-03-28 06:47:02 -0500]:
>...and then Simon White said...
>% Are you on the way to fixing it, or do you need help? I'm starting to feel
>% sorry for your poor script, since I just got mine working OK...

  Yes, it's on its way sort of; I know what I did that broke it, and I
fixed it in a bunch of places but haven't gotten around to fixing the
last spot where it loops back to sig #1 after falling off the end of the
list of quotes.

>It's funny you should ask; I've been debating whether he's actually
>typing that or those are actual outputs from the script :-)
>
>*grin*

  muhahahahaaaaaaa

--

-- 
Hmmm...maybe I just replaced this one manually?
Permalink | Reply | 0 comments |
headers
John Buttery | 1 Apr 2002 03:25
Picon

Re: X-Mailer header

* Michael Tatge <Michael.Tatge <at> web.de> [2002-03-30 13:35:04 +0100]:
>NO. It's "> " Period. Please don't make a new OT thread out of this,
>especially you David. ;-)

  Well, I just did some googling and found a bunch of sites about quote
characters; none of my attempts at searching the RFCs turned up anything
useful, but I don't think I was using very good search terms.
  There doesn't seem to be an authoritative answer on this, despite what
one of the eminent presences on this list implied a while back (in private;
hence why I changed from "> " to ">" in the first place...).
  So, while I'm definitely interested in following the standards, there
doesn't seem to be one.  Eliminating the space saves data, but more
importantly it allows one more character to fit actual text into.
Couple this with the fact that I've never heard of a mailer that
triggered on "> " for a quote, but not ">", and I don't see a compelling
reason to switch back.  Feel free to point out the authoritative source
if there is one; I've changed my mutt settings plenty of times in
response to things people say here (most recently my attribution
string).

  By the way, Sven, you might want to check out this URL, I'm getting a
403 error:

http://www.math.fu-berlin.de/~guckes/message/editing.html

--

-- 
Hi David!  :)
Permalink | Reply | 6 comments |
headers
Thomas Hurst | 1 Apr 2002 03:52

Re: X-Mailer header

* John Buttery (john <at> io.com) wrote:

> * Michael Tatge <Michael.Tatge <at> web.de> [2002-03-30 13:35:04 +0100]:
> >NO. It's "> " Period. Please don't make a new OT thread out of this,
> >especially you David. ;-)

^ The problem with using just '>' is that the quote string merges with
the text and becomes difficult to disinguish, not only for users, but
for reflowing algorithms which often have to put up with crap like:

| %>>JF > Bla bla 

That space goes a long way to ease working out what's a >INITAL quote
and what's not.

If you want to turn:

> > > > > > Foo bar wibble

Into:

>>>>>> Foo bar wibble

Then that's fine (although I prefer the spaces; quotes rarely need to
nest deeply, and the space makes working out the depth easier), but
please don't say:

>>>>>>Foo bar wibble

is better because it saves a single character.  I personally find
(Continue reading)

Permalink | Reply | 2 comments |
headers
Sadiq Al-Lawatia | 1 Apr 2002 04:08
Picon
Favicon

"update encoding?"

Hello Everyone,

I have been using mutt for abour 4 years now. Very happy with it I
must say. Anyways, my system adminstrator had just updated mutt to
1.3.24i (2001-11-29) and since then, everytime I send a message either
a forward, reply or even a new message, I get the following message
when I hit send:
"~/Mail/tmp/mutt-csce-4803-30 [#1] modified. Update encoding?
([yes]/no): "

How can I get rid of it? Its annoying to hit 'y' everytime I want to
send an email, and besides, I do not see any difference in emails even
when I hit n!

Thanx for your help.

--Sadiq
Permalink | Reply | 8 comments |
headers
John Buttery | 1 Apr 2002 04:47
Picon

Re: X-Mailer header

* Thomas Hurst <tom.hurst <at> clara.net> [2002-04- 1 02:52:00 +0100]:
>* John Buttery (john <at> io.com) wrote:
>^ The problem with using just '>' is that the quote string merges with
>the text and becomes difficult to disinguish, not only for users, but
>for reflowing algorithms which often have to put up with crap like:
>
>| %>>JF > Bla bla 
>
>That space goes a long way to ease working out what's a >INITAL quote
>and what's not.

  Hmm.  That's a good point.  Not so much the human parseability angle,
but I suppose it would make things easier for the machine parsers.

>please don't say:
>
>>>>>>>Foo bar wibble
>
>is better because it saves a single character.  I personally find

  Well, of course it's better for that reason.  Sure it's a small
improvement, but some is better than none.  However, it's quite possible
that the reasons for doing it the other way outweigh the space savings.

>quoting without a space after the quote more irritating than any of the
>exotic quote strings I've come across, with the possible exception of:
>
>C=This is quoted text
>C=Bla bla bla
>C=
(Continue reading)

Permalink | Reply | 0 comments |
headers
Rob 'Feztaa' Park | 1 Apr 2002 09:53
Picon
Favicon

Re: OT: Re: X-Mailer header

Alas! Shawn McMahon spake thus:
> perl -e "fork while true"    :-)

Note to self: load averages in excess of 300 aren't healthy. ;)

--

-- 
Rob 'Feztaa' Park
feztaa <at> shaw.ca
--
The only time a dog gets complimented is when he doesn't do anything.
		-- C. Schulz
Permalink | Reply | 0 comments |
headers
Rob 'Feztaa' Park | 1 Apr 2002 10:03
Picon
Favicon

Re: X-Mailer header

Alas! John Buttery spake thus:
>   So, while I'm definitely interested in following the standards, there
> doesn't seem to be one. 

It's not a formal standard in any sense of the word "standard"; it's
more like a deeply rooted tradition that goes all the way back to the
early days of USENET (maybe even earlier). 

--

-- 
Rob 'Feztaa' Park
feztaa <at> shaw.ca
--
	"Then you admit confirming not denying you ever said that?"
	"NO! ... I mean Yes!  WHAT?"
	"I'll put `maybe.'"
		-- Bloom County
Permalink | Reply | 2 comments |
headers
David T-G | 1 Apr 2002 14:43

Re: X-Mailer header

Thomas, et al --

...and then Thomas Hurst said...
% 
...
% is better because it saves a single character.  I personally find
% quoting without a space after the quote more irritating than any of the
% exotic quote strings I've come across, with the possible exception of:
% 
% C=This is quoted text
% C=Bla bla bla
% C=
% C=Cookie to whoever works out what this brain dead quote string is
% C=supposed to represent.

Piece of cake; just set your $display_filter to your Fortran compiler :-)

:-D
--

-- 
David T-G                      * It's easier to fight for one's principles
(play) davidtg <at> justpickone.org * than to live up to them. -- fortune cookie
(work) davidtgwork <at> justpickone.org
http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
Permalink | Reply | 0 comments |
headers
David T-G | 1 Apr 2002 14:48

Re: "update encoding?"

Sadiq --

...and then Sadiq Al-Lawatia said...
% 
% Hello Everyone,

Hello!

% 
% I have been using mutt for abour 4 years now. Very happy with it I
% must say. Anyways, my system adminstrator had just updated mutt to
% 1.3.24i (2001-11-29) and since then, everytime I send a message either

I'm afraid I don't have an answer for your question, but I do have
a suggestion for your admin: go back and re-update to 1.3.28 (latest
development release and a 1.4 release candidate), since a security hole
was fixed with 1.3.27.

HTH & HAND

:-D
--

-- 
David T-G                      * It's easier to fight for one's principles
(play) davidtg <at> justpickone.org * than to live up to them. -- fortune cookie
(work) davidtgwork <at> justpickone.org
http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
Permalink | Reply | 0 comments |
headers
Shawn McMahon | 1 Apr 2002 16:22

Re: X-Mailer header

begin  quoting what Rob 'Feztaa' Park said on Mon, Apr 01, 2002 at 01:03:29AM -0700:
> 
> It's not a formal standard in any sense of the word "standard"; it's
> more like a deeply rooted tradition that goes all the way back to the
> early days of USENET (maybe even earlier). 

Goes back to FIDONET, too.
Permalink | Reply | 0 comments |

Gmane