From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kyle Meyer Subject: Re: Is doc/org-version.tex generation broken? Date: Fri, 30 Jun 2017 10:30:50 -0400 Message-ID: <8737ah8s4l.fsf@kyleam.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:32988) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dQwwk-0005cw-8Q for emacs-orgmode@gnu.org; Fri, 30 Jun 2017 10:30:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dQwwh-0003mr-43 for emacs-orgmode@gnu.org; Fri, 30 Jun 2017 10:30:58 -0400 Received: from pb-smtp2.pobox.com ([64.147.108.71]:55996 helo=sasl.smtp.pobox.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dQwwg-0003mQ-U2 for emacs-orgmode@gnu.org; Fri, 30 Jun 2017 10:30:55 -0400 In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Dale , emacs-orgmode@gnu.org Dale 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