All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Jeremy Baxter <jtbx@disroot.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v2 3/6] intro.1: Explain the meaning of a directory
Date: Mon, 18 Mar 2024 22:57:49 +0100	[thread overview]
Message-ID: <Zfi447ghGCfLC_Kk@debian> (raw)
In-Reply-To: <CZX537Q8308O.YVDA7PY3E2H2@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 2400 bytes --]

Hi Jeremy,

On Tue, Mar 19, 2024 at 08:57:07AM +1300, Jeremy Baxter wrote:
> On Mon Mar 18, 2024 at 4:05 AM NZDT, Alejandro Colomar wrote:
> > On Sun, Mar 17, 2024 at 09:08:31PM +1300, Jeremy Baxter wrote:
> > > ---
> > >  man1/intro.1 | 3 +++
> > >  1 file changed, 3 insertions(+)
> > > 
> > > diff --git a/man1/intro.1 b/man1/intro.1
> > > index 090678750..f0a8d98e0 100644
> > > --- a/man1/intro.1
> > > +++ b/man1/intro.1
> > > @@ -180,6 +180,9 @@ The command
> > >  In this example, we use it to find Maja's telephone number.
> > >  .SS Pathnames and the current directory
> > >  Files live in a large tree, called the file hierarchy.
> > > +In this hierarchy, there are many
> > > +.IR directories ;
> > > +a directory is simply a file that can hold other files as opposed to text.
> >
> > This might confuse more than it helps.  What does "hold" mean?  Does the
> > directory hold the file data?  As in a .tar archive?  No.
> >
> > In any case, this subsection doesn't seem to treat how directories are
> > represented in the filesystem, but rather how they are presented to the
> > user in path names.
> 
> What do you think about this?
> 
>   In this hierarchy, there are many
>   .IR directories ;
>   a directory is simple a file that contains other files,
>   rather than text.
>   For example, if we have a file called
>   .I tel
>   in the directory
>   .IR /home/aeb ,
>   we can refer to it by the pathname
>   .IR /home/aeb/tel .
> 
> I think this section is still important because previously there was
> no explanation for this, and most people are accustomed to using the
> word "folder".

Hmm, it's good that you mention this.  When explaining directories to
friends used to Windows (and GUI) terms, I noticed that it's unfamiliar
to them.

I actually thought about it, and the term "directory" tells you what it
is quite precisely:

Like a directory of phones, it's just a piece of paper where you note
down the phones of people.  Directories, similarly, contain lists of
files.  They don't "hold" nor "contain" the files.

Cheers,
Alex

> 
>  ~Jeremy
> 
> > >  Each file has a
> > >  .I "pathname"
> > >  describing the location of the file from the root of the tree
> > > -- 
> > > 2.44.0
> > > 
> > > 
> 

-- 
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-03-18 21:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-17  8:08 [PATCH v2 1/6] intro.1: Revise language Jeremy Baxter
2024-03-17  8:08 ` [PATCH v2 2/6] intro.1: Document the meaning of the PS1 variable Jeremy Baxter
2024-03-17 15:00   ` Alejandro Colomar
2024-03-18 19:52     ` Jeremy Baxter
2024-03-17  8:08 ` [PATCH v2 3/6] intro.1: Explain the meaning of a directory Jeremy Baxter
2024-03-17 15:05   ` Alejandro Colomar
2024-03-18 19:57     ` Jeremy Baxter
2024-03-18 21:57       ` Alejandro Colomar [this message]
2024-03-18 22:28         ` Jeremy Baxter
2024-03-17  8:08 ` [PATCH v2 4/6] intro.1: Demonstrate special cases of the cd command Jeremy Baxter
2024-03-17 15:07   ` Alejandro Colomar
2024-03-17  8:08 ` [PATCH v2 5/6] intro.1: Define a process ID Jeremy Baxter
2024-03-17  8:08 ` [PATCH v2 6/6] intro.1: Revise paragraph documenting GNU texinfo Jeremy Baxter
2024-03-17 15:10   ` Alejandro Colomar
2024-03-17 14:47 ` [PATCH v2 1/6] intro.1: Revise language Alejandro Colomar
2024-03-18 19:50   ` Jeremy Baxter
2024-03-18 19:56     ` G. Branden Robinson
2024-03-18 22:05       ` Alejandro Colomar
2024-03-18 22:32         ` Jeremy Baxter

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Zfi447ghGCfLC_Kk@debian \
    --to=alx@kernel.org \
    --cc=jtbx@disroot.org \
    --cc=linux-man@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.