all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: dkcombs@panix.com (David Combs)
To: help-gnu-emacs@gnu.org
Subject: Re: shouldn't m-x pwd on *Occur* be SAME DIR as for the file it's ABOUT?
Date: Mon, 12 Apr 2010 05:24:23 +0000 (UTC)	[thread overview]
Message-ID: <hpuaq6$eip$3@reader1.panix.com> (raw)
In-Reply-To: hom1m8$lt4$1@panix3.panix.com

In article <hom1m8$lt4$1@panix3.panix.com>,
David Combs <dkcombs@panix.com> wrote:
>I was surprised today when I did a M-x pwd on *Occur*, and
>it said my home directory, whereas the file I was doing
>the M-x occur on was in a *different* directory.
>
>I don't recall this behavior from the past -- or maybe I'm
>just doing something wrong?
>
>FYI: 
>
>    NTEMACS: [ GNU Emacs 23.0.0.1 (i386-mingw-nt5.1.2600) of 2007-08-18 on TPAD ]
>
>Thanks!
>
>David
>
>

No replies?

If Occur was changed so that *Occur* would "be" in
the *same* directory as what Occur was searching
through?

So that if you saw something interesting in *Occur*,
you could say C-x d and end up in the most likely
directory you'd WANT to end up in?  (Assuming the buffer
being searched by Occur had a file attached to it,
that is...)

It just seems weird, the way it works now.

Thanks,

David




  reply	other threads:[~2010-04-12  5:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-27 22:43 shouldn't m-x pwd on *Occur* be SAME DIR as for the file it's ABOUT? David Combs
2010-04-12  5:24 ` David Combs [this message]
2010-04-12 16:19   ` Stefan Monnier
2010-05-04 19:59 ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2010-04-21  5:41 Shouldn't " David Combs
2010-04-21 17:42 ` Andreas Politz
2010-04-21 18:24 ` Stefan Monnier
2010-05-05  3:15   ` Eli Zaretskii
     [not found]   ` <mailman.59.1273030257.29092.help-gnu-emacs@gnu.org>
2010-05-05 20:36     ` Stefan Monnier
2010-05-06  3:12       ` Eli Zaretskii

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='hpuaq6$eip$3@reader1.panix.com' \
    --to=dkcombs@panix.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.
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.