From: Mathias Dahl <mathias.dahl@gmail.com>
Subject: Re: Using w32's find file dialog from the keyboard
Date: Sat, 12 Aug 2006 02:14:28 +0200 [thread overview]
Message-ID: <m2lkpukdy3.fsf@gmail.com> (raw)
In-Reply-To: mailman.5087.1155312944.9609.help-gnu-emacs@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
> . Cheat:
>
> (let (last-nonmenu-event)
> (call-interactively 'find-file))
This sounds like the solution my friend wanted. I guess I could just
make that a command and bind it to some key, right?
> Out of curiosity: why would you wish to open the file selector so
> badly?
I don't :) This is for a friend that decided to give Emacs a second
try. I guess he want to make the switch gradually (I suggested he use
CUA-mode to begin with because he was put off too much by Emacs
"non-Windows-standard" bindings).
Thanks!
prev parent reply other threads:[~2006-08-12 0:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 13:40 Using w32's find file dialog from the keyboard Mathias Dahl
2006-08-11 14:59 ` Drew Adams
2006-08-11 15:49 ` B. T. Raven
2006-08-12 0:11 ` Mathias Dahl
2006-08-11 16:15 ` Eli Zaretskii
2006-08-11 23:42 ` Reiner Steib
[not found] ` <mailman.5087.1155312944.9609.help-gnu-emacs@gnu.org>
2006-08-12 0:14 ` Mathias Dahl [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=m2lkpukdy3.fsf@gmail.com \
--to=mathias.dahl@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.
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).