From: David Rogoff <david@therogoffs.com>
To: help-gnu-emacs@gnu.org
Subject: Re: find-file-at-point expanding environment variables?
Date: Tue, 13 Apr 2010 17:31:29 -0700 [thread overview]
Message-ID: <4bc50ce1$0$30266$c32e2966@unlimited.newshosting.com> (raw)
In-Reply-To: 4bc4f717$0$6037$c39e29d6@unlimited.newshosting.com
On 2010-04-13 15:58:31 -0700, David Rogoff said:
> I could use some help. I use ffap (bound to c-x c-f) all the time.
> However, I edit many files in which there are references to filenames
> that use shell environment variables as part of the path. For example
> - /home/${USER}/.cshrc . Is there a way for ffap to expand/substitute
> this? It would make my life a lot easier.
I did some experimenting and see that ffap will expand variables ...
except if they are enclosed in curly braces. This isn't too bad a
limitation, but it would be better if I didn't have to edit the files
and remove the curly braces.
David
next prev parent reply other threads:[~2010-04-14 0:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 22:58 find-file-at-point expanding environment variables? David Rogoff
2010-04-14 0:31 ` David Rogoff [this message]
2010-04-14 9:31 ` Andreas Politz
2010-04-14 17:38 ` David Rogoff
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='4bc50ce1$0$30266$c32e2966@unlimited.newshosting.com' \
--to=david@therogoffs.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).