From: Kyle Meyer <kyle@kyleam.com>
To: Dale <dale@codefu.org>, emacs-orgmode@gnu.org
Subject: Re: Is doc/org-version.tex generation broken?
Date: Fri, 30 Jun 2017 10:30:50 -0400 [thread overview]
Message-ID: <8737ah8s4l.fsf@kyleam.com> (raw)
In-Reply-To: <CAEj9N4+z=bd9xBaiPBe29AL-HEMrF+foVO7gT3wwRYpJ4kVP=w@mail.gmail.com>
Dale <dale@codefu.org> 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
next prev parent reply other threads:[~2017-06-30 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 13:25 Is doc/org-version.tex generation broken? Dale
2017-06-30 14:08 ` Michael Ax
2017-06-30 14:30 ` Kyle Meyer [this message]
2017-06-30 17:29 ` Kyle Meyer
2017-07-01 3:46 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737ah8s4l.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=dale@codefu.org \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).