|
Grex > Coop12 > #132: Proposal to eliminate deceased conferences | |
|
| Author |
Message |
| 19 new of 60 responses total. |
gelinas
|
|
response 42 of 60:
| 
Sep 25 03:14 UTC 2002 |
I suppose there are ways to improve the "browse" command, but I don't know
enough about how it works to suggest them. What I'd *really* like, though,
is a way to set a specific response as "new".
Sometimes, I get through fifty of the hundred new responses and have to bug
out. 'Twould be really useful to mark those fifty as "read", so I can pick
up where I left off when I get back to the item.
|
i
|
|
response 43 of 60:
|
Sep 25 04:33 UTC 2002 |
Re: #33
Since i don't recall ever getting a cfadm-as-fw link request, i could
have some logical fun answering the question... I think i'd "just do
it" in response to most such requests. What's there to lose? It takes
virtually no disk space, and cfadm wouldn't be fw if the cf was very
lively.
|
krj
|
|
response 44 of 60:
|
Sep 25 05:05 UTC 2002 |
resp:42 :: In Picospan, the command gelinas is looking for is:
mark [respnum]
and the specified response number will be the first new response
next time you read the item.
|
davel
|
|
response 45 of 60:
|
Sep 25 23:28 UTC 2002 |
Hmm....
Respond or pass? help mark
Sorry, no help available for "mark"
I've often wished for what Joe asked for, myself.
|
aruba
|
|
response 46 of 60:
|
Sep 26 04:17 UTC 2002 |
I have too, and I never knew about "mark". THanks Ken!
|
remmers
|
|
response 47 of 60:
|
Sep 26 11:48 UTC 2002 |
I didn't know about it either, and I've been using Picospan for
18 years.
It doesn't work *quite* as I'd like it to. If I use mark to
flag a response as new (e.g. response 43 of item 132), it does
indeed start at response 43 if I do "read new 132". However,
marking a response in that way doesn't seem to make the item
show up when I do a "browse new" or "read new". It'd be nice
if Picospan would remind me that there's a marked item, so that
I don't forget about it.
|
davel
|
|
response 48 of 60:
|
Sep 26 13:01 UTC 2002 |
This response has been erased.
|
gelinas
|
|
response 49 of 60:
|
Sep 27 02:23 UTC 2002 |
Thanks, Ken. I'll have to try it. Maybe it'll work my with "read unseen"
macro ('ru').
|
aruba
|
|
response 50 of 60:
|
Sep 27 13:23 UTC 2002 |
Hmmm. I think, though, if you mark an item and then later someone posts
something new to it, it will show up as new and start at the right place.
So mark at least works well for active items. (This is from a single test,
so I hope I'm right.)
|
remmers
|
|
response 51 of 60:
|
Sep 27 16:27 UTC 2002 |
You're probably right. I didn't test that case.
|
davel
|
|
response 52 of 60:
|
Sep 28 02:08 UTC 2002 |
That's consistent with the way fixseen works. (It marks the item as read, but
doesn't mark any responses as read; so when someone posts a new response,
you're suddenly buried under all the old responses you used fixseen to avoid
reading.)
|
janc
|
|
response 53 of 60:
|
Sep 28 04:32 UTC 2002 |
Weird. In fronttalk the "new" and "postpone" commands can take response
number arguments. If given, that will be the first new response the next
time you read it, whether new stuff has been posted or not. I'll need to
add a "mark" command, and documentation.
|
cmcgee
|
|
response 54 of 60:
|
Sep 29 13:50 UTC 2002 |
re 52: Ah hah! that may explain my sense of "I thought I caught up, but it
seems like I didn't"
|
davel
|
|
response 55 of 60:
|
Sep 30 01:07 UTC 2002 |
(Try something like "read 5 p > /dev/null" to really catch up that way.)
|
cmcgee
|
|
response 56 of 60:
|
Sep 30 15:21 UTC 2002 |
When I use the "n" command, it marks something as new, but it doesn't let me
see anything past that. Is there some way to leave only one item marked as
new?
|
scott
|
|
response 57 of 60:
|
Sep 30 16:24 UTC 2002 |
"po", for "postpone".
|
carson
|
|
response 58 of 60:
|
Oct 1 05:16 UTC 2002 |
(or "pr", for "preserve".)
|
jaklumen
|
|
response 59 of 60:
|
Mar 25 02:05 UTC 2003 |
interestingly enough, I did browse the vomit conference once. Strange
and icky sort of funky, but whatever floats your boat.
re: way back there, I think it's usually best to have an agora item
linked to the specialty conf (unless the participants don't want that
for some reason) and then note that the item has been linked. Ken
does this quite frequently with music items.
Remember that there is often an agora item that promotes the other
conferences.
Also, a few dead conferences have found new life with new subjects:
notably Inferno and Steve (now titled Perky).
Note also that my reply is several months past the last one. Who
knows-- these conferences might come alive with some funky newcomer.
We've seen enigma go in fits and starts, and basically recovery is
active as needed. I think maybe the latter got a little more activity
because I wanted it to and I took the fairwitness responsibilities.
Sorry, Richie, I heartily disagree.
|
carson
|
|
response 60 of 60:
|
Mar 25 02:42 UTC 2003 |
(nah, I think coop will remain dead. thanks for playing.)
|