X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 	tests=AWL,BAYES_00,SPF_PASS,TVD_SPACED_SUBJECT_WORD3
X-Spam-Check-By: sourceware.org
Message-ID: <495A2BF2.7040409@elite-systems.org>
Date: Tue, 30 Dec 2008 09:10:58 -0500
From: Robert Pendell <shinji AT elite-systems DOT org>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: MinTTY
References: <495917BA DOT 1090401 AT gmail DOT com> <6910a60812291430i6e2c394agcedab557bbf6f673 AT mail DOT gmail DOT com> <4959B7F7 DOT 9020400 AT cwilson DOT fastmail DOT fm> <495A1811 DOT 3030209 AT gmail DOT com>
In-Reply-To: <495A1811.3030209@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Andy Koppe wrote:
> Charles Wilson wrote:
> 
>> It will be interesting to play with the codepage support
>> (already present, apparently) in this terminal -- perhaps UTF-8 +
>> cygwin-1.7...
> 
> That would be interesting indeed, and hopefully I haven't broken any of
> PuTTY's Unicode support. Just set the codepage to UTF-8 to try (assuming
> MinTTY compiles and runs on 1.7, which I haven't yet tried).

It runs on 1.7 but does not appear to execute the shell as a login one.
 I use bash and .bash_profile never gets executed when using MinTTY
directly.  I can help you debug it if you wish.

> 
> Is there an overview somewhere about the Unicode features in cygwin-1.7?
> 
>> The obvious similarity between MinTTY and rxvt is that both use pty
>> emulation to communicate with the inferior, which can sometimes cause
>> issues when running "native" (e.g. non-cygwin) applications. But, that's
>> not a /defect/, per se, just something that users should be aware of.
> 
> Good point. I should mention that on the project page.
> 
>> This looks like a great addition to the cygwin-related toolbox. I look
>> forward to seeing where you go with this in the future.
> 
> First off, documentation. :)
> 
> Thanks,
> Andy
> 

Beyond that one little bit you did a great job otherwise.

The create_shortcut.js script is assuming a 1.5 setup by searching for
and parsing the 1.5 registry keys which may or may not exist on a 1.7
setup.  While I can setup this myself manually (I actually already did)
it may be a good idea to check out the /etc/fstab file format and parse
that.  The starter dir will be located at HKLM\SOFTWARE\Cygwin\setup
with the parameter 'rootdir'.  It is a string dir.  There is no trailing
slash on my install here.

BTW, If anyone is having trouble running the script the below command
will allow you to run it regardless.  .js is also associated with
JavaScript and not just JScript.  I had .js associated to Notepad+ on my
system so it wasn't just a double-click and go.  Maybe re-write the
script as VBScript instead?

In a command prompt with the location of the file as the current dir
(e.g. if the file is on your desktop then %USERPROFILE%\Desktop should
be your current dir)
cscript //E:JScript desktop_shortcut.js

You may replace cscript with wscript if you want window popups instead.


-- 
Robert Pendell
shinji AT elite-systems DOT org

"A perfect world is one of chaos."

Thawte Web of Trust Notary
CAcert Assurer

Some message may be signed digitally
Digital Signature SHA1 Fingerprint
0B:2D:4C:3A:23:EE:2B:69:4E:A1:2B:F4:3F:A3:B9:D7:0A:18:2A:DB

Using CAcert to create certificate.  If you do not already have the root
certificates imported for this CA you can get them at http://www.cacert.org.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/