Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: coreutils@gnu.org, linux-man@vger.kernel.org
Subject: Re: ls/dir/vdir(1)
Date: Sun, 19 Jul 2026 13:21:35 +0200	[thread overview]
Message-ID: <alyx4-PfUx9zh0tc@devuan> (raw)
In-Reply-To: <86qzkzpaof.fsf@aarsen.me>

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

Hi Arsen,

On 2026-07-19T11:53:52+0200, Arsen Arsenović wrote:
> Alejandro Colomar <alx@kernel.org> writes:
> 
> > [[PGP Signed Part:No public key for EB89995CC290C2A9 created at 2026-07-18T17:42:18+0200 using RSA]]
> > Hi,
> >
> > I have some doubts about specific pages; let's start with ls/dir/vdir.
> >
> > Experimentally, ls(1) and dir(1) seem to be exactly the same.  I'd like
> > to document dir(1) with a short page saying that it's equivalent to
> > ls(1).  Is this correct, or is there any subtle difference?
> 
> Quoting the documentation:
> 
> 
> > 10.2 ‘dir’: Briefly list directory contents
> > ===========================================
> > 
> > ‘dir’ is equivalent to ‘ls -C -b’; that is, by default files are
> > listed in columns, sorted vertically, and special characters are
> > represented by backslash escape sequences.
> > 
> >    *Note ‘ls’: ls invocation.
> 
> > 10.3 ‘vdir’: Verbosely list directory contents
> > ==============================================
> > 
> > ‘vdir’ is equivalent to ‘ls -l -b’; that is, by default files are
> > listed in long format and special characters are represented by
> > backslash escape sequences.
> > 
> >    *Note ‘ls’: ls invocation.

Thanks!  I've changed the descriptions of these two programs to the
following short and simple descriptions:

	DESCRIPTION
	     vdir is equivalent to ls -l -b.

	DESCRIPTION
	     dir is equivalent to ls -C -b.


Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es>

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

  reply	other threads:[~2026-07-19 11:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-18 15:13 Hand-written manual pages for GNU coreutils Alejandro Colomar
2026-07-18 15:42 ` ls/dir/vdir(1) Alejandro Colomar
2026-07-18 18:15   ` ls/dir/vdir(1) Ivan Sokolov
2026-07-19  9:53   ` ls/dir/vdir(1) Arsen Arsenović
2026-07-19 11:21     ` Alejandro Colomar [this message]
2026-07-18 17:02 ` Hand-written manual pages for GNU coreutils Pádraig Brady
2026-07-18 17:46   ` Alejandro Colomar

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=alyx4-PfUx9zh0tc@devuan \
    --to=alx@kernel.org \
    --cc=arsen@aarsen.me \
    --cc=coreutils@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox