|
Grex > Coop9 > #38: Since I don't know where else to do it... | |
|
| Author |
Message |
toking
|
|
Since I don't know where else to do it...
| 
Jan 6 20:13 UTC 1997 |
Since I don't know where else to do it, I'm going to suggest something
here...reading the conferances w/backtalk is all fine and dandy, but
if you're like me, you jump around conferances alot, and don't want to
be bogged down by like a years worth of old responses to things, but the
topic being responed to is interesting enough to see what the current
spiel is on it...so you want to be able to read the new responces as
they show up.
As far as my understanding goes, "forget" wont let you do that,
so why not (if it would be possible) either replace it with (or put in
a new button for) seen?
I don't know if it would be easily or fruitfully done, but it would be
nice.
Joe
|
| 15 responses total. |
ryan1
|
|
response 1 of 15:
|
Jan 6 20:35 UTC 1997 |
Well, the command "fixseen" in picospan marks all the items as read, so
it gets rid of all the ancient responses. Then when somebody else posts
in one of the items, the BBS reader (picospan or backtalk) recognizes it
as a "newresponse item". I'm sure somebody else could explain this
better than me, though.
|
popcorn
|
|
response 2 of 15:
|
Jan 6 20:54 UTC 1997 |
Joe, you might want to explore the "read since" command. At an "Ok:" prompt,
you can type "read since 12/20/96" to see all responses made on or after
December 20. There's a Backtalk equivalent to this, though off the top of
my head I don't know what it is. It's only available through the Pistachio
Backtalk interface, not through Vanilla.
|
albaugh
|
|
response 3 of 15:
|
Jan 6 21:51 UTC 1997 |
Then there's the brute-force approach: Find out how many responses there are,
i.e. the "m" of "#n of m". At the "more" prompt, type "q" to quit. If you
get the "Pipe interrupt" message, no problem, just enter "l" to go to the last
response. There, now you're caught up. Jump back 10 or 20 responses by
entering the appropriate number, based on "m". E.g. if "m" were 250, enter
240 to see the last 10 (11!) responses. I don't know if this works in
Backtalk...
|
janc
|
|
response 4 of 15:
|
Jan 7 03:17 UTC 1997 |
The pistachio interface in Backtalk does provide the equivalent of
"read since 12/20/96" kinds of commands. Got to the "list of items" page.
There is a box you can type a date into and hit a button to read all items
and responses to a conference since that date.
Generally, backtalk still needs a larger variety of these kinds of commands.
Picospan is much more flexible.
|
jenna
|
|
response 5 of 15:
|
Jan 7 05:09 UTC 1997 |
Fixseen has its problems, in my edperiences, if you
get a nw response to an item in a conf you've fixseened you still
have the scroll through it to get to the new responses, so it doesn't realy
do
what it says it does, though it is very good for getting itno newer items.
|
rcurl
|
|
response 6 of 15:
|
Jan 7 16:50 UTC 1997 |
Only if you *join* the conference. However if you put it in your .cflist,
you will be shown only the new responses.
|
valerie
|
|
response 7 of 15:
|
Jan 8 00:15 UTC 1997 |
This response has been erased.
|
jenna
|
|
response 8 of 15:
|
Jan 8 03:14 UTC 1997 |
huh? (my resoponse too)
|
rcurl
|
|
response 9 of 15:
|
Jan 8 07:12 UTC 1997 |
What?
|
davel
|
|
response 10 of 15:
|
Jan 9 12:38 UTC 1997 |
I think I see where Rane is confused. Rane, if you join a conference and then
just say "read", the default is for only new stuff. If you (say) browse
and then read by item # ("read 55" or whatever), the default is *not* new -
you must *say* "new" (or "n") if you specify item #s to read. Your .cflist
has nothing to do with it - but I suspect you changed your method of reading
about the time you discovered .cflists and "next". (I think I vaguely
remember Rane's comments at the time.)
|
rcurl
|
|
response 11 of 15:
|
Jan 9 18:54 UTC 1997 |
I was confused by what I took to be Jenna's confusion ;->. My comment in #6
applies to *items*. So, I don't understand the problem Jenna describes
in #5: if you've done a "seen" (I don't think you need the "fix"), you
will only be shown new responses in that cf after that time. Why do you have
to scroll items again, Jenna?
|
jenna
|
|
response 12 of 15:
|
Jan 10 00:19 UTC 1997 |
i don't know, when i used to have multiple logins and bring them into the
poetry conferences
I'd do fixseen with every single one, then when I came to login the next day
IF there was a new response to say item 1, and item one had 102 responses,
i would
have to ead all 102 reponses just o read the one new one.
|
rcurl
|
|
response 13 of 15:
|
Jan 10 06:18 UTC 1997 |
Only thing I can think of was that a bug ate your partcipation file. I gather
this doesn't happen anymore?
|
davel
|
|
response 14 of 15:
|
Jan 10 17:07 UTC 1997 |
It does indeed sound like something ate your participation file - probably
something like a system crash while the file was being written.
Fixseen does work that way. It seems set the marker for the time you read
the item, but not whatever marks which resps you've read. Or something.
A (rather time-consuming) alternative: "read all pass >/dev/null"
|
jenna
|
|
response 15 of 15:
|
Jan 13 23:09 UTC 1997 |
No... it would have had to happen about 20 times for it to have happened
everytime
i did that... i had a LOT of logins, and its not that fixseen works now.
it's that i do't make lots of logins anymore.
|