From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Leo Liu <sdl.web@gmail.com>
Cc: 14300@debbugs.gnu.org
Subject: bug#14300: 24.3; comint-dynamic-complete-functions breaks
Date: Sun, 05 May 2013 22:38:34 -0400 [thread overview]
Message-ID: <jwvli7sj0ur.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m1mws9lxie.fsf@gmail.com> (Leo Liu's message of "Sun, 05 May 2013 15:02:49 +0800")
>> Good question. Can file names really occur at the same places as
>> function names in Octave?
> F("arg1", "arg2", ...) can be written as F arg1 arg2 ... in octave. For
> example 'help sin' and 'cd /usr'.
> So there is no clear way to detect whether a position is file-completion
> or function-completion given the fact that user can define a function
> that does do both in the same position.
While there are cases where there is ambiguity, there are many where the
ambiguity can be lifted:
You could prevent function completion within a string, so file name
completion still won't work after 'cd /u' but it will after 'cd "/u'.
Similarly you might disable function completion if the "current function
name" includes a / (assuming real functions don't include a slash in
their name).
In the worst case, you might want to use ":exclusive t", tho it means that
function completion won't be able to benefit from fancier completion styles.
Stefan
next prev parent reply other threads:[~2013-05-06 2:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 6:39 bug#14300: 24.3; comint-dynamic-complete-functions breaks Leo Liu
2013-05-04 20:08 ` Stefan Monnier
2013-05-05 1:55 ` Leo Liu
2013-05-05 6:39 ` Stefan Monnier
2013-05-05 7:02 ` Leo Liu
2013-05-06 2:38 ` Stefan Monnier [this message]
2013-05-06 3:40 ` Leo Liu
2013-05-06 13:32 ` Stefan Monnier
2013-05-07 8:18 ` Leo Liu
2013-05-10 1:21 ` Leo Liu
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=jwvli7sj0ur.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=14300@debbugs.gnu.org \
--cc=sdl.web@gmail.com \
/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).