unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: behavior of dired-hide-*
Date: Tue, 02 Mar 2010 21:26:53 +0100	[thread overview]
Message-ID: <87iq9etqpe.fsf@tux.homenetwork> (raw)
In-Reply-To: 38948.128.165.0.81.1267558857.squirrel@webmail.lanl.gov

Thanks for your answer,

"Davis Herring" <herring@lanl.gov> writes:

>> It seem to me, according to manual  that the first is to hide directory
>> at point and  the second is to hide all directories in current dired
>> buffer.
>
> That's correct, but from what follows I suppose you misunderstand what the
> documentation for those commands means by "a directory".  A Dired buffer
> can list the contents of multiple directories (not just list, one per
> line, each of the subdirectories of a single directory).  $ and M-$
> manipulate which of these listings is displayed, rather than affecting the
> display of any one file (which might happen to be a directory file).

Yes, i don't understand what is a directory according to the behavior of
this command:
What the $ dired command should do when i run it on the root (/) of my
system and the cursor is on say /bin?
Actually it hide all, and and M-$ does the same.

So what these $ and M-$ are for?

for me actually, they hide all files and subdirs in all case.

>> It hide all for me (files and dirs) and leave only the first line of
>> dired buffer (the directory header).(the two commands $ and M-$ do the
>> same).
>
> When you only have one directory listed (which is the normal starting
> case), they are the same.

Sorry for my difficulty to understand that, but that still very unclear
for me.

Here a directory:(is it?)

,----
|   /etc:
|   total used in directory 2120 available 8350832
|   drwxr-xr-x 90 root    root  12288 Mar  2 20:52 .
|   drwxr-xr-x 21 root    root   4096 Mar  6  2009 ..
|   -rw-------  1 root    root      0 Apr 20  2007 .pwd.lock
|   -rw-r--r--  1 root    root  65265 Oct 24 20:55 ANYTHING-TAG-FILE
|   drwxr-xr-x  4 root    root   4096 Feb 16  2009 ConsoleKit
|   -rw-r--r--  1 root    root   4468 Oct 23 14:06 DIR_COLORS
|   drwxr-xr-x  2 root    root   4096 Dec 20 14:45 RCS
|   drwxr-xr-x  6 root    root   4096 Dec 11 09:47 X11
|   drwxr-xr-x  2 root    root   4096 Jan 29 16:11 abcde
|   drwxr-xr-x  4 root    root   4096 Feb 24 11:19 acpi
`----

What should show $ if my cursor is on say Consolekit (a subdirectory of
/etc right?) ?

What should show M-$ (cursor anywhere)?

-- 
Thierry Volpiatto
Gpg key: http://pgp.mit.edu/





  reply	other threads:[~2010-03-02 20:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-27 16:35 behavior of dired-hide-* Thierry Volpiatto
2010-03-02 19:40 ` Davis Herring
2010-03-02 20:26   ` Thierry Volpiatto [this message]
2010-03-02 21:59     ` Davis Herring
2010-03-02 22:13       ` Thierry Volpiatto
2010-03-03  7:33         ` Thierry Volpiatto

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=87iq9etqpe.fsf@tux.homenetwork \
    --to=thierry.volpiatto@gmail.com \
    --cc=emacs-devel@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 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).