Hans Hagen wrote: > Vit Zyka wrote: >> >> thanks for a remmembering. As I said: this mail is a suggestion to >> solve a general problem by systemic way. >> > sure, but \input cannot be redefined in a robust way because of its > scanning nature; ok, in luatex we can intercept things, but not in mkii > Hans
I thought that the number of calling \input inside text state is limited---(only?) one example is a loading encoding definition file. Why not to incorporate the cleverness of setting a default \endinputchar to a macro that invokes \input? > \startreadingfile ... \stopreadingfile is an option then understand as a solution bypassing \input redefinition Vit ___________________________________________________________________________________ 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________