[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Is doc/org-version.tex generation broken?
From: |
Kyle Meyer |
Subject: |
Re: [O] Is doc/org-version.tex generation broken? |
Date: |
Fri, 30 Jun 2017 10:30:50 -0400 |
Dale <address@hidden> writes:
> a8d007db15 starts generating doc/org-version.{tex,inc},
Unimportant to the rest of this issue, but that commit only started
generating doc/org-version.tex. The generation of doc/org-version.inc
wasn't modified.
> but on my OS X system this ends up creating broken files with (I
> believe) vertical tab characters in them. On HEAD this morning:
>
> $ make card
[...]
> $ cat doc/org-version.tex
> % automatically generated, do not edit
> \def\orgversionnumber{9.0.9}
> \def
> ersionyear{2017}
> \def\year{2017}
>
> I have no idea how that \v is getting turned into a vertical tab. Is make
> processing these?
Ehh, that's coming through fine on my end as
% automatically generated, do not edit
\def\orgversionnumber{9.0.9}
\def\versionyear{2017}
\def\year{2017}
> $ gmake --version
> GNU Make 4.2.1
> Built for x86_64-apple-darwin15.6.0
$ make --version
GNU Make 4.2.1
Built for x86_64-unknown-linux-gnu
> $ gmake -f /tmp/test-makefile single double quad
> echo "single: 123\v456"
> single: 123
> 456
echo "single: 123\v456"
single: 123\v456
> echo "double: 123\\v456"
> double: 123
> 456
echo "double: 123\\v456"
double: 123\v456
> echo "quad: 123\\\\v456"
> quad: 123\v456
echo "quad: 123\\\\v456"
quad: 123\\v456
> Is this something screwed up in my environment or are others seeing this as
> well?
I'm guessing that I should rewrite the command in a more portable way.
Not sure what that is offhand.
--
Kyle