From: Philip Kaludercic <philipk@posteo.net>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: 53897@debbugs.gnu.org
Subject: bug#53897: 28.0.91; regression: rcirc overwrites completion-cycle-threshold
Date: Mon, 14 Feb 2022 18:15:42 +0000 [thread overview]
Message-ID: <87bkz9co1d.fsf@posteo.net> (raw)
In-Reply-To: <d71a645f-8dff-b516-722e-ef79774b148c@daniel-mendler.de> (Daniel Mendler's message of "Wed, 9 Feb 2022 15:18:45 +0100")
Daniel Mendler <mail@daniel-mendler.de> writes:
>> The change that introduced this was that the custom cycling
>> implementation was replaced with one based on completion-at-point
>> (0b367ec), mainly to simplify the code. The reason
>> `completion-cycle-threshold' is set is to preserve the appearance of the
>> previous behaviour, as a complete reversion to completion-at-point
>> seemed like too much of a change.
>
> I agree with your change to remove rcirc-complete. I greatly appreciate
> the simplicity of rcirc and it is good that you try to make it even
> simpler! But rcirc-completion-at-point was already present as Capf on
> Emacs 27 and there `completion-at-point` didn't lead to cycling. I would
> not introduce a user configuration, it is easy enough to set
> completion-cycle-threshold in a hook.
Hmm, ok, I get your point. My rationale is that rcirc-complete (bound
to TAB) used to cycle, and that it was that behaviour that was supposed
to be preserved.
> Furthermore there is the alternative to use completion-category-defaults
> to specify the threshold per completion category. You could add the
> override there. But personally I would avoid doing that. I usually
> prefer if packages avoid intrusive and opinionated settings and instead
> try to ensure consistency across Emacs.
I agree.
>> I could imagine introducing a user option to decide what you want to
>> use. My inclination would be to set it to "cycle by default", but it
>> doesn't need that way. Perhaps we could test non-cycling (regular capf)
>> for a while, and see if there are any complaints or other feedback?
>
> Yes, I would go with normal Capf behavior, which is the usual behavior
> across all of Emacs. If a user wants to restore rcirc-complete, it seems
> easy enough to add this to a user configuration?
>
> (defun rcirc-complete ()
> (interactive)
> (let ((completion-cycle-threshold t))
> (completion-at-point)))
Or, this could be added as rcirc-complete, binding TAB back to this new
command and documenting that if you want to complete using the default
CAPF, you should rebind it to completion-at-point?
> Thanks!
--
Philip Kaludercic
next prev parent reply other threads:[~2022-02-14 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 11:10 bug#53897: 28.0.91; regression: rcirc overwrites completion-cycle-threshold Daniel Mendler
2022-02-09 12:54 ` Philip Kaludercic
2022-02-09 14:18 ` Daniel Mendler
2022-02-14 18:15 ` Philip Kaludercic [this message]
2022-02-14 18:18 ` Daniel Mendler
2022-02-14 18:33 ` Philip Kaludercic
2022-04-15 15:14 ` Philip Kaludercic
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=87bkz9co1d.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=53897@debbugs.gnu.org \
--cc=mail@daniel-mendler.de \
/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).