Re: Segmentation fault
- From: Richard <rgrdev_@xxxxxxxxx>
- Date: Sun, 22 Feb 2009 06:35:02 +0100
Keith Thompson <kst-u@xxxxxxx> writes:
CBFalconer <cbfalconer@xxxxxxxxx> writes:
Ian Collins wrote:
CBFalconer wrote:
Keith Thompson wrote:
.... snip ...
Incidentally, you seem to be approximately the fifth person to
point out that s is uninitialized. The first post to mention
this was posted about 9 hours before yours. And yes, that post
did arrive on your server; you and I use the same one.
However my reader shows posts in order of date/time, so the first
thing I read is the original question. I reply, and then find
other answers.
Why don't you read threads as threads?
I do. But within threads, things are organized as query followed
by answer. If there are multiple answers they are sorted by time.
e.g.:
.query t
|--.ans_1 t+1
|--.ans_2 t+22
| |--.ans_2_2 t+33
| |--.ans_2_3 t+34
|--.ans_3 t+3
etc. So I will see ans_1 and ans_2_* before ans_3.
Does that mean you have to respond to "query" before reading "ans_1"?
If it does, either get a better newsreader or learn to use the one you
have.
In mine, for example, I see a list of articles similar to the one you
describe. When I read an article, it's marked as read, but it doesn't
vanish from the list. That means I can easily read an entire thread
(at least the subset of it that's currently available), then go back
to an article I've already read and post a followup to it if there's a
point nobody else has made yet.
You can also reconstruct the thread with "A T" as well as mark articles
to stay visible despite read status.
.
My newsreader is Gnus, which runs under emacs; if you don't like
emacs, you're not going to like Gnus. But any decent newsreader
should let you do something similar.
- References:
- Segmentation fault
- From: vaib
- Re: Segmentation fault
- From: CBFalconer
- Re: Segmentation fault
- From: Keith Thompson
- Re: Segmentation fault
- From: CBFalconer
- Re: Segmentation fault
- From: Ian Collins
- Re: Segmentation fault
- From: CBFalconer
- Re: Segmentation fault
- From: Keith Thompson
- Segmentation fault
- Prev by Date: Re: Segmentation fault
- Next by Date: Re: Serious conformance bug in <some_compiler>
- Previous by thread: Re: Segmentation fault
- Next by thread: Re: Segmentation fault
- Index(es):
Relevant Pages
|
