On Tue, Oct 1, 2013 at 12:23 PM, luigi scarso wrote:
>
> I understand the problem of triggering useless compilation due the change in
> the date only, but I think that it's easily solvable by an adequate parse of
> the banner
> that saves only the components needed.
Can you please explain? (I'm no
On Tue, Oct 1, 2013 at 11:41 AM, Hans Hagen wrote:
> On 10/1/2013 11:26 AM, Hans Hagen wrote:
>
>> On 10/1/2013 11:19 AM, Taco Hoekwater wrote:
>>
>>> On 10/01/2013 11:11 AM, Hans Hagen wrote:
>>>
as long as we keep the (unique) date in the luatex banner ... context
uses that for a
On 10/1/2013 11:26 AM, Hans Hagen wrote:
On 10/1/2013 11:19 AM, Taco Hoekwater wrote:
On 10/01/2013 11:11 AM, Hans Hagen wrote:
as long as we keep the (unique) date in the luatex banner ... context
uses that for automatically regenerating the format etc and that's a
feature I'd not like to see
On 10/1/2013 11:19 AM, Taco Hoekwater wrote:
On 10/01/2013 11:11 AM, Hans Hagen wrote:
as long as we keep the (unique) date in the luatex banner ... context
uses that for automatically regenerating the format etc and that's a
feature I'd not like to see go awa
Does it matter to you whether it
On 10/1/2013 11:19 AM, Taco Hoekwater wrote:
On 10/01/2013 11:11 AM, Hans Hagen wrote:
as long as we keep the (unique) date in the luatex banner ... context
uses that for automatically regenerating the format etc and that's a
feature I'd not like to see go awa
Does it matter to you whether it
On 10/1/2013 11:11 AM, Hans Hagen wrote:
as long as we keep the (unique) date in the luatex banner ... context
uses that for automatically regenerating the format etc and that's a
feature I'd not like to see go away
(we had rev. once so when date goes, that one has to come back to
identi
On 10/01/2013 11:11 AM, Hans Hagen wrote:
as long as we keep the (unique) date in the luatex banner ... context
uses that for automatically regenerating the format etc and that's a
feature I'd not like to see go awa
Does it matter to you whether it is an actual date string, or could it
be a su
On 10/1/2013 10:33 AM, Mojca Miklavec wrote:
On Tue, Oct 1, 2013 at 10:26 AM, Taco Hoekwater wrote:
Hi,
Karl would like me to remove \luatexdatestamp (and its associated lua
value), because that makes it easier to create new binaries from the
same source code (without getting small differences
On Tue, Oct 1, 2013 at 10:26 AM, Taco Hoekwater wrote:
> Hi,
>
> Karl would like me to remove \luatexdatestamp (and its associated lua
> value), because that makes it easier to create new binaries from the
> same source code (without getting small differences always).
>
> That is a good argument, s
Hi,
Karl would like me to remove \luatexdatestamp (and its associated lua
value), because that makes it easier to create new binaries from the
same source code (without getting small differences always).
That is a good argument, so my current plan is to remove it in the next
version. Consider
10 matches
Mail list logo
