Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!husc6!yale!Ram-Ashwin
From: Ram-Ashwin@cs.yale.edu (Ashwin Ram)
Newsgroups: comp.emacs
Subject: Re: Selective Dired
Message-ID: <50660@yale-celray.yale.UUCP>
Date: 15 Feb 89 01:41:31 GMT
References: <5318@lifia.imag.fr> <35981@bbn.COM> <50608@yale-celray.yale.UUCP> <36009@bbn.COM>
Sender: root@yale.UUCP
Reply-To: Ram-Ashwin@cs.yale.edu (Ashwin Ram)
Organization: Computer Science, Yale University, New Haven, CT 06520-2158
Lines: 17
In-reply-to: mesard@bbn.com (Wayne Mesard)

In article <36009@bbn.COM>, mesard@bbn.com (Wayne Mesard) writes:
> In article <50608@yale-celray.yale.UUCP> Ram-Ashwin@cs.yale.edu (Ashwin Ram) writes:
> >prefer to be able to specify a list of dired-ignored-extensions, similar to
> >completion-ignored-extensions, once and for all.  It's easier to ^X^F a
> >directory to enter dired instead of typing M-x dired {core,Makefile,*.[ch]}
> >each time.
> 
> Agreed, but would you really want to ignore the same exact file name
> patterns *all the time*?  Or more would you have two or three complex
> patterns which are each called for fairly frequently (as is implied by
> the original article)?

Probably the former in my case.  I can't see any harm in adding
dired-ignored-extensions -- if you prefer not to use this feature, you can
just let this list be nil.

-- Ashwin.