From: Enselic <enselic@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Make dabbrev-expand work like Bash file-name completion?
Date: Sat, 30 Jun 2007 04:43:08 -0700 [thread overview]
Message-ID: <1183203788.289804.198350@w5g2000hsg.googlegroups.com> (raw)
In-Reply-To: <yoijlke1ya6r.fsf@remote5.student.chalmers.se>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 317 bytes --]
On 30 Juni, 13:05, bojohan+n...@dd.chalmers.se (Johan Bockgård) wrote:
> Enselic <ense...@gmail.com> writes:
> > I would like a second M-/ to put some_func_foo, some_func_bar,
> > some_func_another in *Completions*
>
> Use C-M-/
>
> --
> Johan Bockgård
Wow, that was an easy solution. Thanks!
- Martin
prev parent reply other threads:[~2007-06-30 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 8:50 Make dabbrev-expand work like Bash file-name completion? Enselic
2007-06-30 11:05 ` Johan Bockgård
2007-06-30 11:43 ` Enselic [this message]
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=1183203788.289804.198350@w5g2000hsg.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).