Rf:j lounge/patio
Joining lounge/patio 54 new messages.
Rf:sea dat 26jun2001 to dat 27jun2001 mjuergens
searching for 'mjuergens'
Msg #221 [author]
Msg #222 [author]
Rf:j gripes/bugs
mjuergens wrote 223, not 222. This happened once: Subsequent searches returned the correct
message number.
Anonymous
Logged In: YES
user_id=138414
==========
gripes/bugs #2221, from peabo, 1991 chars, Wed Jul 4 12:41:01 2001
TITLE: Search command displays incorrect message number
I searched a topic for a string in the current (last) message and the
message number displayed in the matching messages was wrong by several
hundred (766 instead of 1021). See transcript below.
It's repeatable. Also, the first citation (message 765) is accurate.
Only the second citation has the wrong message number.
peter
Hit <RETURN> for next active conf/topic.
Read:sea 1 to 1021 GoF
searching for 'GoF'
Msg #765 TITLE: Add hours and minutes to status and logoff reports to match BIX
Msg #766 These days that's called the "state" pattern. See GoF P305 or
.More..
No more unread messages in this topic
Hit <RETURN> for next active conf/topic.
Read:766
==========================
cosy_dev/tcosy #766, from peabo, 258 chars, Mon Apr 30 21:05:44 2001
This is a comment to message 734.
I recommend not adding commands to root's context because of security issues.
It's bad enough having ls instead of /bin/ls in root shell scripts, but when
commands start meaning different things than they do out of the box, it's
a recipe for trouble.
peter
But when I (John Ralls) tried it:
Rf:j cosy_dev/tcosy
Joining cosy_dev/tcosy 0 new messages.
Rf:sea 1 to 1021 GoF
searching for 'GoF'
Msg #765 TITLE: Add hours and minutes to status and logoff reports to match BIX
Msg #1021 These days that's called the "state" pattern. See GoF P305 or