ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Werner Hennrich <wehe@gmx.at>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: what happend to \writeline?
Date: Fri, 28 May 2021 18:05:39 +0200	[thread overview]
Message-ID: <03bedc2e-fa86-155c-82b2-e849dac3a79d@gmx.at> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 884 bytes --]

Hello everyone,

I'm looking into my environment's logging to trace a problem and realize
that \writeline is gone mute -
that is, the output of subsequent logging lines now gets joined up in
the same line, very hard to read...

I observe this in version: 2021.05.27 14:15, as well as in version:
2021.05.27 14:15
the last one I used where \writeline did write (and end) the logging
line was version: 2021.03.17 17:46.

    \def\log#1{
    \message{ logging: #1}
    \writeline
    logging #1\par
    }
    \starttext
    \log{the}
    \log{quick}
    \log{brown}
    \log{fox}
    \stoptext

used to log like this:

    logging: the
    logging: quick
    logging: brown
    logging: fox

but now:

logging: the logging: quick logging: brown logging: fox

Any idea how I can switch back the old behavior (on the new lmtx)?

Thanks you,
Werner


[-- Attachment #1.2: Type: text/html, Size: 2559 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2021-05-28 16:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 16:05 Werner Hennrich [this message]
2021-05-28 16:19 ` Hans Hagen
2021-05-31 14:06   ` Werner Hennrich

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=03bedc2e-fa86-155c-82b2-e849dac3a79d@gmx.at \
    --to=wehe@gmx.at \
    --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).