unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Enselic <enselic@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Make dabbrev-expand work like Bash file-name completion?
Date: Sat, 30 Jun 2007 01:50:28 -0700	[thread overview]
Message-ID: <1183193428.456090.136770@q75g2000hsh.googlegroups.com> (raw)

Hello,

Mx dabbrev-expand RET does exactly what I want, with one exception. It
does not make completions like bash does.

If I have

  some_func_foo
  some_func_bar
  some_func_another

in a buffer, and do

  some_fu M-/

it will complete to

  some_func_another

instead of

  some_func_

I would like a second M-/ to put some_func_foo, some_func_bar,
some_func_another in *Completions*, and then doing f M-/ would expand
to

  some_func_foo

just like bash.

Does anyone know of elisp that accomplishes this?

Thank you,
- Martin Nordholts

             reply	other threads:[~2007-06-30  8:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-30  8:50 Enselic [this message]
2007-06-30 11:05 ` Make dabbrev-expand work like Bash file-name completion? Johan Bockgård
2007-06-30 11:43   ` Enselic

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=1183193428.456090.136770@q75g2000hsh.googlegroups.com \
    --to=enselic@gmail.com \
    --cc=help-gnu-emacs@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.
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).