Path: utzoo!mnetor!uunet!kddlab!ccut!ascgw!flab!umerin From: umerin@photon.stars.flab.Fujitsu.JUNET (Masanobu UMEDA) Newsgroups: comp.emacs Subject: Re: Bad assumptions made by GNUS NNTP news reader Message-ID: Date: 26 Feb 88 09:46:12 GMT References: <2766@flab.flab.fujitsu.JUNET> <5372@elroy.Jpl.Nasa.Gov> Sender: news@flab.flab.fujitsu.JUNET Reply-To: umerin%flab.flab.Fujitsu.JUNET@uunet.uu.NET Followup-To: comp.emacs Distribution: comp Organization: Fujitsu Laboratories Ltd., Kawasaki, Japan. Lines: 51 In-reply-to: earle@jplopto.uucp's message of 4 Feb 88 11:01:56 GMT Posting-Front-End: GNU Emacs 18.47.5 of Mon Nov 2 1987 on photon (berkeley-unix) In article <5372@elroy.Jpl.Nasa.Gov> earle@jplopto.uucp (Greg Earle) writes: > (1) GNUS sets the `Path:' header to be `NNTP-host!user' where NNTP-host > is the name of the NNTP server that GNUS uses. This is patently wrong, `Path:' field is intended to be used for feeding news articles effectively, not by mail. If host name of NNTP client is included in the path, the host will not receive the article even when the host is receiving or relaying usenet news. This is absolutely wrong. > (2) GNUS seems obligated to insert a Message-ID: field. I don't know how > `rrn' does it, but I do know that using `rrn' results in the NNTP server > having its own inews create the message ID, like `<1234@nntp_svr.some.do.main>' > which makes life easier for other Usenet software to deal with. Instead, > GNUS creates a Message-ID: field that concatenates the user's login name, > converted to all CAPS, then a `.GNUS' followed by a number (1 or more?) thus > a followup by me would get tagged with something like > Message-ID: `rrn' (standard NNTP client program) has its own client inews program which should be installed publicly in local host by system administrator (or root). A number in Message ID can be easily shared by inews between users in the local host. On the other hand, GNUS need not to be installed publicly because it does not depend on any other standard news programs except for NNTP server. So, there is no safe way to share a number of message ID between other GNUS users in the local host. I think NNTP server should do the job. Anyway, what kind of Message ID do you expect? > (3) When entering a newsgroup, GNUS decides you must want to see the beginning > of the first unread article in the group, so it sticks it in the buffer. Just type `=' instead of SPACE. You may not be able to find out the command because of my Japanenglish. (:-) > (4) GNUS keeps a window of 4 lines of Subject: lines for reference, while > reading. This is a good feature, but I don't understand why when the last > article in the window is read, the window only scrolls up two lines, showing > the (now current) next article and one after that, instead of scrolling > N-1 lines so that the article > you just read is the only one left, and 3 new Subject: lines appear. 2 > lines of previous context is acceptable for the read buffers , but is > unwieldy for just a four line window. This is Emacs feature. GNUS does nothing about scrolling. -- Masanobu UMEDA umerin@flab.flab.Fujitsu.JUNET umerin%flab.flab.Fujitsu.JUNET@uunet.uu.NET