[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: @hashchar{}, --dvi/--pdf #line
From: |
Patrice Dumas |
Subject: |
Re: @hashchar{}, --dvi/--pdf #line |
Date: |
Tue, 3 Jan 2012 22:38:32 +0100 |
User-agent: |
Mutt/1.4.2.2i |
On Tue, Jan 03, 2012 at 10:40:20AM -0800, Karl Berry wrote:
> I implemented @hashchar{}. I blindly added it in the same places as
> @backslashchar{}, which seemed to work ok, but didn't add it to any
> tests.
Seems right. I forgot to add all the others to tests too.
> Hope that doesn't disturb. If you'd rather I stay out of tp/,
> just let me know :).
No problem, that please me. I reread the patches anyway.
> Regarding #line and texi2any --dvi/--pdf, looking at the old mail, I
> guess we concluded that there was no way for tp to pass a temp file with
> just the #line's stripped. Instead, either the user has to arrange for
> #line's not to be generated when making dvi/pdf, or has to use
> texi2any -E. Right? Just making sure before I try to write the
> documentation.
That's what I recall too, because of @include, mostly. If I really manage
to do something smart with marksource, maybe this could be possible to
improve over the situation, but that'll be for later.
--
Pat