From: zeurkous@blaatscaahp.org
To: Oliver Kiddle <opk@zsh.org>
Cc: zsh-workers@zsh.org, "Jun. T" <takimoto-j@kba.biglobe.ne.jp>
Subject: RE: Re: ksh compatibility: initial value of $_
Date: Wed, 05 Apr 2023 08:15:58 +0000 (UTC) [thread overview]
Message-ID: <thinkcrap!zeurkous!1680682556.7436@uucp> (raw)
In-Reply-To: <24885-1680656615.101426@YPd-.5KmN.pkOW>
Haai,
On Wed, 05 Apr 2023 03:03:35 +0200, Oliver Kiddle <opk@zsh.org> wrote:
> "Jun. T" wrote:
> Given that you're ignoring the output, test -L is likely more portable
> in this case. Specifically it would work on Solaris 10 which doesn't
> have readlink (but does have /proc/self/path/a.out). test -L is covered
> by the POSIX standard while readlink isn't.
FWIW, OpenBSD test(1) says--
-\b-L\bL _\bf_\bi_\bl_\be
True if _\bf_\bi_\bl_\be exists and is a symbolic link. This operator is for
compatibility purposes. Do not rely on its existence; use -\b-h\bh
instead.
Note that last part. Is "-L" actually more standard? (Even on other
*cough* Unices, me's always used "-h").
There's also stat(1), but that appears to be even less standard than
readlink(1).
> Oliver
--zeurkous.
--
Friggin' Machines!
next prev parent reply other threads:[~2023-04-05 8:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 1:52 Bart Schaefer
2023-03-23 10:40 ` Jun T
2023-03-31 8:18 ` Jun T
2023-03-31 14:31 ` Jun. T
2023-03-31 17:45 ` Bart Schaefer
2023-04-03 11:16 ` Jun. T
2023-04-03 16:48 ` Bart Schaefer
2023-03-31 19:02 ` Bart Schaefer
2023-03-31 19:03 ` Bart Schaefer
2023-04-03 12:13 ` Jun. T
2023-04-03 16:50 ` Bart Schaefer
2023-04-04 16:24 ` Jun. T
2023-04-05 1:03 ` Oliver Kiddle
2023-04-05 8:15 ` zeurkous [this message]
2023-04-05 9:00 ` Oliver Kiddle
2023-04-05 16:24 ` Jun. T
2023-04-05 8:14 ` dana
2023-04-05 18:16 ` Jun. T
2023-04-08 4:03 ` dana
2023-04-08 16:22 ` Oliver Kiddle
2023-04-09 13:30 ` Jun. T
2023-04-10 0:51 ` Jun T
2023-04-15 5:02 ` Felipe Contreras
2023-04-15 22:24 ` Bart Schaefer
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='thinkcrap'\!'zeurkous'\!'1680682556.7436@uucp' \
--to=zeurkous@blaatscaahp.org \
--cc=opk@zsh.org \
--cc=takimoto-j@kba.biglobe.ne.jp \
--cc=zsh-workers@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).