== off topic == One Google Groups irritation fixed
Kent Paul Dolan
written by me, and half a million by other users of
Google Groups, they've fixed the default "Reply"
button, the one easily visible to naive users, so
that it quotes the entire article as a beginning of
the "context" so often demanded here, just like
every other news article writing tool has done since
the beginning of (Unix) time.
FYI
xanthian.
It took me three tries to convince myself the
behavior had changed, though.
--
Posted via Mailgate.ORG Server - http://www.Mailgate.ORG
dogscoff
Kent Paul Dolan wrote:
> Finally ...[google groups] fixed the default "Reply"
> button,
OK, so how long until the first n00b appears to hit the reply button,
and then painstakingly delete out all the context before writing their
post...
Kent Paul Dolan
> OK, so how long until the first n00b appears to
> hit the reply button, and then painstakingly
> delete out all the context before writing their
> post...
Too late for the newbies, I got there first, since
in those three cases that was exactly my intention,
to post a context-free reply, because the "context"
to which I was answering was a history of posting
habits by the prior poster, not some particular
quotable part of the prior posting.
xanthian.
Zeitgeist
Kent Paul Dolan wrote:
><snip google groups reply stuff>
>
> It took me three tries to convince myself the
> behavior had changed, though.
>
title too?
--
Zeitgeist.
A manually typed sig? How dull.
Google groups get your act together!
Roy L. Fuchs
Gave us:
2 seconds. They are so lazy, they like top posting, yet when faced
with proper formatting, they will deliberately spend time to do it
incorrectly anyway.
Kent Paul Dolan
> Is it just me, or is google groups showing [s] tags in the
> title too?
Hmm, it will take two tries to answer you, but let's find out.
This one's a test, with subject line:
[testing Google Groups retention of square brackets] (was: == off topic
== One Google Groups irritation fixed)
xanthian.
Kent Paul Dolan
[posted via Google Groups, I forgot to say]
Well, the result is a mixed bag; when the article
was _viewed_ via Google Groups, the left sidebar, in
"view as tree" mode, shows that whole subject line,
square bracketed part and all, but the main page
display omits the part in square brackets, just as
before, leaving:
(was: == off topic == One Google Groups irritation fixed)
displayed.
That's unsatisfactory, since use of "view as tree"
mode is optional, and so the main subject line
display is still incorrect, and a nuisance to
readers here in rgrn who are expecting to use such
flagged subject lines to avoid/choose/flag Slash'Em
articles.
Worse yet, the square bracketed part, even though
Google Groups obviously _has it_, isn't copied into
the followup subject line, and so this article will omit
what should have been copied along to the new
subject line. Grrrr. I'm sticking a new set of square
brackets at the end, since I seem to recall seeing
a square bracketed [s] in an article I cannot re-locate;
several days back.
The recommendation (made by someone else) to use
some other article meta-flag delimiters still holds.
I, obviously, like putting a pair of equal signs at
each end, it nicely sets off the "bracketed" stuff
for users of Google Groups, apparently quite a few
participants here.
FWIW
xanthian.
Kent Paul Dolan
> I'm sticking a new set of square
> brackets at the end, since I seem to recall seeing
> a square bracketed [s] in an article I cannot re-locate;
> several days back.
And that works perfectly in both the "view as tree" sidebar
_and_ in the main body article subject header. So, the *bug*
is related to the bracketed part being at the _beginning_
of the subject line; it works OK elsewhere. It even copied okay
to this followup without help.
quant. suf.
HTH
xanthian.