From: MON KEY <monkey@sandpframing.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 7499@debbugs.gnu.org
Subject: bug#7499: Documentation: `comint-dynamic-list-filename-completions'
Date: Sun, 28 Nov 2010 15:46:58 -0500 [thread overview]
Message-ID: <AANLkTinqZ9xE0q1WYvQc=8koCeUORVZHZmL1RkL7x70y@mail.gmail.com> (raw)
In-Reply-To: <jwvoc9ay5s3.fsf-monnier+emacs@gnu.org>
On Sat, Nov 27, 2010 at 1:35 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
> The term "help buffer" is apparently used here loosely to mean
> "auxiliary buffer helpful to the user".
>
Its less than apparent (to me at least) that such loose usage is helpful. :)
AFAICT `comint-dynamic-list-completions' is hardwired to "*Completions*".
Its docstring is equally suspect:
,---- (documentation 'comint-dynamic-list-completions)
|
| List in help buffer sorted completions. The meaning of
| common-substring is the same as in `display-completion-list'.
| Typing SPC flushes the help buffer.
|
`----
W/re `comint-dynamic-list-completions',
`comint-dynamic-list-filename-completions' (and any other similar such
comint docstrings), what would prob. be more "helpful to the user"
would be to explicitly document that return value is to
"*Completions*". :)
After all, there is no provision for an alternative destination
stream. Indeed, it is doubtful such alternatives could be made
available via `comint-dynamic-list-completions' given the complicated
interactions between windows/buffers/configurations and the dynamic bindings of
`standard-output' happening around the internal calls to
`display-completion-list' and `with-output-to-temp-buffer'.
> Stefan
--
/s_P\
next prev parent reply other threads:[~2010-11-28 20:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 17:10 bug#7499: Documentation: `comint-dynamic-list-filename-completions' MON KEY
2010-11-27 18:35 ` Stefan Monnier
2010-11-28 20:46 ` MON KEY [this message]
2010-11-28 22:42 ` Drew Adams
2010-11-29 1:35 ` Stefan Monnier
2010-11-29 3:02 ` MON KEY
2010-12-05 0:55 ` Chong Yidong
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='AANLkTinqZ9xE0q1WYvQc=8koCeUORVZHZmL1RkL7x70y@mail.gmail.com' \
--to=monkey@sandpframing.com \
--cc=7499@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.