all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Edward O'Connor <oconnor@soe.ucsd.edu>
Subject: Re: Looking for a package filename expansion in a buffer (ala dabbrev)
Date: Mon, 05 May 2003 10:13:49 -0700	[thread overview]
Message-ID: <ddfzntpb8y.fsf@oecpc11.ucsd.edu> (raw)
In-Reply-To: 2bd747c7.0305050849.497d36e1@posting.google.com

> I'm just looking for a package that will let me expand filenames when
> I'm inside a buffer.
> 
>    e.g.  I'd be typing /a/path/to<KEY>
> 
> and KEY would expand (or give me options) the path/filename
> 
>    /a/path/to/a/unique/file
> 
> or something like that.

Maybe M-x comint-dynamic-complete-filename RET does what you want?

,----[ C-h f comint-dynamic-complete-filename RET ]
| comint-dynamic-complete-filename is an interactive compiled Lisp function in `comint'.
| (comint-dynamic-complete-filename)
| 
| Dynamically complete the filename at point.
| Completes if after a filename.  See `comint-match-partial-filename' and
| `comint-dynamic-complete-as-filename'.
| This function is similar to `comint-replace-by-expanded-filename', except that
| it won't change parts of the filename already entered in the buffer; it just
| adds completion characters to the end of the filename.  A completions listing
| may be shown in a help buffer if completion is ambiguous.
| 
| Completion is dependent on the value of `comint-completion-addsuffix',
| `comint-completion-recexact' and `comint-completion-fignore', and the timing of
| completions listing is dependent on the value of `comint-completion-autolist'.
| 
| Returns t if successful.
`----



Ted

-- 
Edward O'Connor
oconnor@soe.ucsd.edu

  reply	other threads:[~2003-05-05 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-05 16:49 Looking for a package filename expansion in a buffer (ala dabbrev) bigfaceworm
2003-05-05 17:13 ` Edward O'Connor [this message]
2003-05-05 17:53 ` Martin Lorentzson
2003-05-06  7:34 ` Klaus Berndl

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=ddfzntpb8y.fsf@oecpc11.ucsd.edu \
    --to=oconnor@soe.ucsd.edu \
    /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.