From: Tobias Burnus <burnus@gmx.de>
Cc: ntg-context@ntg.nl
Subject: Re: Use-Encoding
Date: Tue, 04 Jan 2000 18:29:44 +0100 [thread overview]
Message-ID: <38722E08.2C44C7E1@gmx.de> (raw)
In-Reply-To: <14449.52403.202079.307256@PC709.wkap.nl>
Hi Taco,
> Hm. In that case: perhaps you are using a tcx file and/or something
> else that changes the catcodes of the 8-bit chars back into 'letter'?
> enco-win sets then to \active, just like ~.
No, but:
> If Hans doesnt have the problem (neither have I, btw), then probably
> it makes sense to update your context distrib first, just in case.
This was using the beta Hans mentioned. Using the new 2000 version,
the problem went away (see my mail from yesterday, 20:42 CET).
Tobias
prev parent reply other threads:[~2000-01-04 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-03 18:48 Use-Encoding Tobias Burnus
2000-01-04 9:19 ` Use-Encoding Taco Hoekwater
2000-01-04 8:39 ` Use-Encoding Hans Hagen
2000-01-04 10:34 ` Use-Encoding Taco Hoekwater
2000-01-04 17:29 ` Tobias Burnus [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=38722E08.2C44C7E1@gmx.de \
--to=burnus@gmx.de \
--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).