From: "Bourgneuf Francois" <francois.bourgneuf@groupe-mma.fr>
To: <help-gnu-emacs@gnu.org>
Subject: RE: hippie-expand show possible expansions for files
Date: Wed, 7 Nov 2007 16:27:53 +0100 [thread overview]
Message-ID: <8A921A5AACA1A64F936C730FC1F8172101185F92@zw67246c.societe.mma.fr> (raw)
> -----Message d'origine-----
> De :
> help-gnu-emacs-bounces+francois.bourgneuf=groupe-mma.fr@gnu.or
> g
> [mailto:help-gnu-emacs-bounces+francois.bourgneuf=groupe-mma.f
> r@gnu.org] De la part de Thierry Volpiatto
> Envoyé : mardi 6 novembre 2007 23:52
> À : f.braennstroem@gmx.de
> Cc : help-gnu-emacs@gnu.org
> Objet : Re: hippie-expand show possible expansions for files
>
> Fabian Braennstroem <f.braennstroem@gmx.de> writes:
>
> > Hi Thierry,
> >
> > Thierry Volpiatto wrote:
> >
> >> Fabian Braennstroem <f.braennstroem@gmx.de> writes:
> >>
> >>> Hi,
> >>>
> >>> does anyone know, if there is a chance to show all
> possible expansions
> >>> for file names and directories when using hippie-expand?
> Something like
> >>> 'comint-dynamic-complete' does!? Would be nice...
> >>
> >> Hi, yes for me it work, i bind it to C-c p.
> >
> > I was not clear enough, I can you hippie-expand too, but I
> don't get a
> > buffer jumping up with all possible expansion. I think it would be a
> > realy nice feature!?
> > Fabian
> >
> Hi Fabian,
> i have the buffer with all the possible completions if i do C-c p
> 2 times :)
> (only if comint-dynamic-complete find more than one possible
> completion)
>
> --
> A + Thierry
> pubkey: http://pgp.mit.edu/
>
>
> _______________________________________________
> help-gnu-emacs mailing list
> help-gnu-emacs@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
>
>
Hi,
I didn't know these completion features, I find them very handy.
Do you know if there is a way to manage file name completion even if a directory contains a whitespace.
I work under Windows and neither hippie-expand nor comint-dynamic-complete could expand anything after c:\program Files
Thank you
Bour9
next reply other threads:[~2007-11-07 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 15:27 Bourgneuf Francois [this message]
2007-11-07 16:03 ` hippie-expand show possible expansions for files Thierry Volpiatto
2007-11-07 16:44 ` Peter Dyballa
2007-11-07 18:30 ` Thierry Volpiatto
[not found] ` <mailman.3095.1194453900.18990.help-gnu-emacs@gnu.org>
2007-11-07 21:19 ` Fabian Braennstroem
-- strict thread matches above, loose matches on Subject: below --
2007-11-06 19:52 Fabian Braennstroem
2007-11-06 20:02 ` Thierry Volpiatto
[not found] ` <mailman.3056.1194379207.18990.help-gnu-emacs@gnu.org>
2007-11-06 21:14 ` Fabian Braennstroem
2007-11-06 22:51 ` Thierry Volpiatto
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=8A921A5AACA1A64F936C730FC1F8172101185F92@zw67246c.societe.mma.fr \
--to=francois.bourgneuf@groupe-mma.fr \
--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).