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 22:02:40 -0500 [thread overview]
Message-ID: <AANLkTinp7xbT2udVDr7AaMmbmsXS93KjdvB1cT_4uxnR@mail.gmail.com> (raw)
In-Reply-To: <jwvvd3gud2y.fsf-monnier+emacs@gnu.org>
On Sun, Nov 28, 2010 at 8:35 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>> No need to defend that text; just use "buffer `*Completions*'" or
>> "window `*Completions*'" (depending on the context).
>
> I'd argue instead that there is no reason for that text to say where
> it's going to be displayed.
Once one has left the immediate locus of the `comint-*' callers it is
good to know
what/where these gals do their business.
> So I'd replace "List in help buffer sorted completions" with something
> like "Display sorted completions".
OK. It makes sense to leave from for future changes.
But, there is third party code that uses this feature:
Their users may deserve some consideration...
`slime-maybe-complete-as-filename'
`-> `comint-replace-by-expanded-filename'
`-> `comint-dynamic-complete-filename'
`-> `comint-dynamic-complete-as-filename'
`-> `comint-dynamic-list-filename-completions'
`-> `comint-dynamic-list-completions'
Do an occur for "slime-complete-*" in slime.el
Also, take a look at `slime-completions-buffer-name'.
I'm sure there are other non-core libs which make similar use of `comint-*'...
> Stefan
--
/s_P\
next prev parent reply other threads:[~2010-11-29 3:02 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
2010-11-28 22:42 ` Drew Adams
2010-11-29 1:35 ` Stefan Monnier
2010-11-29 3:02 ` MON KEY [this message]
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
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=AANLkTinp7xbT2udVDr7AaMmbmsXS93KjdvB1cT_4uxnR@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 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).