From: Vivek Dasmohapatra <vivek@etla.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 15362@debbugs.gnu.org
Subject: bug#15362: 24.1; pcomplete unnecessarily restricts tab-completion entry points
Date: Fri, 13 Sep 2013 13:29:13 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.00.1309131319180.7157@octopus.pepperfish.net> (raw)
In-Reply-To: <jwvmwnhs8jp.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1371 bytes --]
> So if cycling is to take place, it should presumably not be done by
> pcomplete but by completion-at-point (e.g. obeying
> completion-cycle-threshold).
>
> IOW, I don't understand how your patch can fix your problem.
> Can you provide a reproducible recipe starting from "emacs -Q"?
emacs -Q
customise the erc group, make sure erc-pcomplete is on (it
should be)
customise erc-complete-functions, add erc-pcomplete to
the head of that list
M-x erc RET … ; connect to freenode, enter #emacs
j TAB ; big list of nicks beginning with jpops up
l TAB ; unconditionally completes to whichever jl… nick
; was at the head of the list.
Analaysis:
TAB → completion-at-point
completion-at-point → completion-at-point-functions
completion-at-point-functions → erc-complete-word-at-point
erc-complete-word-at-point →
(run-hook-with-args-until-success 'erc-complete-functions)
erc-complete-functions → erc-pcomplete
erc-pcomplete → (call-interactively 'pcomplete)
pcomplete →
(memq last-command '(pcomplete
pcomplete-expand-and-complete
pcomplete-reverse)
The above test controls entry into the cycling code.
next prev parent reply other threads:[~2013-09-13 12:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 2:15 bug#15362: 24.1; pcomplete unnecessarily restricts tab-completion entry points Vivek Dasmohapatra
2013-09-13 3:35 ` Stefan Monnier
2013-09-13 12:29 ` Vivek Dasmohapatra [this message]
2013-09-13 13:32 ` Stefan Monnier
2013-09-13 13:50 ` Vivek Dasmohapatra
2013-09-13 15:17 ` Stefan Monnier
2013-09-14 0:00 ` Vivek Dasmohapatra
2013-09-13 14:03 ` Vivek Dasmohapatra
2019-09-30 14:39 ` Stefan Kangas
2019-10-30 20:54 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.00.1309131319180.7157@octopus.pepperfish.net \
--to=vivek@etla.org \
--cc=15362@debbugs.gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.