From: Carlos Pita <carlosjosepita@gmail.com>
To: 31906@debbugs.gnu.org
Subject: bug#31906: 26.1.50; Properly set completion-at-point-functions in eshell
Date: Tue, 19 Jun 2018 23:59:29 -0300 [thread overview]
Message-ID: <CAELgYhcjOCdEiE+n8SxabGUk6v3f2Ro-sduxunuwhMO13P320g@mail.gmail.com> (raw)
In-Reply-To: <CAELgYhcmLn4UqCmRe8p3ukT8r6srn7Suh5XFjVUm+MwAa1K7TQ@mail.gmail.com>
Mmmh it seems to be that it's overriding the default
pcomplete-completions-at-point. But then why is this default set at
all? <Tab> is directly bound to eshell-pcomplete, a simple wrapper
around pcomplete, which AFAICS doesn't rely on
completion-at-point-functions. But there is this workaround for
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=12838 in the final line
of eshell-pcomplete:
(defun eshell-pcomplete (&optional interactively)
"Eshell wrapper for `pcomplete'."
(interactive "p")
;; Pretend to be pcomplete so that cycling works (bug#13293).
(setq this-command 'pcomplete)
(condition-case nil
(if interactively
(call-interactively 'pcomplete)
(pcomplete))
(text-read-only (completion-at-point)))) ; Workaround for bug#12838.
Although I don't fully understand the workaround.
So to sum up, what I would have expected is:
1. completion-at-point-functions contains only elisp-completions-at-point.
2. M-<Tab> is bound to completion-at-point.
3. <Tab> is bound to a wrapper to pcomplete (that doesn't call
completion-at-point).
All these expectations are violated.
next prev parent reply other threads:[~2018-06-20 2:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 2:34 bug#31906: 26.1.50; Properly set completion-at-point-functions in eshell Carlos Pita
2018-06-20 2:40 ` Carlos Pita
2018-06-20 2:59 ` Carlos Pita [this message]
2018-06-20 3:38 ` Carlos Pita
2019-10-03 2:14 ` 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=CAELgYhcjOCdEiE+n8SxabGUk6v3f2Ro-sduxunuwhMO13P320g@mail.gmail.com \
--to=carlosjosepita@gmail.com \
--cc=31906@debbugs.gnu.org \
/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.