lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

LYNX-DEV news: question


From: WHITLOCK
Subject: LYNX-DEV news: question
Date: Thu, 16 Oct 1997 14:10:00 -0500 (CDT)

(Sorry about the two repeated posts; I don't user this VMS mailer much...)

On Wed, 15 Oct  Klaus Weide <address@hidden> wrote:

> So is the message available from the server?  Start with
>    "telnet news.host.com 119".

Looks like the message is available if requested by message NUMBER, but
not by message ID.  The NNTP help text says either should be acceptable,
but is that something that the news server can be configured to work with
one, the other, or both?  Pine works, perhaps that retrieves by message
number.  I don't recall seeing that Lynx can be set to use number instead
of message ID; can it?

> What it maybe shouldn't have is the //news.host.com/ part.

Just news:comp.risks gives the same result.  news.host.com is set up
in the lynx.cfg as NNTPSERVER:news.wwa.com (Ok, "host" is really "wwa"; 
I was trying to protect the possibly innocent.)

> ... and you're keeping it a secret what version that would be...

Sorry.  2.7.1f, 2.7.1 with Fotemods from Jul 30.

>        lynx -trace

Ok, I hope I've included all the relevant portions:

HTParse: aName:news:comp.risks   relatedName:
3
HTParse: result:news:comp.risks

LYpush: address:file://localhost/home/menus/internet_tree/home.html
        title:Internet Users' Menu
LYGetFile: getting news:comp.risks

HTParse: aName:news:comp.risks   relatedName:
HTParse: result:

HTParse: aName:news:comp.risks   relatedName:
HTParse: result:
Entered HTAnchor_findAddress
New anchor 0x80ea370 has hash 98 and address `news:comp.risks'
HTAccess: loading document news:comp.risks
HTParse: aName:news:comp.risks   relatedName:file:
HTParse: result:news
HTParse: aName:news:comp.risks   relatedName:
HTParse: result:
HTParse: aName:news://:119/   relatedName:
HTParse: result:
HTNews: Looking for news:comp.risks
HTNews: NNTPSERVER defined as `news.wwa.com'
News: doing HTDoConnect on 'lose://news.wwa.com/'
Connecting to NewsHost ...
HTParse: aName:lose://news.wwa.com/   relatedName:
HTParse: result:news.wwa.com
Looking up news.wwa.com.
TCP: Parsed address as port 119, IP address 198.49.174.10
Making NNTP connection to news.wwa.com.
HTNews: Connected to news host news.wwa.com.
NNTP Response: 200 hirame.wwa.com InterNetNews NNRP server INN 1.5.1 
17-Dec-1996 ready (posting ok).
NNTP command to be sent: mode reader
NNTP Response: 200 hirame.wwa.com InterNetNews NNRP server INN 1.5.1 
17-Dec-1996 ready (posting ok).
NNTP command to be sent: GROUP comp.risks
NNTP Response: 211 1 224 224 comp.risks
Reading list of articles in newsgroup.
GridText: Change to style Normal
GridText: split_line called
HTML:begin_element: adding style to stack - Normal
HTML:begin_element: adding style to stack - Normal
HTML:end_element: Popped style off stack - Normal
HTML:end_element: Popped style off stack - Normal
Newsgroup status=211, count=1, (224-224) required:(0-0)
    Chunk will be (224-224)
GridText: Change to style Heading1
HTML:begin_element: adding style to stack - Heading1
HTML:end_element: Popped style off stack - Normal
GridText: Change to style Normal
GridText: split_line called
GridText: split_line called
Beginning underline
Ending underline
GridText: Change to style List
GridText: split_line called
HTML:begin_element: adding style to stack - List
NNTP command to be sent: HEAD 224
NNTP Response: 221 224 <address@hidden> head
G Path: 
news.wwa.com!news-chi-1.sprintlink.net!news-east.sprintlink.net!news-dc-26.sprintlink.net!news-peer.sprintlink.net!news.sprintlink.net!Sprint!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!newsfeed.internetmci.com!206.156.5.16!news.livenet.net!not-for-mail
G From: address@hidden
Trying to find name in:  address@hidden
G Newsgroups: comp.risks
G Subject: 99c Tripple Cheeseburger!!
G Date: 9 Oct 1997 22:24:46 GMT
G Organization: GBC Internet
G Lines: 9
G Message-ID: <address@hidden>
G NNTP-Posting-Host: dialup26.ds4.livenet.net
G Xref: news.wwa.com comp.risks:224
G .
new Anchor 0x80eac10 named `' is child of 0x80ea370
Entered HTAnchor_findChildAndLink
HTParse: aName:news:address@hidden   relatedName:news:comp.risks
3
HTParse: result:news:address@hidden
HTParse: aName:news:address@hidden   relatedName:
HTParse: result:
Entered HTAnchor_findAddress
New anchor 0x80eacd8 has hash 70 and address `news:address@hidden'
Linking anchor 0x80eac10 to anchor 0x80eacd8
HText_endAnchor: number:1 link_type:1
Beginning underline
Ending underline
GridText: split_line called
HTML:end_element: Popped style off stack - Normal
Reducing List Nesting Level to -1
GridText: Change to style Normal
GridText: split_line called
GridText: split_line called
GridText: split_line called
GridText: split_line called
new Anchor 0x80eaf98 named `' is child of 0x80ea370
Entered HTAnchor_findChildAndLink
HTParse: aName:newspost://news.wwa.com/comp.risks   relatedName:news:comp.risks
1
HTParse: result:newspost://news.wwa.com/comp.risks
HTParse: aName:newspost://news.wwa.com/comp.risks   relatedName:
HTParse: result:
Entered HTAnchor_findAddress
New anchor 0x80eaea0 has hash 37 and address 
`newspost://news.wwa.com/comp.risks'
Linking anchor 0x80eaf98 to anchor 0x80eaea0
HText_endAnchor: number:2 link_type:1
Gridtext: Entering HText_endAppend
GridText: split_line called
GridText: Removing bottom blank line: 
GridText: New bottom line: Post to comp.risks
Gridtext: Anchor found on line:4 col:4
anchor text: '  * "99c Tripple Cheeseburger!!" - address@hidden'   pos: 5
anchor text: '  * "99c Tripple Cheeseburger!!" - address@hidden'   pos: 5
GridText: adding link on line 4 in HText_endAppend
Gridtext: Anchor found on line:8 col:0
anchor text: 'Post to comp.risks'   pos: 1
anchor text: 'Post to comp.risks'   pos: 1
GridText: adding link on line 8 in HText_endAppend
HTAccess:  status=29997
HTAccess: `news:comp.risks' has been accessed.

LYpush: address:news:comp.risks
        title:Newsgroup comp.risks
LYGetFile: getting news:address@hidden

HTParse: aName:news:address@hidden   relatedName:
HTParse: result:

HTParse: aName:news:address@hidden   relatedName:
HTParse: result:
Entered HTAnchor_findAddress
Anchor 0x80eacd8 with address `news:address@hidden' already exists.
HTAccess: loading document news:address@hidden
HTParse: aName:news:address@hidden   relatedName:file:
HTParse: result:news
HTParse: aName:news:address@hidden   relatedName:
HTParse: result:
HTParse: aName:news://:119/   relatedName:
HTParse: result:
HTNews: Looking for news:address@hidden
NNTP command to be sent: mode reader
NNTP Response: 200 hirame.wwa.com InterNetNews NNRP server INN 1.5.1 
17-Dec-1996 ready (posting ok).
NNTP command to be sent: ARTICLE <address@hidden>
NNTP Response: 430 No such article
430 No such article
News: doing HTDoConnect on 'lose://news.wwa.com/'
Connecting to NewsHost ...
HTParse: aName:lose://news.wwa.com/   relatedName:
HTParse: result:news.wwa.com
Looking up news.wwa.com.
TCP: Parsed address as port 119, IP address 198.49.174.10
Making NNTP connection to news.wwa.com.
HTNews: Connected to news host news.wwa.com.
NNTP Response: 200 hirame.wwa.com InterNetNews NNRP server INN 1.5.1 
17-Dec-1996 ready (posting ok).
NNTP command to be sent: mode reader
NNTP Response: 200 hirame.wwa.com InterNetNews NNRP server INN 1.5.1 
17-Dec-1996 ready (posting ok).
NNTP command to be sent: ARTICLE <address@hidden>
NNTP Response: 430 No such article

Alert!: 430 No such article

HTAccess:  status=-29999
HTAccess: `news:address@hidden' has been accessed, No data loaded.
LYpop: address:news:comp.risks
     title:Newsgroup comp.risks
LYGetFile: getting news:comp.risks

HTParse: aName:news:comp.risks   relatedName:
HTParse: result:

HTParse: aName:news:comp.risks   relatedName:
HTParse: result:
Entered HTAnchor_findAddress
Anchor 0x80ea370 with address `news:comp.risks' already exists.
HTAccess: loading document news:comp.risks
HTAccess: Document already in memory.


  -- Brad Whitlock
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;

reply via email to

[Prev in Thread] Current Thread [Next in Thread]