Re: use same numbers for pager(responses) and thread(articles) view

On Sat, May 26, 2007 at 04:28:20PM +0200, Rado S wrote:
> > > When in the pager I hit #4, it jumps to a different message than
> > > when I hit #4 in the thread view. This is ... confusing.
> > 
> > it prompts for different things, in the thread level it prompts:
> > "Select article> " whereas in the pager it prompts
> > "Read response> ". article 1 is response 0 so the current code is correct.
> >
> > > Shouldn't the same number jumped to refer to the same message
> > > in the thread independent of viewing mode?
> > 
> > only if you prompt for the same thing (which the current code doesn't do).
> 
> Ok, if it's just the word, there you go.

now the threadlvel is the only level where the numbering begins with 0, in
the group or select level and in the menu the numbering starts with 1. fixing
one ionconsistency by adding another one isn't very helpfull.

> -	if ((num = prompt_num(ch, _(txt_read_resp))) == -1) {
> +	if ((num = prompt_num(ch, _(txt_select_art))) == -1) {

here you remove the last occurence of txt_read_resp but it is still in
extern.h/lang.c