zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-users@zsh.org
Subject: Re: ls *.mp4 → ls : invalid option -- 'M'
Date: Fri, 13 Oct 2023 16:13:10 +0100 (BST)	[thread overview]
Message-ID: <1312746524.945376.1697209990281@mail.virginmedia.com> (raw)
In-Reply-To: <ff4c078f-bd8b-4bd6-8043-50766db23769@eastlink.ca>

> On 13/10/2023 15:46 Ray Andrews <rayandrews@eastlink.ca> wrote:
> On 2023-10-13 01:15, Mikael Magnusson wrote:
> 
> > One (or more) of your files start with the string "--M", you want
> > either ls -- * or ls ./* (or print -rl - *)
>
> I understand the answer and it was courteously given, but just
> technically speaking, is that a zsh issue? I'm seeing it as the
> internal problem of ls. Remembering that the shell will do the
> expansion of the argument, is it in any way up to zsh to parse any
> '--M*' as special? In other words, Denis' question seems to suppose
> that it IS somehow up to zsh to handle that, and I'm wondering if
> that's correct.

It's more that it's up to the zsh user, and if they don't know what to
do, they're going to ask the zsh users mailing list.  It's a very
generic Unix shell issue; you can argue whether shells should work like
this but it's way too late now.

So no, it's not up to zsh to do anything different, but yes, it is
up to zsh users on the mailing list to help out with questions like
this.

pws


  reply	other threads:[~2023-10-13 15:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13  7:59 Denis Bitouzé
2023-10-13  8:15 ` sergio
2023-10-13  8:15 ` Mikael Magnusson
2023-10-13 11:38   ` Denis Bitouzé
2023-10-13 14:46   ` Ray Andrews
2023-10-13 15:13     ` Peter Stephenson [this message]
2023-10-13 15:58       ` Ray Andrews
2023-10-16  0:46       ` Bart Schaefer
2023-10-16  4:17         ` Bart Schaefer
2023-10-16  4:25           ` Bart Schaefer
2023-10-16 13:35             ` Ray Andrews
2023-10-16 18:21               ` Bart Schaefer
2023-10-16 19:45                 ` Ray Andrews
2023-10-17  3:49                   ` Bart Schaefer
2023-10-17 14:04                     ` Ray Andrews
2023-10-17 15:55                       ` Bart Schaefer
2023-10-17 17:03                         ` Ray Andrews

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=1312746524.945376.1697209990281@mail.virginmedia.com \
    --to=p.w.stephenson@ntlworld.com \
    --cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).