zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@cambridgesiliconradio.com>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: Cygwin: environ problem
Date: Fri, 21 Jul 2000 14:11:20 +0100	[thread overview]
Message-ID: <0FY10078PTYVGJ@la-la.cambridgesiliconradio.com> (raw)
In-Reply-To: "Your message of Fri, 21 Jul 2000 15:56:45 +0400." <000101bff30a$be2cc1d0$21c9ca95@mow.siemens.ru>

I'll reply to both cygwin-related messages in one go:

Andrej wrote:
> We _could_try_ to directly manipulate __cygwin_environ, but I do not
> like it - who knows, where and how it is used. BTW comments imply, that
> DLLs should actually refer to __cygwin_environ :-)

Without some major rewriting, we may have to: the export-related machinery
assumes it has direct control of the (new) environment's memory.  This is
certainly a contender for the problems people have been seeing.  Strange it
usually works, though.

>> I have English Win2k with Russian locale set, and russian
>> characters are
>> shown as ? in ls output. While this is definitely Cygwin problem, Zsh
>> (often) completely hangs when completing such name ... sorry, it just
>> takes hours (well, a bit less :-) to give listing. It is so
>> slow, that I
>> really had impression it was hung.
> 
> While figuring out environ problem, I got a look at locale
> implementation in Cygwin. There is no :-) setlocale() is just a stub
> function that accepts "C" as locale name and nothing more. It does
> nothing :-))) And locale table contains only ASCII support. So, I
> wonder, how can it work correclty even for ISO-8859-1 charset.

Is there any chance this could be network-related?  My desktop PC has lots
of Samba-mounted drives in various paths, and completion is an absolute
pig, at least until things are cached.  I installed cygwin and zsh onto
someone's notebook this week, with no network dependencies, obviously, and
it's as fast as `normal', whatever normal means for a UNIX porting layer on
top of NT.  There are no serious network problems here which could cause
the difference if everything's running properly.

-- 
Peter Stephenson <pws@cambridgesiliconradio.com>
Cambridge Silicon Radio, Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK                          Tel: +44 (0)1223 392070


  reply	other threads:[~2000-07-21 13:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-21 11:56 Andrej Borsenkow
2000-07-21 13:11 ` Peter Stephenson [this message]
2000-07-21 13:39   ` Andrej Borsenkow
2000-07-24  8:14   ` Andrej Borsenkow
2000-07-24 10:39     ` Environ handling broken on Cygwin " Andrej Borsenkow
2000-07-24 10:57       ` Peter Stephenson
2000-07-25 10:49         ` Andrej Borsenkow
2000-08-16 13:28         ` Sourceforge development account Andrej Borsenkow
2000-08-16 13:35           ` Thomas Köhler
2000-08-16 13:41           ` Peter Stephenson
2000-08-21  1:25           ` Chmouel Boudjnah

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=0FY10078PTYVGJ@la-la.cambridgesiliconradio.com \
    --to=pws@cambridgesiliconradio.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).