Re: yap error

So, if I'd known about setting --trace when starting yap, it would have 
provided further information. Thanks for the tip. I'll have to see if I 
can find the technical docs that explain this more fully.

On the other hand, being chastised for failing to use a feature I wasn't 
aware of does very little to help, other than perhaps make you feel 
morally superior (since you brought up morality -- really, its a 
morality issue?), despite the fact I make $$$ donations to MikTeX on an 
annual basis (which I'm not morally obligated to do).

Now that we confounded morality with financials and technical insights, 
lets move on. If you want a mea culpa then fine.

> Not at all.  Think about the many other MiKTeX users who are going to
> encounter the same issue today and will be goggling "yap internal error".
>
> Your "solution" is not a good one.  The "internal error" message
> is a bug in yap.  Using "yap --trace--<traceflags>" could have
> provided information needed to fix the bug yesterday.
>
> In fact, the bug appears to be caused by missing modes.mf,
> provided by the metafont package.   Perhaps yap should revert
> to dvips rendering if metafont is not available (in which case
> it does not make sense to make the yap package depend on metafont).
>
> Just because you aren't obliged to contribute financially to MiKTeX
> doesn't free you of a moral obligation to the community.  A small
> extra effort on your part could potentially save many others from
> wasting time.
>
>
>> On 11/09/2016 04:07 AM, Ulrike Fischer wrote:
>>> Am Tue, 8 Nov 2016 10:53:22 -0500 schrieb Evan Cooch:
>>>
>>>> Sure, but when the error message is simply 'internal error', there
>>>> isn't much to report that would be of value, is there? ;-)
>>> The information "internal error" excludes some other possible error
>>> messages (like e.g. a ghostscript error due to a wrong renderer
>>> method).
>>>
>>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today. http://sdm.link/xeonphi
>> _______________________________________________
>> Q: How can I leave the mailing list?
>> A: See http://docs.miktex.org/faq/support.html#leavingml
>>
>
>


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Q: How can I leave the mailing list?
A: See http://docs.miktex.org/faq/support.html#leavingml