From: Victor Engmark via GNU coreutils Bug Reports <bug-coreutils@gnu.org>
To: 60667@debbugs.gnu.org
Subject: bug#60667: Split pathchk's -p into multiple flags?
Date: Mon, 09 Jan 2023 10:08:05 +1300 [thread overview]
Message-ID: <349d2f61e0c9b62ba44948ab3a48a99761584597.camel@engmark.name> (raw)
Hi,
I'd like to enforce the POSIX portable file name character set in my
projects, which `pathchk -p` does, but I don't want to enforce the
POSIX maximum path component length of 14 characters, which it also
does. Would it be useful to introduce separate flags for the three
rules enforced by `-p`? One to enforce non-empty file names, one to
enforce the POSIX portable file name character set, and one to enforce
the POSIX maximum path component length.
Kind regards
Victor Engmark
next reply other threads:[~2023-01-08 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 21:08 Victor Engmark via GNU coreutils Bug Reports [this message]
2023-01-09 5:35 ` bug#60667: Close message Victor Engmark via GNU coreutils Bug Reports
2023-01-09 13:56 ` Pádraig Brady
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://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=349d2f61e0c9b62ba44948ab3a48a99761584597.camel@engmark.name \
--to=bug-coreutils@gnu.org \
--cc=60667@debbugs.gnu.org \
--cc=victor@engmark.name \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).