unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: Mac - why no proxy badge for dired mode?
Date: Mon, 06 Nov 2006 09:48:10 -0700	[thread overview]
Message-ID: <einp1m$g27$1@sea.gmane.org> (raw)
In-Reply-To: <m2k62b2oyz.fsf@cs.ucsd.edu>

Sean O'Rourke wrote:
> merlyn@stonehenge.com (Randal L. Schwartz) writes:
>> Ahh, actually, it seems to always represent *my* home directory.
>> So that's not working.  I should have tried more cases.
> 
> I've currently added
> 
>     (setq buffer-file-name dired-directory)
> 
> to dired-mode-hook, and that seems to do what you want.  Now to
> see what it breaks...

I suspect the case where dired-directory is a wildcard spec or a list
will cause problems.  Would default-directory be a good fallback for
mac_update_proxy_icon to use, when buffer-file-name is nil?

,----
| dired-directory is a variable defined in `dired.el'.
| Its value is nil
|
| Documentation:
| The directory name or wildcard spec that this dired directory lists.
| Local to each dired buffer.  May be a list, in which case the car is the
| directory name and the cdr is the list of files to mention.
| The directory name must be absolute, but need not be fully expanded.
|
| [back]
`----


-- 
Kevin

  reply	other threads:[~2006-11-06 16:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-02 20:13 Mac - why no proxy badge for dired mode? Randal L. Schwartz
2006-11-04  3:19 ` YAMAMOTO Mitsuharu
2006-11-04  8:05   ` Randal L. Schwartz
2006-11-04  9:10     ` Andreas Schwab
2006-11-04  9:12       ` Randal L. Schwartz
2006-11-04 10:54         ` YAMAMOTO Mitsuharu
2006-11-04 11:02           ` Randal L. Schwartz
2006-11-04 12:09             ` YAMAMOTO Mitsuharu
2006-11-04 14:00               ` Randal L. Schwartz
2006-11-04 14:16     ` Benjamin Riefenstahl
2006-11-04 14:53       ` Randal L. Schwartz
2006-11-04 15:47         ` Sean O'Rourke
2006-11-06 16:48           ` Kevin Rodgers [this message]
2006-11-07  0:58             ` YAMAMOTO Mitsuharu
2006-11-05  4:00       ` YAMAMOTO Mitsuharu

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='einp1m$g27$1@sea.gmane.org' \
    --to=ihs_4664@yahoo.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 public inbox

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

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).