GNU bug report logs - #18255
Selecting a group with RET vs gnus-thread-hide-subtree

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 18255 in the body.
You can then email your comments to 18255 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Carlos Pita <carlosjosepita <at> gmail.com>
To: submit <at> debbugs.gnu.org (The Gnus Bugfixing Girls + Boys)
Subject: Selecting a group with RET vs gnus-thread-hide-subtree
Date: Tue, 12 Aug 2014 18:41:19 -0300

Selecting with RET is supposed not to select any article in the summary
buffer. Nevertheless, if the first article in the summary is an
unseen/unread article belonging to a thread, then that thread is
expanded, even if gnus-thread-hide-subtree is t. To make things more
confusing, the little > at the left fringe is shown in the last article
of the summary, not the first.

I think a more sensible behavior is:

1) Show the > at the article SPACE (as opposed to RET) would have
selected, but without really selecting it.

2) Don't expand any thread at all (that is, when selecting the group
with RET).

Implementing just 1 will be a second best at least, because one can
interpret this behavior as kinda "selecting without showing". But the
current behavior is misleading: nothing seems to be selected, but there
is an arrow pointing to the last article, despite the point is in the
first one and the first thread is expanded => pretty messy.

Best regards
--
Carlos

Gnus v5.13
GNU Emacs 24.3.92.1 (i686-pc-linux-gnu, GTK+ Version 3.12.2)
 of 2014-07-22 on carlos
200 news.gmane.org InterNetNews NNRP server INN 2.5.1 ready (posting ok)
100 Legal commands
  ARTICLE [message-ID|number]
  AUTHINFO USER name|PASS password|GENERIC program [argument ...]
  BODY [message-ID|number]
  CAPABILITIES [keyword]
  DATE
  GROUP newsgroup
  HDR header [message-ID|range]
  HEAD [message-ID|number]
  HELP
  IHAVE message-ID
  LAST
  LIST [ACTIVE [wildmat]|ACTIVE.TIMES [wildmat]|DISTRIB.PATS|DISTRIBUTIONS|HEADERS [MSGID|RANGE]|MODERATORS|MOTD|NEWSGROUPS [wildmat]|OVERVIEW.FMT|SUBSCRIPTIONS]
  LISTGROUP [newsgroup [range]]
  MODE READER
  NEWGROUPS [yy]yymmdd hhmmss [GMT]
  NEWNEWS wildmat [yy]yymmdd hhmmss [GMT]
  NEXT
  OVER [range]
  POST
  QUIT
  STARTTLS
  STAT [message-ID|number]
  XGTITLE [wildmat]
  XHDR header [message-ID|range]
  XOVER [range]
  XPAT header message-ID|range pattern [pattern ...]
Report problems to <usenet <at> ger.gmane.org>.
.
382 Begin TLS negotiation now
100 Legal commands
  ARTICLE [message-ID|number]
  AUTHINFO USER name|PASS password|GENERIC program [argument ...]
  BODY [message-ID|number]
  CAPABILITIES [keyword]
  DATE
  GROUP newsgroup
  HDR header [message-ID|range]
  HEAD [message-ID|number]
  HELP
  IHAVE message-ID
  LAST
  LIST [ACTIVE [wildmat]|ACTIVE.TIMES [wildmat]|DISTRIB.PATS|DISTRIBUTIONS|HEADERS [MSGID|RANGE]|MODERATORS|MOTD|NEWSGROUPS [wildmat]|OVERVIEW.FMT|SUBSCRIPTIONS]
  LISTGROUP [newsgroup [range]]
  MODE READER
  NEWGROUPS [yy]yymmdd hhmmss [GMT]
  NEWNEWS wildmat [yy]yymmdd hhmmss [GMT]
  NEXT
  OVER [range]
  POST
  QUIT
  STARTTLS
  STAT [message-ID|number]
  XGTITLE [wildmat]
  XHDR header [message-ID|range]
  XOVER [range]
  XPAT header message-ID|range pattern [pattern ...]
Report problems to <usenet <at> ger.gmane.org>.
.

Message #12 received at 18255 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Carlos Pita <carlosjosepita <at> gmail.com>
Cc: 18255 <at> debbugs.gnu.org
Subject: Re: bug#18255: Selecting a group with RET vs gnus-thread-hide-subtree
Date: Wed, 25 Jan 2017 20:15:27 +0100

Carlos Pita <carlosjosepita <at> gmail.com> writes:

> Selecting with RET is supposed not to select any article in the summary
> buffer. Nevertheless, if the first article in the summary is an
> unseen/unread article belonging to a thread, then that thread is
> expanded, even if gnus-thread-hide-subtree is t. To make things more
> confusing, the little > at the left fringe is shown in the last article
> of the summary, not the first.

I've never noticed that thing in the fringe.  :-)  What sets it?

> I think a more sensible behavior is:
>
> 1) Show the > at the article SPACE (as opposed to RET) would have
> selected, but without really selecting it.
>
> 2) Don't expand any thread at all (that is, when selecting the group
> with RET).
>
> Implementing just 1 will be a second best at least, because one can
> interpret this behavior as kinda "selecting without showing". But the
> current behavior is misleading: nothing seems to be selected, but there
> is an arrow pointing to the last article, despite the point is in the
> first one and the first thread is expanded => pretty messy.

Yes, I think 2) makes most sense.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #15 received at 18255 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Carlos Pita <carlosjosepita <at> gmail.com>
Cc: 18255 <at> debbugs.gnu.org
Subject: Re: bug#18255: Selecting a group with RET vs gnus-thread-hide-subtree
Date: Wed, 25 Jan 2017 20:33:38 +0100

Lars Ingebrigtsen <larsi <at> gnus.org> writes:

> Carlos Pita <carlosjosepita <at> gmail.com> writes:
>
>> Selecting with RET is supposed not to select any article in the summary
>> buffer. Nevertheless, if the first article in the summary is an
>> unseen/unread article belonging to a thread, then that thread is
>> expanded, even if gnus-thread-hide-subtree is t. To make things more
>> confusing, the little > at the left fringe is shown in the last article
>> of the summary, not the first.
>
> I've never noticed that thing in the fringe.  :-)  What sets it?

Found it.  Fixed.

>> I think a more sensible behavior is:
>>
>> 1) Show the > at the article SPACE (as opposed to RET) would have
>> selected, but without really selecting it.
>>
>> 2) Don't expand any thread at all (that is, when selecting the group
>> with RET).

I think the problem with 2) is when there's an unread article in the
first thread, but there are some read older articles...  we want to put
point on the first unread article, but to do that we have to expand the
thread.  In general.

So on second thought I'm not sure we want to do that.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.