unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@lexort.com>
To: 39999@debbugs.gnu.org
Subject: bug#39999: sed -i non-POSIX
Date: Fri, 01 May 2020 10:37:43 -0400	[thread overview]
Message-ID: <rmi4kszg1qg.fsf@s1.lexort.com> (raw)
In-Reply-To: <0E291356-1D5D-4F19-9809-43F7A2B35643@mac.com> (wlharvey's message of "Wed, 29 Apr 2020 17:37:13 -0700")

wlharvey4--- via "Bug reports for GUILE, GNU's Ubiquitous Extension
Language" <bug-guile@gnu.org> writes:

> Greg,
>
> Good point.  The BSD sed man page says:
>
> "The -E, -a and -i options are non-standard FreeBSD extensions and may not be available on other operating systems."
>
> So perhaps a better solution is to not use the -i option at all and be POSIX compliant?
>
> Informally looking through some of the code, this was the only use of the -i option that I found.

If that is at all reasonable, then I think it's the best thing to do.

FWIW, the saem text about -i being a FreeBSD extension appears in the
NetBSD man page.





      reply	other threads:[~2020-05-01 14:37 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 ` bug#39999: BSD sed vs Gnu sed W. Lincoln Harvey via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2020-04-30  0:04   ` 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 [this message]

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=rmi4kszg1qg.fsf@s1.lexort.com \
    --to=gdt@lexort.com \
    --cc=39999@debbugs.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).