ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Lutz Haseloff via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: [NTG-context] Bug in context
Date: Sun, 14 May 2023 10:45:42 +0200	[thread overview]
Message-ID: <23b91ec5-fc4e-1167-1391-7c629d26f806@freedom.nl> (raw)
In-Reply-To: <DF966675-0926-473F-8EAA-F9DB27E98708@toppkieker.info>

On 5/13/2023 2:04 PM, Lutz Haseloff via ntg-context wrote:
> Hi Hans, hi all,
> 
> I mainly use ConTeXt in a server environment. So I am a friend of the 
> console.
> I found a small problem there.
> When I invoke context with parameter --ansi,
> the logfile remains empty.
> I tried Linux aarch64 and Windows64.
sure, as it makes no sense to write ansi sequences to the log so then 
that channel is turned off

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

      parent reply	other threads:[~2023-05-14  8:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-13 12:04 Lutz Haseloff via ntg-context
2023-05-13 12:35 ` Marco Patzer via ntg-context
2023-05-14  8:45 ` Hans Hagen via ntg-context [this message]

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=23b91ec5-fc4e-1167-1391-7c629d26f806@freedom.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@freedom.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).