From: "Pablo Rodríguez" <oinos@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug with --purgeall?
Date: Thu, 29 Dec 2011 17:12:55 +0100 [thread overview]
Message-ID: <4EFC9187.5010900@web.de> (raw)
In-Reply-To: <4EFC80E5.3030103@wxs.nl>
On 12/29/2011 04:01 PM, Hans Hagen wrote:
> On 29-12-2011 07:24, Pablo Rodríguez wrote:
>> Hi there,
>>
>> yesterday I ran the following command:
>>
>> context --purgeall --environment=mysecondstyle.tex --mode=myexample.xml
>>
>> I know that the source file is missing (I discovered it later). This is
>> not my issue.
>>
>> The problem is that the --purgeall option caused context to erase all
>> ..log files contained in that directory. Instead of asking for a source
>> file name, it deleted all .log files.
>>
>> I'm afraid this is a bug, at least it shouldn't erase files that context
>> didn't generate.
>
> how should it know?
By name and by modification date and time.
But in any case, the following command:
context --purgeall
should give an error (missing document) before trying to purge all
documents.
Thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-12-29 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 6:24 Pablo Rodríguez
2011-12-29 15:01 ` Hans Hagen
2011-12-29 16:12 ` Pablo Rodríguez [this message]
2011-12-29 18:49 ` Hans Hagen
2011-12-29 20:35 ` Pablo Rodríguez
2011-12-30 12:18 ` Hans Hagen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EFC9187.5010900@web.de \
--to=oinos@web.de \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).