On 02/05/05, Rahul Sinha <quidire(a)gmail.com> wrote:
This didn't go to the whole list; did you want to
send it there?
Bah! I wish I could stop that happening - or at least easily predict
and spot *when* it would happen. I think it's when one reply goes to
the sender's address as well as the list, and GMail combines these so
that the next reply goes only to the person, and not the list.
Grrrr...
On 2 May 2005, at 12.50 PM, Rowan Collins wrote:
On 02/05/05, Rahul Sinha
<quidire(a)gmail.com> wrote:
#REDIRECT
[[Foo]] BECAUSE For info on Foo, see [[#Foo]]
or maybe
#REDIRECT [[Foo]] #BECAUSE For info on Foo, see [[#Foo]]
to make it more clear that "#because" is a magic word, not part
of the
explanation.
Makes sense; I had thought the syntax should allow for arbitrarily
long "because" explanations... thus an end delimiter would be of
use...
I guess the reason I didn't bother with that is that I can't think of
a reason to have content *other than* an explanation on the redirect
page. So everything from "#because" to the end of the page can be
safely treated as an explanation. As I say, the "#because" is only
really there so that existing redirects don't start behaving in ways
their creators didn't intend - if designing from scratch, one probably
wouldn't use that either.
--
Rowan Collins BSc
[IMSoP]
--
Rowan Collins BSc
[IMSoP]