9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] awk(1): quote argument for -v option
Date: Tue, 29 Nov 2022 09:52:40 -0500	[thread overview]
Message-ID: <AEFBBA3E-1428-4509-BC10-45B8827977E7@stanleylieber.com> (raw)
In-Reply-To: <Y4X2srVryGMhBXDR@x1.home>

this is an rc quirk, not related to awk. for example, what if you run awk from the ape/sh (or some other) shell?

on the other hand, obviously in almost every case the user will be launching awk from rc.

still, i do not think we need to document rc quoting behavior in every man page because ultimately the man page is for the program in question, while rc quoting is something a 9front user will have to come to terms with early in their career as a 9front.

in summary, rc’s quoting is not a universal condition, so it should remain implied rather than explicit in man pages that are not the rc man page.

sl

> On Nov 29, 2022, at 7:11 AM, Anders Damsgaard <anders@adamsgaard.dk> wrote:
> 
> Dear all,
> 
> Running awk from rc, I found that I need to quote the arguments to awk's
> -v option, as in:
> 
>    awk -v 'myvar=asdf' 'BEGIN{print myvar}'
> 
> However, the awk man page specifies this without quotes as "awk -v
> myvar=asdf".  I now realize that it will not work without quotes because
> rc tries to interpret the assignment operator.
> 
> Is this just a beginner mistake, being used to unix behavior, or worth
> documenting as in the patch below?
> 
> Thanks, Anders
> 
> 
> diff ff2ebe6cfdacd890a74a6d2f9b0acd062d2633b7 uncommitted
> --- a/sys/man/1/awk
> +++ b/sys/man/1/awk
> @@ -23,7 +23,7 @@
> ]
> [
> .B -v
> -.I var=value
> +.I 'var=value'
> ]
> [
> .B -f
> @@ -58,13 +58,13 @@
> Any
> .IR file
> of the form
> -.I var=value
> +.I 'var=value'
> is treated as an assignment, not a file name,
> and is executed at the time it would have been opened if it were a file name.
> The option
> .B -v
> followed by
> -.I var=value
> +.I 'var=value'
> is an assignment to be done before the program
> is executed;
> any number of
> 


  parent reply	other threads:[~2022-11-29 14:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 12:10 Anders Damsgaard
2022-11-29 13:47 ` qwx
2022-11-29 14:52 ` Stanley Lieber [this message]
2022-11-29 15:14 ` Kurt H Maier
2022-11-29 15:22   ` Stanley Lieber
2022-11-29 16:24   ` Sigrid Solveig Haflínudóttir
2022-11-29 16:28     ` Jacob Moody
2022-11-29 16:43       ` Kurt H Maier
2022-11-29 19:06         ` Stanley Lieber
2022-11-29 19:52           ` Stanley Lieber

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=AEFBBA3E-1428-4509-BC10-45B8827977E7@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).