From: Alejandro Colomar <alx@kernel.org>
To: Jeremy Baxter <jtbx@disroot.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v2 4/6] intro.1: Demonstrate special cases of the cd command
Date: Sun, 17 Mar 2024 16:07:26 +0100 [thread overview]
Message-ID: <ZfcHLv9ySN3TGGmD@debian> (raw)
In-Reply-To: <20240317080850.28564-7-jtbx@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
On Sun, Mar 17, 2024 at 09:08:32PM +1300, Jeremy Baxter wrote:
> ---
> man1/intro.1 | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/man1/intro.1 b/man1/intro.1
> index f0a8d98e0..8102640ba 100644
> --- a/man1/intro.1
> +++ b/man1/intro.1
> @@ -213,6 +213,25 @@ Try using the
> and
> .I pwd
> commands in different ways.
> +.I cd .
> +changes the current directory to the path to the current directory;
> +this does nothing.
. and .. are not a special case of cd. They are a special case of the
file system.
> +.I cd ..
> +changes the current directory to the parent directory of the current
> +directory.
> +For instance, if our current directory is
> +.I /home/aeb
> +and we change the current directory to
> +.IR .. ,
> +the current directory will now be
> +.IR /home .
> +.I cd /
> +changes the current directory to the root of the hierarchy.
> +.I cd \[ti]
> +changes the current directory to the user's home; if I am logged in as
> +.IR aeb ,
> +this command will change my current directory to
> +.IR /home/aeb .
> .SS Directories
> The command
> .I mkdir
> --
> 2.44.0
>
>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-17 15:07 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
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 [this message]
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=ZfcHLv9ySN3TGGmD@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.