unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Suvayu Ali'" <fatkasuvayu+linux@gmail.com>, <help-gnu-emacs@gnu.org>
Subject: RE: non noisy dired
Date: Sun, 7 Jun 2009 07:02:17 -0700	[thread overview]
Message-ID: <9A9A000218384909BF879106872DA265@us.oracle.com> (raw)
In-Reply-To: <4A2B01C0.20906@gmail.com>

> > http://www.emacswiki.org/emacs/DiredDetails
> > 
> > You'll never have to see anything other than the file name, 
> > unless you want to, and you can do that by hitting a toggle key.
>
> This is probably OT, but still. When you mentioned this extension I 
> tried out dired-details+.el. It works perfectly as expected 
> when I load it using `M-x load-library dired-details+'.
> 
> However if I put (require 'dired-details+) in my .emacs, I 
> get "Symbol's value as variable is void: dired-mode-map"
> 
> What am I doing wrong here? I am very new to emacs, just a 
> few months. So its very likely I could be missing something trivial.

No, you were not doing anything wrong.
Here's the explanation (it was a bug):

(require 'dired-details+) loads dired-details+, which in turn does (require
'dired-details), which loads dired-details.

But neither explicitly loads dired, which is where variable `dired-mode-map' is
defined. After it loads dired-details, dired-details+ tries to use that variable
at load time --> error.

Should be fixed now. The fix is to use the variable not at load time, but after
dired is loaded.

Thx - Drew

P.S. Two years ago, the author of dired-details.el, Rob Giardina, integrated all
of the dired-details.el and dired-details+.el features into Emacs - he submitted
a comprehensive patch. The Emacs developers seemed to agree to this addition,
but they never followed up, so it never happened. I've ping'ed them several
times about it (the last time was 2008-11-12), with zero response. Too bad.
Rob's integration was clean, avoiding the `defadvice' and other hoops that these
two libraries jump through.





  reply	other threads:[~2009-06-07 14:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04 14:18 non noisy dired Rustom Mody
2009-06-05  3:28 ` Eli Zaretskii
2009-06-05  4:37 ` Drew Adams
2009-06-06 23:54   ` Suvayu Ali
2009-06-07 14:02     ` Drew Adams [this message]
2009-06-07 15:00       ` Thien-Thi Nguyen
2009-06-07 15:42         ` Drew Adams
2009-06-07 15:18       ` Suvayu Ali
2009-06-07 15:56       ` Suvayu Ali
2009-06-07 16:21         ` Drew Adams
2009-06-07 16:49           ` Suvayu Ali
     [not found]           ` <mailman.168.1244402670.2239.help-gnu-emacs@gnu.org>
2009-06-08 14:20             ` rustom
2009-06-08 15:18               ` Drew Adams
     [not found]               ` <mailman.217.1244474339.2239.help-gnu-emacs@gnu.org>
2009-06-09  7:03                 ` rustom
     [not found] ` <mailman.36.1244176697.2239.help-gnu-emacs@gnu.org>
2009-06-05 12:50   ` rustom
2009-06-05 15:25     ` Drew Adams

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=9A9A000218384909BF879106872DA265@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=fatkasuvayu+linux@gmail.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).