[OS X TeX] Re: Save date-time, not Print date

Alain Schremmer schremmer.alain at gmail.com
Tue Feb 5 03:11:27 CET 2008

On Feb 4, 2008, at 3:41 PM, Joachim Kock wrote:

>> Whenever I print a document, I get the PRINT date. Is it possible
>> to get the (last) SAVE date-time instead?
> In my opinion, this should be the task of the editor (with a save hook
> inserting a date stamp), not the task of tex.

I wholeheartedly agree. Unfortunately, I happen also to be the editor  
inasmuch as whatever user(s), if any, will have downloaded the stuff  
from FMTo. Joke apart, my very limited understanding of the old  
thread was that the editor had somehow to cooperate with TeX.

>> I thought I remembered something about it but was unable to find in
>> the archive anything other than version control which is a lot more
>> than what I would like since all I want to know is if what I have
>> handed out to the students is "current".
> On Fri, 14 Jul 2006, I explained how to set up such a save hook in  
> Alpha
> (adapted from save hooks that exist in most of Alpha's programming  
> modes).

I hadn't planned on switching from TeXShop anytime in the foreseeable  
future (Pace Dyballa)

>> Before I bother sourceforge with a request, though, I would like to
>> have the opinion of this list on the merit(s) of the case, if any.
> You mention that TeXShop saves the file on Typeset even if the file
> has not been modified.  I think this is a bug.

Well then I like that bug.

> By principle, typesetting
> a file is not supposed to modify the file; you ought to be able to
> typeset an old file as saved years ago, without suddenly seeing a
> different modification date on it.

It certainly makes complete sense and I didn't dare suggest it but I  
think that there ought to be three buttons: Typeset&Save—TypesetOnly— 
SaveOnly (Yes, I know, I can go File > Save but then there is the  
MakeIndex button and the Tool bar can be customized.)

>   Gratuitously saving an unmodified
> file also has a bad effect on backup schemes, and may interfere with
> version control.

Here, I am the scheme and it doesn't bother the schem-mer.

> I think Dick explained me many years ago that TeXShop has to save the
> file because of a translation back and forth between unicode and
> something else, which takes place behind the scenes.  I think a
> workaround for this bug would be valuable.

For me it certainly would!

Grateful regards

More information about the macostex-archives mailing list