unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Van Ly <van.ly@sdf.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 53739@debbugs.gnu.org
Subject: bug#53739: 28.0.91; "C-x d" fails when "emacs -Q" starts on NetBSD with plan9/bin on head of PATH
Date: Thu, 3 Feb 2022 13:12:07 +0000 (UTC)	[thread overview]
Message-ID: <ecd096cd-2eee-1bfc-d6d5-568035c4b1@SDF.ORG> (raw)
In-Reply-To: <87fsp06zgb.fsf@yahoo.com>

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

On Thu, 3 Feb 2022, Po Lu wrote:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Can you tell more about the incompatibilities, perhaps by comparing
>> the output of their 'ls' with a compatible one?
>
> I can't remember the specifics, but IIRC their version of ls simply
> prints out each file in the current working directory, without any
> option to display permission bits, size, or ownership information.
>

The manpage for plan9's ls command is attached.

-- 
vl

[-- Attachment #2: Manpage for ls command --]
[-- Type: text/plain, Size: 3919 bytes --]


     LS(1)                                                       LS(1)

     NAME
          ls, lc - list contents of directory

     SYNOPSIS
          ls [ -dlmnpqrstuFQ ] name ...

          lc [ -dlmnpqrstuFQ ] name ...

     DESCRIPTION
          For each directory argument, ls lists the contents of the
          directory; for each file argument, ls repeats its name and
          any other information requested.  When no argument is given,
          the current directory is listed.  By default, the output is
          sorted alphabetically by name.

          Lc is the same as ls, but sets the -p option and pipes the
          output through mc(1).

          There are a number of options:

          -d   If argument is a directory, list it, not its contents.

          -l   List in long format, giving mode (see below), file sys-
               tem type (e.g., for devices, the # code letter that
               names it; see intro(3)), the instance or subdevice num-
               ber, owner, group, size in bytes, and time of last mod-
               ification for each file.

          -m   List the name of the user who most recently modified
               the file.

          -n   Don't sort the listing.

          -p   Print only the final path element of each file name.

          -q   List the qid (see stat(3)) of each file; the printed
               fields are in the order path, version, and type.

          -r   Reverse the order of sort.

          -s   Give size in Kbytes for each entry.

          -t   Sort by time modified (latest first) instead of by
               name.

          -u   Under -t sort by time of last access; under -l print
               time of last access.

          -F   Add the character / after all directory names and the
               character * after all executable files.

     Page 1                       Plan 9              (printed 2/4/22)

     LS(1)                                                       LS(1)

          -L   Print the character t before each file if it has the
               temporary flag set, and - otherwise.

          -Q   By default, printed file names are quoted if they con-
               tain characters special to rc(1).  The -Q flag disables
               this behavior.

          The mode printed under the -l option contains 11 characters,
          interpreted as follows: the first character is

          d    if the entry is a directory;

          a    if the entry is an append-only file;

          D    if the entry is a Unix device;

          L    if the entry is a symbolic link;

          P    if the entry is a named pipe;

          S    if the entry is a socket;

          -    if the entry is a plain file.

          The next letter is l if the file is exclusive access (one
          writer or reader at a time).

          The last 9 characters are interpreted as three sets of three
          bits each.  The first set refers to owner permissions; the
          next to permissions to others in the same user-group; and
          the last to all others.  Within each set the three charac-
          ters indicate permission respectively to read, to write, or
          to execute the file as a program.  For a directory, `exe-
          cute' permission is interpreted to mean permission to search
          the directory for a specified file.  The permissions are
          indicated as follows:

          r  if the file is readable;
          w  if the file is writable;
          x  if the file is executable;
          -  if none of the above permissions is granted.

     SOURCE
          /usr/local/plan9/src/cmd/ls.c
          /usr/local/plan9/bin/lc

     SEE ALSO
          stat(3), mc(1)

     Page 2                       Plan 9              (printed 2/4/22)


  parent reply	other threads:[~2022-02-03 13:12 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02 22:12 bug#53739: 28.0.91; "C-x d" fails when "emacs -Q" starts on NetBSD with plan9/bin on head of PATH Van Ly
2022-02-03  7:22 ` Eli Zaretskii
2022-02-03  8:01   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-03  9:18     ` Eli Zaretskii
2022-02-03 10:01       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-03 10:31         ` Eli Zaretskii
2022-02-03 11:02           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-03 11:08             ` Eli Zaretskii
2022-02-03 11:28               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-03 13:20                 ` Van Ly
2022-02-03 16:47                   ` Eli Zaretskii
2022-02-03 13:12         ` Van Ly [this message]
2022-02-03 16:47           ` Eli Zaretskii
2022-02-04  0:59           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-04  4:29             ` Van Ly
2022-02-04  4:50               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-04  7:18                 ` Van Ly
2022-02-04  7:55                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-04  8:05                 ` Eli Zaretskii
2022-02-04  8:59                   ` Van Ly
2022-02-04  9:26                     ` Van Ly
2022-02-04 11:52                       ` Eli Zaretskii
2022-02-05  3:07                         ` Van Ly
2022-02-05  7:37                           ` Eli Zaretskii
2022-02-05  9:04                             ` Van Ly
2022-02-05  9:19                               ` Eli Zaretskii
2022-02-05 10:57                                 ` Van Ly
2022-02-05 21:57                             ` Lars Ingebrigtsen
2022-02-04 11:50                     ` Eli Zaretskii
2022-02-03 13:05     ` Van Ly
2022-02-03 16:45       ` Eli Zaretskii
2022-02-03 13:00   ` Van Ly

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=ecd096cd-2eee-1bfc-d6d5-568035c4b1@SDF.ORG \
    --to=van.ly@sdf.org \
    --cc=53739@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    /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).