Paul Eggert writes:
> I've not been a fan of those .m4 serial numbers, which may help to
> explain why so many .m4 files lack them. Although I still have doubts
> whether they're worth the trouble, perhaps it'd help if we added a
> file m4/.dir-locals.el (or something similar) that would cause Em
Paul Eggert wrote:
> Although I still have doubts whether they're worth the trouble
While I personally have not encountered the benefits of the serial
numbers — since I don't use 'aclocal --install' —, other people
surely do.
> perhaps it'd help if we added a file
> m4/.dir-locals.el (or somethi
I've not been a fan of those .m4 serial numbers, which may help to
explain why so many .m4 files lack them. Although I still have doubts
whether they're worth the trouble, perhaps it'd help if we added a file
m4/.dir-locals.el (or something similar) that would cause Emacs to
update these serial
Sam James wrote:
> At a glance, it looks like gettext's m4/fixautomake.m4 at
> least might be affected.
Yes, some *.m4 files in other packages are affected as well. Fixed now.
> I should really have all the GNU projects in one directory so I can
> easily grep in future.
For searching across many
Bruno Haible writes:
> Sam James wrote:
>> For reasons once might be able to guess, I'm currently playing with
>> "known" M4 macros vs unseen serials and such.
>>
>> At the moment, my tool uses the format described at
>> https://www.gnu.org/software/automake/manual/html_node/Serials.html.
>>
>>
Sam James wrote:
> For reasons once might be able to guess, I'm currently playing with
> "known" M4 macros vs unseen serials and such.
>
> At the moment, my tool uses the format described at
> https://www.gnu.org/software/automake/manual/html_node/Serials.html.
>
> My reading of it implies that t
