all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: William Case <billlinux@rogers.com>
To: "Sebastian P. Luque" <spluque@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Changing working Directory useing abbrev ?? -- [SOLVED]
Date: Mon, 30 Apr 2007 01:31:51 -0400	[thread overview]
Message-ID: <1177911111.3152.161.camel@CASE> (raw)
In-Reply-To: <87fy6io7wj.fsf@patagonia.sebmags.homelinux.org>

Thanks Sebastion;

I finally figured out how it works.

On Sun, 2007-04-29 at 22:31 -0500, Sebastian P. Luque wrote:
> On Sun, 29 Apr 2007 13:00:44 -0400,
> William Case <billlinux@rogers.com> wrote:
> 
> [...]
> 
> > How can I use my path abbrevs to change to a new pwd??
> 
> > Oh, by the way, I have googled and info-ed indeed.  I am still not used
> > to using all the correct search criteria, so the explanation is there
> > somewhere I am sure, but I can't find it.
> 
> I'm not familiar with such directory abbreviations, but for this
> functionality I like bookmarks; 'C-x r m' for creating a new one
> (e.g. dired buffers), 'C-x r b' for jumping to one.  Have a look.
> 

It's not intuitive to me but it works.  I wanted to set a new pwd before
visiting files or creating new ones.  You know, set it up before I start
working and then be free to bop around and know I will always get back
to my working directory.

I now I see I can do that with 'find-file' and directory-abbrev-alist +
bookmarks.  I still feels counter-intuitive but I'll get used to it.

I believe I might be able to create environmental constants and use cd
$CONSTANT, but that seems like more trouble than it is worth.

Thanks for your tip -- it got me re-thinking the whole thing.

-- 
Regards Bill

      reply	other threads:[~2007-04-30  5:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-29 17:00 Changing working Directory useing abbrev ?? William Case
2007-04-30  3:31 ` Sebastian P. Luque
2007-04-30  5:31   ` William Case [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1177911111.3152.161.camel@CASE \
    --to=billlinux@rogers.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=spluque@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.