Re: Extensions to M4sh

2022-05-06 Thread Alex Ameen
This is beautiful. We're walking a real similar path here. Let t me throw my macros in a repo so you can see On Fri, May 6, 2022, 8:46 AM madmurphy wrote: > Hey I recently implemented a pretty sizeable set of M4sh extensions that > make it much more suitable for writing general purpose shell sc

Re: Extensions to M4sh

2022-05-06 Thread madmurphy
Hey I recently implemented a pretty sizeable set of M4sh extensions that make it much more suitable for writing general purpose shell scripts. That is wonderful, could please you share a link? Whoever is most actively working on M4sh would be an incredibly useful contact for me, so if "that's you

Re: Extensions to M4sh

2022-05-04 Thread Michael Orlitzky
On Wed, 2022-05-04 at 08:17 -0700, Per Bothner wrote: > On 5/4/22 05:07, Michael Orlitzky wrote: > > The trade-off you get for writing m4 is that the build system produced > > by autotools doesn't require you to have autotools installed, and > > instead uses only a portable subset of standard syste

Re: Extensions to M4sh

2022-05-04 Thread Per Bothner
On 5/4/22 05:07, Michael Orlitzky wrote: The trade-off you get for writing m4 is that the build system produced by autotools doesn't require you to have autotools installed, and instead uses only a portable subset of standard system tools. I think this is a very minor benefit: (1) To build a pr

Re: Extensions to M4sh

2022-05-04 Thread Nate Bargmann
* On 2022 04 May 07:09 -0500, Michael Orlitzky wrote: > The trade-off you get for writing m4 is that the build system produced > by autotools doesn't require you to have autotools installed, and > instead uses only a portable subset of standard system tools. As a > result, end users can never encou

Re: Extensions to M4sh

2022-05-04 Thread Carlos O'Donell
On 5/4/22 06:00, Demi Marie Obenour wrote: > On 5/3/22 16:35, Zack Weinberg wrote: >> On Mon, May 2, 2022, at 2:30 AM, Paul Eggert wrote: >>> On 5/1/22 19:06, Alex Ameen wrote: Whoever is most actively working on M4sh would be an incredibly useful contact for me, so if "that's you" let me

Re: Extensions to M4sh

2022-05-04 Thread Carlos O'Donell
On 5/3/22 16:35, Zack Weinberg wrote: > On Mon, May 2, 2022, at 2:30 AM, Paul Eggert wrote: >> On 5/1/22 19:06, Alex Ameen wrote: >>> Whoever is most actively working on M4sh would be an incredibly >>> useful contact for me, so if "that's you" let me know. >> >> To be honest right now I think "tha

Re: Extensions to M4sh

2022-05-04 Thread Michael Orlitzky
On Wed, 2022-05-04 at 06:00 -0400, Demi Marie Obenour wrote: > > Honestly, I feel like the autotools are dying. > They're feature-complete, up to support for some newer languages. > If I use Meson or CMake, I get solutions to all of these problems, > except perhaps IDE integration. And that i

Re: Extensions to M4sh

2022-05-04 Thread Demi Marie Obenour
On 5/3/22 16:35, Zack Weinberg wrote: > On Mon, May 2, 2022, at 2:30 AM, Paul Eggert wrote: >> On 5/1/22 19:06, Alex Ameen wrote: >>> Whoever is most >>> actively working on M4sh would be an incredibly useful contact for me, so >>> if "that's you" let me know. >> >> To be honest right now I think "

Re: Extensions to M4sh

2022-05-03 Thread Zack Weinberg
On Mon, May 2, 2022, at 2:30 AM, Paul Eggert wrote: > On 5/1/22 19:06, Alex Ameen wrote: >> Whoever is most >> actively working on M4sh would be an incredibly useful contact for me, so >> if "that's you" let me know. > > To be honest right now I think "that's you" is the correct answer. As > in, y

Re: Extensions to M4sh

2022-05-01 Thread Paul Eggert
On 5/1/22 19:06, Alex Ameen wrote: Whoever is most actively working on M4sh would be an incredibly useful contact for me, so if "that's you" let me know. To be honest right now I think "that's you" is the correct answer. As in, you're the one. If these are extensions to m4sh (as opposed to c