From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Taco Hoekwater <taco@elvenkind.com>,
Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: Missing "missing character" warning
Date: Mon, 28 May 2012 21:20:33 +0200 [thread overview]
Message-ID: <4FC3D001.8050309@wxs.nl> (raw)
In-Reply-To: <CALBOmsbrHZQs6d4od-+UCphgPh5=R3P2w=Dj5zMCRzxLzkp26g@mail.gmail.com>
On 28-5-2012 20:51, Mojca Miklavec wrote:
> On Mon, May 28, 2012 at 7:00 PM, Hans Hagen wrote:
>> On 28-5-2012 18:26, Marco Pessotto wrote:
>>
>>> After a lot of mumbling by myself... Is there a reason not to have the
>>> fonts.missing tracker enabled by default? Performance hit?
>>
>> indeed
>
> Still, given the large amount of data that gets printed during a
> compilation (it is basically impossible to figure out if something
> goes wrong without carefully looking at the log), I would also support
> the idea to print missing characters by default.
one can configure that locally ... much functionality only kicks in when
really used (thereby limiting the overhead) and in that case messages
also get suppressed till they make sense
> I'm also contemplating a different idea (after TL): wouldn't it be
> nice if ConTeXt (luatex) would print warnings (missing image, missing
> module, missing character, ...) in colour (if that's supported), to
> make it clearly stand out from the rest?
i once played with it (1) but such a thing will only work on a console
that supports ansi escape sequences (and console output of tex is
already rather slow and flushing being character based it might give
problems)
Hans
(1) in pdftex times ... it failed due to thsu ^^ escaping that tex applies
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2012-05-28 19:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 7:15 Marco Pessotto
2012-05-25 7:40 ` Hans Hagen
2012-05-25 7:45 ` luigi scarso
2012-05-25 7:50 ` luigi scarso
2012-05-25 7:52 ` Hans Hagen
2012-05-25 7:59 ` Marco Pessotto
2012-05-28 16:26 ` Marco Pessotto
2012-05-28 17:00 ` Hans Hagen
2012-05-28 17:11 ` Marco Pessotto
2012-05-28 18:51 ` Mojca Miklavec
2012-05-28 19:15 ` Hans Hagen
2012-05-28 19:20 ` Hans Hagen [this message]
2012-05-25 7:48 ` Marco Pessotto
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=4FC3D001.8050309@wxs.nl \
--to=pragma@wxs.nl \
--cc=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=taco@elvenkind.com \
/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).