From: MERC::"uunet!VM1.NoDak.EDU!ANU-NEWS" 17-JUL-1992 13:12:45.56 To: Multiple recipients of list ANU-NEWS CC: Subj: Some (new?) bugs in ANU NEWS 6.1alpha4 ! In article <1992Jul10.160618.1375@tac.fi>, tiok_jk@tac.fi (Juha Koivisto) writes: > I discovered one new(?) bug in 6.1-alpha-4: > > If you have line NEWREGISTER=*/confirm in your NEWSRC-file > and then you answer Q to the "New newsgroup: group.name, Register? [Y]"- > question then your profile (and later your NEWSRC when you EXIT) > changes to NEWREGISTER=*0confirm and this means that next time when > there is new groups NEWS will not ask you confirmation any more. > If you answer Y, N or A then all works fine. > > I looked NEWSPROFILE.C and line 103 looks like that: > if (slash) *slash = '0'; > and I am not sure if it should be like > if (slash) *slash = '\0'; > I have not tried it, but this may be the reason. Now I had little more time to examine it and that previos guess was not correct. NEWSPROFILE.C line 103 looks like: if (slash) *slash = '0'; but this '0' should actually be '/'. So the line 103 should be: if (slash) *slash = '/'; I compiled it again and this little change seems to fix this bug. I hope that someome (Geoff?) will correct this to the next release. When I was testing it I came across with few more problems: If you answer A then news will not print the names of the groups when it register those groups. If you answer Q then news will (correctly?) print the groups with the text 'not registered'. Another problem is with RC-FILTER profile setting. When you have this profile setting in your newsrc and you start news, it will print (like New newsgroup: xxxx.yyyyy not registered) all those newsgroups you don't have in your newsrc-file. This did not happen with 6.0-3. I know few people in our site who have about 15 newsgoups and RC-FILTER in their newsrc-files and now when they start news they have to watch about 2000 lines of text before they can use news. When they exit the newsrc file will be ok. It does not have those goups in it. The third bug is with SHOW UNSEENITEMS command (the same bug was already in 6.0-3. Has anybody else noticed this?). Select any nousgroup where is unseen items. Mark some of them as read but leave some items from the beginning of the list as unread (or at least there should be skipped or read items after one unseen item) and use SHOW UNSEENITEMS command. If there were consecutive read/skipped items then news will still show every second of them. And this is not all. Try the SHOW UNSEENITEMS command again. Now news will mark some of already read (or skipped) articles as unread. If you use the SHOW UNSEENITEMS command enough times then all the items will be as unread ! -- Juha Koivisto * Department of Information Technology tiok_jk@tac.fi * City of Tampere, Finland