unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>,
	75305@debbugs.gnu.org, Andrew G Cohen <cohen@andy.bu.edu>
Subject: bug#75305: 31.0.50; gnus-refer-thread-use-search isn't exact enough about how the current group is searched
Date: Sun, 05 Jan 2025 22:33:59 +0200	[thread overview]
Message-ID: <19076.2791711435$1736109323@news.gmane.org> (raw)
In-Reply-To: <86wmf9ai4k.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 05 Jan 2025 08:29:15 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Björn Bidar <bjorn.bidar@thaodan.de>
>> Cc: 75305@debbugs.gnu.org
>> Date: Sat, 04 Jan 2025 23:34:10 +0200
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > Thanks, but the patch seems to include unrelated changes in the code?
>> > I thought we were talking only about fixing the manual?  Or what did I
>> > miss?
>> >
>> 
>> I look at the situation further and noticed that adding the current
>> group does not work without the user writing a custom hook to add it.
>> I already wrote a hook to change gnus-refer-thread-use-search for
>> another reason, to add the current gnus-message-archive-group to 
>> gnus-refer-thread-use-search.
>> To just add the current group writing a hook would be to clumsy.
>> Using the current symbol similar as in gnus-refer-article-method is much
>> simpler, makes the setting easier to understand and customize for new 
>> users.
>> 
>> The customization changes are there to use better custom types which
>> makes it easier to customize and harder to put false values into the
>> option when using custom.
>
> Then we'll need to wait for our Gnus expert (CC'ed) to review your
> code changes.  I have some comments to the documentation part below:

OK great. 

>> * lisp/gnus/gnus-sum.el (gnus-refer-thread-use-search):
>> Make it easier to customize the variable by adding predefine choices
>> as well as descriptions to each choice. Add option to add the value
>> `current' to the list of servers and groups to add the current group.
>> E.g. to add another group and the current group.
>> * lisp/gnus/gnus-search.el (gnus-refer-thread-maybe-add-current-group,
>> gnus-search-thread): Add helper function to determine if the option
>> contains the value current. Use helper function.
>> * lisp/gnus/nnselect.el (nnselect-request-thread): Use helper function
>> to check if the value current is in gnus-refer-thread-use-search.
>> * doc/misc/gnus.texi (gnus-refer-thread-use-search):
>> Include the current value in the section. Format the section a little
>> better to have a paragraph for each possible value that the option
>> may contain. Explain the option to have a list of servers more detailed
>> , i.e. similarly to the custom description. Highlight that the current
>> group is not searched unless specified. Explain that unless the articles
>> of that thread are contained in the searched groups not adding the
>> current group might not be the desired effect.
>
> Some of the lines in the log message are too long.  Please be sure to
> wrap lines at column 64 if possible, and in any case before column 70.
>

I did so but it does make the message harder to read when long function
or variable names come into play.

The grammar errors you noticed are fixed. I also applied the suggested
changes to the docstring of the new function.





  reply	other threads:[~2025-01-05 20:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87wmfclrf0.fsf@>
2025-01-03  8:16 ` bug#75305: 31.0.50; gnus-refer-thread-use-search isn't exact enough about how the current group is searched Eli Zaretskii
2025-01-03 20:33   ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]   ` <87o70nd4dd.fsf@>
2025-01-04 13:26     ` Eli Zaretskii
2025-01-04 21:34       ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]       ` <87bjwmw9f1.fsf@>
2025-01-05  6:29         ` Eli Zaretskii
2025-01-05 20:33           ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
     [not found]           ` <87o70lt2yw.fsf@>
2025-01-05 20:36             ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-02 23:36 Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors

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='19076.2791711435$1736109323@news.gmane.org' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=75305@debbugs.gnu.org \
    --cc=bjorn.bidar@thaodan.de \
    --cc=cohen@andy.bu.edu \
    --cc=eliz@gnu.org \
    --cc=eric@ericabrahamsen.net \
    /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).