From: Lars Ingebrigtsen <larsi@gnus.org>
To: Barry Warsaw <barry@python.org>
Cc: 11360@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#11360: Case sensitive ERC nick completion regression
Date: Thu, 04 Feb 2016 17:45:36 +1100 [thread overview]
Message-ID: <87lh71ynvz.fsf@gnus.org> (raw)
In-Reply-To: <20160112140239.7a78def9@limelight.wooz.org> (Barry Warsaw's message of "Tue, 12 Jan 2016 14:02:39 -0500")
Barry Warsaw <barry@python.org> writes:
> On Dec 27, 2015, at 10:26 PM, Lars Ingebrigtsen wrote:
>
>>When I try to do nick completion in erc now, it seems like it's case
>>sensitive again, so I think it probably worked. And I'm closing this
>>report.
>
> Sorry, I don't understand. I want case-insensitive completion of nicks.
Sorry; I misread your message.
I've now been following the completion code down the rabbit hole, and
via approx. 23 indirections, the completion is actually done by
`try-completions'. And that respects the `completion-ignore-case'
variable.
However, TAB is bound to `completion-at-point', which does not allow any
way to have that variable be bound. So I think we'll just have to bind
TAB to an erc function that binds that variable, and then call
`completion-at-point'.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-02-04 6:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 13:38 bug#11360: ERC completion case-sensitive Antoine Levitt
2012-05-05 3:11 ` Stefan Monnier
2012-05-05 7:49 ` Antoine Levitt
2016-02-05 13:38 ` Stefan Monnier
2016-02-06 3:17 ` Lars Ingebrigtsen
2016-02-06 14:06 ` Stefan Monnier
2013-07-01 12:52 ` bug#11360: Case sensitive ERC nick completion regression Barry Warsaw
2013-07-30 20:46 ` Stefan Monnier
2015-12-27 21:26 ` Lars Ingebrigtsen
2016-01-12 19:02 ` Barry Warsaw
2016-02-04 6:45 ` Lars Ingebrigtsen [this message]
2016-02-05 19:08 ` Barry Warsaw
2014-09-11 19:31 ` bug#11360: (no subject) Carlos Pita
2014-09-11 19:58 ` bug#11360: none Carlos Pita
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=87lh71ynvz.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=11360@debbugs.gnu.org \
--cc=barry@python.org \
--cc=monnier@iro.umontreal.ca \
/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).