Re: Bug in m4

m4:Alan+Roger+Davin-2014.hts:10: ERROR: end of file in argument list > make[2]: *** [../../Makefile.mk:149: m4-inner] Error 1 So m4 is reporting that there is a syntax error in your file Alan+Roger+Davin-2014.hts. That's not a bug in m4, but in your file. Without knowing the contents of th

Re: Bug in m4

webs-com Can you give more details? What error messages are you getting? Why do you think it is a bug in m4, rather than in the Peblic sources? -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org

Re: Bug in m4

Apologies for missing the following hyperlink in the previous email to you. -- Sincerely and kindest regards, *Davin Pearson* http://davin.50webs.com On Sun, 2 Apr 2023 at 13:25, Davin Pearson wrote: > The following archive Peblic-20230

Re: Bug in m4

Try the following FTP download... > -- -- Sincerely and kindest regards, *Davin Pearson* http://davin.50webs.com On Sun, 2 Apr 2023 at 13:28, Davin Pearson wrote: > Apologies for missi

Bug in m4

The following archive Peblic-20230402-131204.tar.gz when extracted fails to build the following targets. The code takes an X.hts (stands for HTml Source) file and converts it to an X.html file using GNU m4. $cd ~/Peblic/Makefile && make m4-test $cd ~/Peblic/sources/Makefile && make m4

RE: There is a bug in m4 tracing

Sorry, what was confusing me was that the trace information is interspersed with the output. I.e.,   m4trace: -2- foo m4trace: -1- echo1 This is the macro m4trace: -1- foo This is the macro foo..   Blue is the real output and red is the trace. I was reading it like   m4trace: -2- f

Re: There is a bug in m4 tracing

Hello, > Witness the following typescript: looks right to me. Let me explain; let's start with your definition: > define(`foo', `This is the macro `foo'.') The most natural way to use this macro as a parameter would be this: > define(`echo3', `$1') > echo3(`foo') (Note that the parameter is

There is a bug in m4 tracing

Witness the following typescript:   Script started on Tue 28 Mar 2006 10:30:52 PM PST $ cat m4.txt define(`echo1', `$*') define(`echo2', `$@') define(`foo', `This is the macro `foo'.') #traceon echo1(foo) echo2(foo) $ m4 m4.txt       #traceon This is the macro This is the macr

Re: Bug in M4 documentation

I changed it to `m4wrap can be called from m4wrapped text. However, the order of evaluation can not be determined ahead of time.' I've attached a diff to m4.texinfo, if that is correct. Samuel Lauber - Original Message - From: "Stepan Kasal" <[EMAIL PROTECTED]> > Hello, > > [the bes

Re: Bug in M4

Hello, [again, I'm moving the discussion to bug-m4] in the bug report below, you say that the text saved by m4wrap should not be processed at the end of the input when the m4 run is to be frozen. The text should be saved to the frozen file instead. I read the node `Frozen files' of the GNU m4 ma

Re: Bug in M4 documentation

Hello, [the best place to discuss m4 bugs is bug-m4, so I'm moving the discussion there] On Sun, Jan 09, 2005 at 07:38:26PM +0100, Sam Lauber wrote: > "It is safe to call `m4wrap' from saved text, but the order > in which the saved text is read is undefined." > > I do not understand that paragr

A possible bug in m4 1.4.1 with missing file supplied as program argument

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello. I suppose that this may be a bug: If you call m4 with non-existing file as one of m4's arument, an error message is printed, but the program does not terminate with error. While this may be acceptable in normal conditions, I expect that with