Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!cmcl2!yale!Ram-Ashwin
From: Ram-Ashwin@cs.yale.edu (Ashwin Ram)
Newsgroups: comp.emacs
Subject: Re: Selective Dired
Message-ID: <50608@yale-celray.yale.UUCP>
Date: 14 Feb 89 16:47:44 GMT
References: <5318@lifia.imag.fr> <35981@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: 23
In-reply-to: mesard@bbn.com (Wayne Mesard)

In article <35981@bbn.COM>, mesard@bbn.com (Wayne Mesard) writes:
> In article <5318@lifia.imag.fr> phs@lifia.imag.fr (Philippe Schnoebelen) writes:
> >Is there any hook, regexp, alist or whatever trick available to tell Dired
> >not to list files such and such ?
> 
> How about the more straight-forward approach: ask and you shall receive.
> 
> > [ For example, I can imagine situations
> >where I would like the *.c and *.h files to be displayed (with also core
> >and Makefile :-) but not the *.o.
> 
> M-x dired {core,Makefile,*.[ch]}

I think I would prefer the less straight-forward approach :-).  I would
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.

Come to think of it, one would usually want dired-ignored-extensions to be
the same as completion-ignored-extensions, no?

-- Ashwin.