* David T-G <[EMAIL PROTECTED]> [020313 12:24]:
> % > % David - I will you as as soon as use revert to standard
> % > Did you mean to say that you'd show
> % > me how or did you mean something else?
> % yes - "show" (it was missing).
> That's not the only thing that was missing;
> what's with the "use revert"?
indeed. *sigh*
"David - I will [show] you as as soon as
[you] use revert to standard..."
> % > When all of you folks move from >_ to > then *perhaps*
> % > you can come back and argue with me some more.
> % well, ">_" is standard with many programs, so one
> % "be nice to Mozilla and Outlook Express users".
> Actually, Outhouse seems to have no problem supporting
> %_ for quotes. I don't know whether I like that or not,
> given how much I love to bash it, but there it is.
well - one more program that supports it - good!
but for the vast majority of non-configurable agents
out there - please just use '>' or ">_" - thankyou!
> % > I'm not terribly impressed with yours. No problem, though.
> % well, at least my attribution contains the persons address
> % so you can still use this info when following up to my mail.
> Yep. One of the reasons I'm not impressed with it, actually.
please elaborate!
> % it is vital on mailing lists as there is no repository as there
> % is with news servers from which you could request the parent message.
> IMNSHO it's up to you to keep the parent message
> for as long as you want to be in the thread.
how can you "keep the parent message"
when you never received it at all?
you might just have joined the list -
or be reading it via some archive.
> I realize that that may not sit well with some folks, but
> I'm also the sort who would like to respond to the original
> message, rather than a quoted quoted reply, anyway.
same here - I usually reply to people directly.
however, I do send BCCs of my reply to "P2"
(the sender of the parent message
of the message I am replying to)
when there has been a long interval
and when i know that this person might
not be reading the list/newsgroup any more.
in that case I need the address of that person
and I usually take it from the attribution.
> % moreover, an attribution without any "words" can be used
> % on any mailinglists - independent of its language.
> I want an attribution that reflects my conversational style.
> Yes, I'm also anal-retentive and a bit obsessive and want
> unambiguous date strings (and accurate clocks, grumble grumble)
> where dates are needed (though you'll note that I don't feel
> that that is terribly important in an attribution),
> but my writing style is distinctly casual. An
> introduction like my attribution fits me much better.
I'd suggest you keep the informal attribution for private
conversation and add name+address for mailing lists.
> If I *were* to construct an attribution that had
> these sorts of things in it, I might or might not
> include the address (see above) but would include
> not only the timestamp but the Message-ID: as well;
> *that* is starting to get unambiguous enough for me.
the MID is not supposed to be read by humans -
so you can leave this in the header.
> % > % (and learn to delete unnecessarily quoted line blocks!)
> % > Hey, I thought I trimmed enough.
> % you send lots of quoted empty lines - didn't you notice?
> Actually, I didn't; I try not to take away lines at the
> expense of readability, which can be defined differently
> from person to person, but I do try to trim up the junk.
your replies still have those quoted lines without content.
I stripped them away so you cannot see them.
but you could have done that yourself.
please do so with further replies - thankyou!
> % I am aware that the short date form like 020312 could be mistaken for
> % 1902-03-12 or 2102-03-12 - but so far it has not been a problem. ;-)
> My biggest issue with it, since I can figure it out manually as well
> as the next guy, is that it doesn't sort or machine parse well.
> I should obviously make my scripts and ls wrappers smarter, right? :-)
huh? pray tell - where do any of your programs make use
of those date strings when we use them in these messages
or on webpages? does it matter to your scripts? and
what *exactly* are you doing with that info, anyway?
besides, if your "ls" gets confused with
those short date form then let us know.
Sven [not expecting to hear any complaints
within the next 50 years..]
--
Sven Guckes HOLY WARS of Usenet [EMAIL PROTECTED]
HOLY EDITOR: emacs|vi TEXT: text/plain|base64|quoted-printable
HOLY PAGER: less|more SHELL: sh|bash|ksh|tcsh|zsh tabstop=2|4|8
HOLY textwidth=65|72|80 TABU: indent_string="> " sigdashes=ON
