From: Jorge del Conde Date: January 31 2002 9:45pm Subject: RE: MyCC 0.8.1 Bug Report List-Archive: http://lists.mysql.com/gui-tools/12 Message-Id: <004801c1aaa0$a33bf770$0100a8c0@WINDOWS> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0049_01C1AA6E.58A18770" ------=_NextPart_000_0049_01C1AA6E.58A18770 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Hi, I don't know why that happened. I will check it out. In the mean time, you can fix that by going to Options->General->[SQL Editor TAB] and select the syntax.txt file manually. >I've also looked at the two Syntax.txt files from the two difference installations in Notepad and the 0.0.8 doesn't look like a true text file where the 0.8.1 one does They are both pure text files ... it's just that in 0.8.1 the file is DOS readable (I.E. carriage return is represented as line-break + carriage return and the older version only had a line-break). but that's not the source of the problem! Regards, Jorge -- For technical support contracts, visit https://order.mysql.com/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Mr. Jorge del Conde / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer /_/ /_/\_, /___/\___\_\___/ Mexico City, Mexico <___/ www.mysql.com -----Original Message----- From: Donald Deacon [mailto:ddeacon@stripped] Sent: Thursday, January 31, 2002 10:28 AM To: 'mycc@stripped' Subject: MyCC 0.8.1 Bug Report The Syntax checking in 0.8.1 seems to be broken (I'm assuming it's because I now get the message that MyCC can't load the syntax.txt file). I've enclosed a couple of screenshots, one from MyCC 0.0.8 and one from 0.8.1, which show the error message and the lack of syntax checking. I've also looked at the two Sytax.txt files from the two difference installations in Notepad and the 0.0.8 doesn't look like a true text file where the 0.8.1 one does. I've tried copying the 0.0.8 version over to the 0.8.1 install but still no go. By the way, I did do a clean uninstall and reinstall first when I ran into this but then started running two separate installations to troubleshoot. <<008 Query.jpg>> <<081 Query.jpg>> Regards, Don Deacon ------=_NextPart_000_0049_01C1AA6E.58A18770 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Message
Hi,
 
I=20 don't know why that happened.  I will check it = out.
 
In the=20 mean time, you can fix that by going to Options->General->[SQL = Editor TAB]=20 and select the syntax.txt file manually.
 
>I've also=20 looked at the two Syntax.txt files from the two difference installations = in=20 Notepad and the 0.0.8 doesn't look like a true = text file=20 where the 0.8.1 one does
 
They = are both pure=20 text files ... it's just that in 0.8.1 the file is DOS readable (I.E. = carriage=20 return is represented as line-break + carriage return and the older = version only=20 had a line-break).
 
but = that's not the=20 source of the problem!
 
Regards,
Jorge
--
For technical support = contracts,=20 visit https://order.mysql.com/
 &= nbsp;=20 __  ___     ___ ____  __
  /  = |/  /_ __/ __/ __ \/ /    Mr. Jorge del Conde=20 <jorge@stripped>
 / /|_/ / // /\ \/ /_/ / /__   = MySQL=20 AB, Full-Time Developer
/_/  /_/\_, /___/\___\_\___/   = Mexico=20 City, Mexico
       = <___/  =20 www.mysql.com
-----Original Message-----
From: = Donald Deacon=20 [mailto:ddeacon@stripped]
Sent: Thursday, January = 31,=20 2002 10:28 AM
To: 'mycc@stripped'
Subject: = MyCC=20 0.8.1 Bug Report

The Syntax = checking in=20 0.8.1 seems to = be broken (I'm assuming it's because I now get the = message that MyCC=20 can't load the syntax.txt file). I've enclosed a couple of = screenshots, one=20 from MyCC 0.0.8 and one from 0.8.1, which show the error message and = the lack=20 of syntax checking.

I've also = looked at the=20 two Sytax.txt files from the two difference installations in Notepad = and the=20 0.0.8 doesn't look = like a true=20 text file where the 0.8.1 one does. I've tried copying the 0.0.8 = version over=20 to the 0.8.1 install but still no go.

By the = way, I did do a=20 clean uninstall and reinstall first when I ran into this but then = started=20 running two separate installations to troubleshoot.

<<008=20 Query.jpg>> <<081 Query.jpg>>

Regards,

Don=20 Deacon


------=_NextPart_000_0049_01C1AA6E.58A18770--