Discussion:
powershell training in hyderabad
(too old to reply)
v***@gmail.com
2016-12-03 06:47:42 UTC
Permalink
Tech Repack are Professional in powershell training in hyderabad providing online courses like powershell online training, sccm 2012 training and Microsoft app v 5.1 Packaging Online Training.
Mayayana
2017-04-16 14:07:55 UTC
Permalink
<***@gmail.com> wrote

| Tech Repack are Professional in powershell
|training in hyderabad providing online courses
|

Test post only.
Sorry to hijack this post. I needed to do a test
and this particular post seems to be completely
irrelevant.

I've found that when I type CSS with a class
dot, like the following, in the mozilla newsgroup
it shows up with two dots! I can't imagine why.
I wanted to try it here.

.tab-throbber {display: none !important;}

OK. End of test.
R.Wieser
2017-04-16 15:23:21 UTC
Permalink
Mayayana,
Post by Mayayana
I've found that when I type CSS with a class
dot, like the following, in the mozilla newsgroup
it shows up with two dots! I can't imagine why.
When sending a mail or news message a single dot on a line ends the message
(and commands can be send again). A dot on its own on a line therefore
needs to be "escaped" by putting another dot infront/after it. It just
might be related to that ...

Regards,
Rudy Wieser
Post by Mayayana
| Tech Repack are Professional in powershell
|training in hyderabad providing online courses
|
Test post only.
Sorry to hijack this post. I needed to do a test
and this particular post seems to be completely
irrelevant.
I've found that when I type CSS with a class
dot, like the following, in the mozilla newsgroup
it shows up with two dots! I can't imagine why.
I wanted to try it here.
.tab-throbber {display: none !important;}
OK. End of test.
Mayayana
2017-04-16 15:38:16 UTC
Permalink
"R.Wieser" <***@not.available> wrote

| When sending a mail or news message a single dot on a line ends the
message
| (and commands can be send again). A dot on its own on a line therefore
| needs to be "escaped" by putting another dot infront/after it. It just
| might be related to that ...

I doubt it. That's for just a dot with nothing else.
I tried an email and a post here with the text that
acted up on the Mozilla server and there was no
problem. The Mozilla post seemed to be OK when
I switched from | to > for commenting. Either
that or the Mozilla people had already fixed their
server.

So then I wondered whether there might be some
arcane relationship with | and . But I can't find any
in a search. And the . didn't even follow on the
next line from the |. So my best guess is that the
Mozilla server has a bug in the way it parses posts,
inadvertently doing something that wasn't intended.
R.Wieser
2017-04-16 16:05:46 UTC
Permalink
Mayayana,
Post by Mayayana
I doubt it. That's for just a dot with nothing else.
So, why does it only do that on lines starting with a dot (and nowhere else)
?

And by the way, that second part ? Thats what said in my reply ...
Post by Mayayana
Mozilla server has a bug in the way it parses posts,
inadvertently doing something that wasn't intended.
See above. :-)

Regards,
Rudy Wieser
Post by Mayayana
| When sending a mail or news message a single dot on a line ends the
message
| (and commands can be send again). A dot on its own on a line therefore
| needs to be "escaped" by putting another dot infront/after it. It just
| might be related to that ...
I doubt it. That's for just a dot with nothing else.
I tried an email and a post here with the text that
acted up on the Mozilla server and there was no
problem. The Mozilla post seemed to be OK when
I switched from | to > for commenting. Either
that or the Mozilla people had already fixed their
server.
So then I wondered whether there might be some
arcane relationship with | and . But I can't find any
in a search. And the . didn't even follow on the
next line from the |. So my best guess is that the
Mozilla server has a bug in the way it parses posts,
inadvertently doing something that wasn't intended.
Loading...