From: "W. Lincoln Harvey" via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile@gnu.org>
To: 39999@debbugs.gnu.org
Subject: bug#39999: BSD sed vs Gnu sed
Date: Wed, 29 Apr 2020 12:30:22 -0700 [thread overview]
Message-ID: <4BF90412-EB21-47F5-9F56-BADAA2079B18@mac.com> (raw)
In-Reply-To: <12F04DBA-35DF-49B3-B2BB-B07A95550151@gmail.com>
Sorry; my explanation above is not correct.
What I meant to say is that to edit a file in place WITHOUT CREATING a backup file, BSD sed’s -i option requires a zero-length string as a mandatory argument, while Gnu sed’s -i option does not take any argument. If a backup file is wanted, then their option -i syntax is identical.
The INSTANTIATE macro as written is not including any argument to sed’s -i option, meaning that no backup file is wanted.
Therefore, a very simply solution to this problem is to make a backup file, then delete it. Both sed versions would work correctly.
A more complicated solution is to determine which version of sed is being used, and change the INSTANTIATE macro to use the correct syntax.
Gnu sed has a version option (—version), but BSD sed does not (it throws an error when either -v or —version are used).
wlh
next prev parent reply other threads:[~2020-04-29 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 13:29 bug#39999: make install fails on mac (Catilina, Guile-3.0.1) Massimiliano Gubinelli
2020-03-11 11:11 ` Ludovic Courtès
2020-03-11 11:20 ` Massimiliano Gubinelli
2020-03-11 14:04 ` Ludovic Courtès
2020-04-29 18:22 ` bug#39999: MacOS Catalina with sed W. Lincoln Harvey via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2020-04-29 19:30 ` W. Lincoln Harvey via Bug reports for GUILE, GNU's Ubiquitous Extension Language [this message]
2020-04-30 0:04 ` bug#39999: BSD sed vs Gnu sed Greg Troxel
2020-04-30 0:37 ` bug#39999: sed -i non-POSIX wlharvey4--- via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2020-05-01 14:37 ` Greg Troxel
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BF90412-EB21-47F5-9F56-BADAA2079B18@mac.com \
--to=bug-guile@gnu.org \
--cc=39999@debbugs.gnu.org \
--cc=lincolnlaw@mac.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.
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).