From: Ronald <followait@163.com>
Subject: good, thanks
Date: Tue, 12 Dec 2006 11:00:52 +0800 [thread overview]
Message-ID: <ell614$ofk$2@news.yaako.com> (raw)
In-Reply-To: <mailman.1778.1165889144.2155.help-gnu-emacs@gnu.org>
Leo wrote:
> * [2006.12.12 08:45 +0800] Ronald wrote:
> ^^^^^^
>> C-x C-f
>> then I want to delete the path in the mini window,
>> how to do it quickly?
>
> ,----[ (info "(emacs)File Names") ]
> | Note that it is legitimate to type an absolute file name after you
> | enter the minibuffer, ignoring the presence of the default directory
> | name as part of the text. The final minibuffer contents may look
> | invalid, but that is not so. For example, if the minibuffer starts out
> | with `/usr/tmp/' and you add `/x1/rms/foo', you get
> | `/usr/tmp//x1/rms/foo'; but Emacs ignores everything through the first
> | slash in the double slash; the result is `/x1/rms/foo'. *Note
> | Minibuffer File::.
> |
> | You can use `~/' in a file name to mean your home directory, or
> | `~USER-ID/' to mean the home directory of a user whose login name is
> | `user-id'(1).
> |
> | `$' in a file name is used to substitute an environment variable.
> | The environment variable name consists of all the alphanumeric
> | characters after the `$'; alternatively, it can be enclosed in braces
> | after the `$'. For example, if you have used the shell command `export
> | FOO=rms/hacks' to set up an environment variable named `FOO', then you
> | can use `/u/$FOO/test.c' or `/u/${FOO}/test.c' as an abbreviation for
> | `/u/rms/hacks/test.c'. If the environment variable is not defined, no
> | substitution occurs: `/u/$notdefined' stands for itself (assuming the
> | environment variable `notdefined' is not defined).
> `----
>
next prev parent reply other threads:[~2006-12-12 3:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 0:45 How to delete the path in mini window when finding a file quickly Ronald
2006-12-12 2:05 ` Leo
[not found] ` <mailman.1778.1165889144.2155.help-gnu-emacs@gnu.org>
2006-12-12 3:00 ` Ronald [this message]
2006-12-12 9:24 ` Mathias Dahl
2006-12-12 14:01 ` Ken Goldman
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='ell614$ofk$2@news.yaako.com' \
--to=followait@163.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).