headers
Christopher Faylor | 11 May 2011 17:36
Favicon

Re: Who's using "CYGWIN=tty" and why?

On Wed, May 11, 2011 at 11:02:40AM -0400, Edward Lam wrote:
>Personally, when I first ran into this problem, I never realized that 
>CYGWIN=tty would fix it. I did notice that there was a change in the 
>behavior between Cygwin B20 and the Cygwin 1.X releases but I only 
>realize now that this was probably the reason.

Ding, ding ding!

A B20 reference!  B20 was da bomb!
Permalink | Reply | 2 comments |
headers
Charles Wilson | 11 May 2011 17:54
Favicon

Re: Who's using "CYGWIN=tty" and why?

On 5/11/2011 11:36 AM, Christopher Faylor wrote:
> On Wed, May 11, 2011 at 11:02:40AM -0400, Edward Lam wrote:
>> Personally, when I first ran into this problem, I never realized that 
>> CYGWIN=tty would fix it. I did notice that there was a change in the 
>> behavior between Cygwin B20 and the Cygwin 1.X releases but I only 
>> realize now that this was probably the reason.
> 
> Ding, ding ding!
> 
> A B20 reference!  B20 was da bomb!

I realize this is sacrilege, but...somewhere in my archives I have an
old copy of full.exe from B20.1 (as well as the ancient cygutils add-on
packages; while the webpages for B20-era cygutils still exist at
http://cygutils.fruitbat.org/OBSOLETE/B20/index.html, the tarballs do
not.  I still have 'em somewhere...)

I ought to install it on XP or Vista and see just how awful it really
is, compared to modern versions. [/bad sacrilegious Chuck. No cookie!]

--
Chuck
Permalink | Reply | 1 comment |
headers
Christopher Faylor | 11 May 2011 18:19
Favicon

Re: Who's using "CYGWIN=tty" and why?

On Wed, May 11, 2011 at 11:54:55AM -0400, Charles Wilson wrote:
>On 5/11/2011 11:36 AM, Christopher Faylor wrote:
>> On Wed, May 11, 2011 at 11:02:40AM -0400, Edward Lam wrote:
>>> Personally, when I first ran into this problem, I never realized that 
>>> CYGWIN=tty would fix it. I did notice that there was a change in the 
>>> behavior between Cygwin B20 and the Cygwin 1.X releases but I only 
>>> realize now that this was probably the reason.
>> 
>> Ding, ding ding!
>> 
>> A B20 reference!  B20 was da bomb!
>
>I realize this is sacrilege, but...somewhere in my archives I have an
>old copy of full.exe from B20.1 (as well as the ancient cygutils add-on
>packages; while the webpages for B20-era cygutils still exist at
>http://cygutils.fruitbat.org/OBSOLETE/B20/index.html, the tarballs do
>not.  I still have 'em somewhere...)
>
>I ought to install it on XP or Vista and see just how awful it really
>is, compared to modern versions. [/bad sacrilegious Chuck. No cookie!]

Wasn't B20 auto-adaptable to new versions of Windows?  I suspect that,
if you just let it sit for a while, it will probably figure out how
to run on XP or Vista.

cgf
Permalink | Reply | 0 comments |
headers
Charles Wilson | 12 May 2011 16:03
Favicon

Re: GNU screen on Cygwin: Cannot seem to reattach, no matter what I try

On 5/11/2011 5:37 PM, Doug Morse wrote:
> P.S., BTW, gotta love the Romans: we're just like 'em! :) :)

Yeah: they progressed from republic, to empire, and then collapse due to
loose fiscal policy and over-extended military adventurism.  Bread and
circuses, man, bread and circuses.

History doesn't repeat itself -- but it does rhyme.  While things aren't
quite THAT bad, yet, there are definite similarities. (Looking at
President "I Won"'s appointees, czars, and assorted insane bureaucrats,
I'm reminded of Caligula's horse.)

--
Chuck
Permalink | Reply | 0 comments |
headers
Christopher Faylor | 20 May 2011 15:52
Favicon

Re: mk_all

On Fri, May 20, 2011 at 01:50:15AM -0700, kathy3826 wrote:
>Thanks guys, 
>
>it must have been make all.  And it seems I can bypass the one with x
>windows using source code.

I think probably replicating the process with consternation hides sea
monkeys.

cgf
(just wanted to get in on this "send incomprehensible statements to
a mailing list" thing - it looks like a lot of perl)
Permalink | Reply | 0 comments |
headers
Nellis, Kenneth | 23 May 2011 15:44
Picon
Favicon

internationalized text processing

Never posted here, but somewhat off-topic for the general Cygwin list...

I've been frustrated at the lack of guidance I've found online regarding 
how to build an internationalized text-based Unix application, in particular 
with reference to handling different character sets. For example, "man"
recognizes the character set specified in locale settings and uses Unicode 
punctuation appropriately. OTOH, the cygutils "ascii -e" utility does not 
recognize that my LANG specifies UTF-8 and outputs garbage for the 
extended half. Should this be considered a bug?

Closer to a real application, how should a program that reads, processes, 
and outputs text detect the character set so that it can process the text 
correctly? In the absence of a BOM in the input file, should the program 
blindly presume the locale-specified character set or analyze the file to 
guess it? And what advice is there for guessing? And, once detected, what 
takes precedence for output: the input file's character set or the locale 
setting?

I presume these issues are either settled or being debated somewhere.

--Ken Nellis
Permalink | Reply | 2 comments |
headers
Charles Wilson | 23 May 2011 16:51
Favicon

Re: internationalized text processing

On 5/23/2011 9:44 AM, Nellis, Kenneth wrote:
> OTOH, the cygutils "ascii -e" utility does not 
> recognize that my LANG specifies UTF-8 and outputs garbage for the 
> extended half. Should this be considered a bug?

No, ascii is deliberately intended to be stupid.  In fact, the -e option
itself is simply a workaround.  Originally, ascii always printed the
first 256 codepoints unconditionally.  With the change in 1.7 to
defaulting to UTF-8, we recognized that this was bad, and changed
ascii's default behavior to print only the first 128 codepoints, and
added -e to restore the original behavior.

A bit of history: the reason ascii was originally written was as a
diagnostic tool so that folks could check whether their font settings
and (old, obsolete, do not do this anymore: CYGWIN var contained
charset:oem) var settings were correct, so that the DOS line-drawing
characters could be used in a bash shell (running in a cmd box).

E.g. poor man's hack to get CP437 working

This predated "real" codepage and $LANG handling, in cygwin-1.7.

Now, with "real" $LANG handling, line draw stuff Just Works(tm) when
LANG=*.UTF-8, at least for ncurses programs: try
	/usr/lib/ncurses/test/lrtest.exe
from the ncurses-demo package, in a bash shell running in a cmd box (or
pstree -G).  So, the need for ascii (-e) as a diagnostic tool is
kinda...not needed anymore.

Thus, I'm not too fussed about this "bug" in an obsolete and no longer
(Continue reading)

Permalink | Reply | 1 comment |
headers
Buchbinder, Barry (NIH/NIAID) [E] | 24 May 2011 04:32
Picon

RE: internationalized text processing

Charles Wilson sent the following at Monday, May 23, 2011 10:51 AM
>Thus, I'm not too fussed about this "bug" in an obsolete and no longer
>needed diag tool -- but I also don't see a need to remove it from
>cygutils. So...mark this "bug" as either NOTABUG or WONTFIX. :-)

Please keep ascii.  I use it to find how various characters might be
coded (most commonly when dealing with a URL).  And there are enough
times that I'm interested in the upper characters that I've now
aliased ascii='ascii -e'.

Thanks,

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.
Permalink | Reply | 0 comments |
headers
Buchbinder, Barry (NIH/NIAID) [E] | 27 May 2011 18:30
Picon

RE: File Name Case Sensitivity & Globbing! Was: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?

On May 27 12:11, Corinna Vinschen wrote:
>So actually I got it wrong.

"Say it ain't so, Joe!  Say it ain't so!"

http://en.wikiquote.org/wiki/Shoeless_Joe_Jackson#Quotes_about_Jackson

http://en.wikipedia.org/wiki/Shoeless_Joe_Jackson#Black_Sox_scandal


Disclaimer: Statements made herein are not made on behalf of NIAID.
Permalink | Reply | 0 comments |
headers
Buchbinder, Barry (NIH/NIAID) [E] | 28 May 2011 16:45
Picon

RE: File Name Case Sensitivity & Globbing! Was: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?

Corinna Vinschen sent the following at Saturday, May 28, 2011 3:50 AM
>I'm not a native English speaker, but it's still frustrating how my
>words are misunderstood.

Personally, I think your English is excellent.  I don't remember ever
noticing anything that you've written that showed any evidence of you
being a non-native English speaker.  I not only didn't notice it, but
I noticed that I hadn't noticed it.)  And I say this having been
married for over twenty years to a non-native speaker whose written
English is excellent but, for the first decade and a half, showed
evidence of being written by a non-native speaker.

I find your writing to be careful and clear.  If there is a
misunderstanding of something you wrote, I always bet on the problem
being with the reader.

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.
Permalink | Reply | 1 comment |

Gmane