Getting Python Accepted in my Organisation

[bonono]

It would still be easier to respond to your posts if you didn't
top-post, though (i.e., if you didn't put your comments BEFORE what
you're commenting on -- that puts the "conversation" in a weirdly
distorted order, unless one give up on quoting what you're commenting
on, or invests a lot of time and energy in editing...;-).

oops. I developed this habit because I found I like to read it this
way. As I usually would read just the first few lines to see if I want
to read on. top post serve me well for this purpose. And I assume other
may also find my stuff not worth reading and skip quick so why force
them to scroll all the way down ? I would only do in-line response type
when there is a need for specific response in context.

 

[Jorge Godoy]

oops. I developed this habit because I found I like to read it this
way. As I usually would read just the first few lines to see if I want
to read on. top post serve me well for this purpose. And I assume other
may also find my stuff not worth reading and skip quick so why force
them to scroll all the way down ? I would only do in-line response type
when there is a need for specific response in context.

I'm more of the type that wouldn't read on if I have no context to what I'm
reading... Specially if there's a mix of top posts with bottom posts...

 

[Guest]

I'm more of the type that wouldn't read on if I have no context to
what I'm reading... Specially if there's a mix of top posts with
bottom posts...

Anyway, if you keep more than a pageful of the previous message, you're
probably not cutting it hard enough. Just keep what's needed to keep the
context.

 

[bonono]

I'm more of the type that wouldn't read on if I have no context to what I'm
reading... Specially if there's a mix of top posts with bottom posts...

That just means different people have different reading style. Just
like some find one-liner easier to read, some find step by step
imperative style easier to read.

 

[bonono]

Anyway, if you keep more than a pageful of the previous message, you're
probably not cutting it hard enough. Just keep what's needed to keep the
context.

Sometimes it is easy(like this). Sometimes, it is not easy and cutting
in any part of the original message would make it out of context.

 

[Chris F.A. Johnson]

oops. I developed this habit because I found I like to read it this
way. As I usually would read just the first few lines to see if I
want to read on. top post serve me well for this purpose. And I
assume other may also find my stuff not worth reading and skip quick
so why force them to scroll all the way down?

If I want to read that way, I just tell my newsreader not to
display the quoted material (actually it displays the first line of
each block).

Or I press TAB to jump to the next original material.

I would only do in-line response type when there is a need for
specific response in context.

If there's not, why would you quote anything?

 

[bonono]

If I want to read that way, I just tell my newsreader not to
display the quoted material (actually it displays the first line of
each block).

Or I press TAB to jump to the next original material.

My news reader is through Google, web browser. So there is no this
feature there.

If there's not, why would you quote anything?

To keep the original so if people want, they can still read it. And the
google reader has this feature which has the quoted collapsed. And this
response is the kind that I think in-line response is needed

I believe what reader one use also drive the reading/writing habit.

 

[bonono]

It would still be easier to respond to your posts if you didn't
top-post, though (i.e., if you didn't put your comments BEFORE what
you're commenting on -- that puts the "conversation" in a weirdly
distorted order, unless one give up on quoting what you're commenting
on, or invests a lot of time and energy in editing...;-).

One interesting I found, seems that Google's usenet reader(through web)
favor top post, even in line top post. If I do it as this one, I lose
the show/hide quoting feature of it. If I use top post(even in line on
top of the previous's message context, the BEFORE style), I got
multiple nice hide/show feature.

 

[Steven D'Aprano]

On Fri, 04 Nov 2005 20:55:48 -0500, Chris F.A. Johnson wrote:

<quoting deliberately removed to make a point>

So that people reading your reply know what you are commenting about.

(Now, imagine that you're reading from a newsgroup where Chris' post has
disappeared off the server, or perhaps never showed up at all.)

 

[Chris F.A. Johnson]

On Fri, 04 Nov 2005 20:55:48 -0500, Chris F.A. Johnson wrote:

<quoting deliberately removed to make a point>

So that people reading your reply know what you are commenting about.

(Now, imagine that you're reading from a newsgroup where Chris' post has
disappeared off the server, or perhaps never showed up at all.)

Did I say something???

 

[Steven D'Aprano]

Did I say something???

Yes.

Quoting from your earlier post, including the text you quoted:

I would only do in-line response type when there is a need for
specific response in context.

If there's not, why would you quote anything?
[end quote]


You should almost always quote *something*, if only to give some
context. If there is no context at all, you almost certainly want to
start a new thread.