unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: 18255@debbugs.gnu.org
Subject: bug#18255: Selecting a group with RET vs gnus-thread-hide-subtree
Date: Wed, 25 Jan 2017 20:15:27 +0100	[thread overview]
Message-ID: <87ziiflzn4.fsf@gnus.org> (raw)
In-Reply-To: <84r40lfksg.fsf@gmail.com> (Carlos Pita's message of "Tue, 12 Aug 2014 18:41:19 -0300")

Carlos Pita <carlosjosepita@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





       reply	other threads:[~2017-01-25 19:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <84r40lfksg.fsf@gmail.com>
2017-01-25 19:15 ` Lars Ingebrigtsen [this message]
2017-01-25 19:33   ` bug#18255: Selecting a group with RET vs gnus-thread-hide-subtree Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ziiflzn4.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=18255@debbugs.gnu.org \
    --cc=carlosjosepita@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).