delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
DomainKey-Signature: | a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id |
:list-unsubscribe:list-subscribe:list-archive:list-post | |
:list-help:sender:date:from:to:subject:message-id:reply-to | |
:references:mime-version:content-type:in-reply-to; q=dns; s= | |
default; b=sOxnrNj+ARUtkQTA5gdB1qGRJEz3H9nYEeX1o2njq3L9vNQeZPhfH | |
JCgzb6pWUQHtBcAC22xyqbn8SIMtn315Ixq1n+ZsxL0G+1OVdSkLyGwFmAk1xnPb | |
6gOS/DKvuZD1T2xXa+y/70kbDrS8K4Tmg6VADCXBlPoGya/NKholqE= | |
DKIM-Signature: | v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id |
:list-unsubscribe:list-subscribe:list-archive:list-post | |
:list-help:sender:date:from:to:subject:message-id:reply-to | |
:references:mime-version:content-type:in-reply-to; s=default; | |
bh=8Js3Okxqy1IUq98iI6OtxgGYO8s=; b=M1VB3uiBfQgLCoaxidcDM6gAx84X | |
IH3Ya06H6OdkQOQRkuu5xEG4DtHl13D5mSsxDwntangzCnhg5aTCJVoe1Q8p+U64 | |
w6WjJ17bqy8g0Js4x8NSYm/7vAaSPjRG/XcTO1mhRltl6weUST6GifV2pR0A7XxG | |
mx4E8QLvRExv9j4= | |
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 |
Authentication-Results: | sourceware.org; auth=none |
X-Virus-Found: | No |
X-Spam-SWARE-Status: | No, score=-4.1 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 |
X-HELO: | calimero.vinschen.de |
Date: | Wed, 1 Jul 2015 12:47:57 +0200 |
From: | Corinna Vinschen <corinna-cygwin AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: mintty system integration before release |
Message-ID: | <20150701104757.GI2918@calimero.vinschen.de> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
References: | <558EA4BB DOT 8080506 AT towo DOT net> <20150627145021 DOT GA23036 AT calimero DOT vinschen DOT de> <558EC861 DOT 2030903 AT towo DOT net> |
MIME-Version: | 1.0 |
In-Reply-To: | <558EC861.2030903@towo.net> |
User-Agent: | Mutt/1.5.23 (2014-03-12) |
--Bg2esWel0ueIH/G/ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Jun 27 17:59, Thomas Wolff wrote: > Am 27.06.2015 um 16:50 schrieb Corinna Vinschen: > >On Jun 27 15:27, Thomas Wolff wrote: > >>Hi, > >>Before a mintty release, I'd like to check Windows console issues with > >>mintty in Windows 10, > >>see https://github.com/mintty/mintty/issues/439 > >>As I don't have Windows 10, maybe someone can help out testing; > >>there is some kind of resource magic which I'm not familiar with (and I > >>remember it's been discussed here in some context); there is a file res= .mft > >>in mintty with these 2 lines: > >> <supportedOS Id=3D"{e2011457-1546-43c5-a5fe-008deee3d3f0}"/> <!-= - Vista > >>--> > >> <supportedOS Id=3D"{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/> <!-= - 7 --> > >>and I have a vague idea that specific lines should be added to facilita= te > >>seamless integration with Windows 8, 8.1, and 10. > >>Which lines could that be? > > $ strings /usr/lib/default-manifest.o > > > >If that's all there is to mintty's manifest, you can remove it and > >just build mintty without explicit manifest. > Well, there is also a res.rc without which mintty loses its Options menu. > And it does not compile without the res.mft, so I guess it's needed. In that case, yes. > >In that case GCC will apply /usr/lib/default-manifest.o to the executabl= e. > > > >Did you see my mail to you from 2015-06-23? > Yes, and I wonder how my response got lost :/ > I was remotely aware of that mailing list and had no plan to resurrect it > (unless you would convince me it's worth it); > I think it's sufficient for this project to have one of issue tracker or > mailing list/forum, not both. And an issue tracker has the valuable > advantage that you can close issues... Mailing lists allow discussing stuff before formally requesting something via issue tracker. E.g, user problems can be both, a user just having a thinko or a bug. ML discussions help to find out and avoid spurious issues in the issue tracker. Also, many people happily report bugs on mailing lists but don't want to be bothered with issue trackers which you have to login to. Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --Bg2esWel0ueIH/G/ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVk8VdAAoJEPU2Bp2uRE+gNEYP/0vJvWnxpGvy7q6VId7qvOIM jFCVhWuB3+NmXErKeAeoWii6wP/3/UpKsU/CVElpVZdwrRX5fGRay3NZeDP6Wgl6 ZGRE4CPrEuq/9J5D0LhPSeQTlbNhB65YFOsHgaWuUK7jCX5jmydtVbvqZJQ4sfEA 2whjcgkPSUdVP+Xhglzn6FIfjtzMwK4LgDKp0NgblR/DQE5GHeoFE5JPDluIx0Q/ zF8Qpc1+08KTPRyHpFi8mRUGwrM37O5aMdthy6vw6zR48je0kbIz+s1Awr42nIF9 pvlVspZi8PU9TGCLLbk7/5qUTNI3vuzG6iMxWq9qOkzG3QDyuDl9tbmQ/+raALPO w522JHx8hvlrNlXna4fgVeVwhb0ar8/2Dc96VPnC2/KaZHvQNEVEfjj+LG8geYaL OyZcVcGSKLX1oSmgHiUihLFzdxge4G+3SgWEQVGTG/8Qes2Ls7NxtDnqlBu1hcZa RNH4cKSR3p4Bi98S3IjTtIJF1pICblm5q2+lypmoP5HKwCj/MhYUINFVWNc14bHJ 6+gepLaJa7mqg2FEu3RVygZb5TSN0W3qWwBgwXV6H0RDnqDbe+6DRiUsPhZ6hkCu 33zn+CQVaPNIO5VrN0soUEEAerKrovf9qU7f4B5MZVNESHoTZU5d2VN8dHfn8par jevL1tfI4WODxT108v6O =MgnE -----END PGP SIGNATURE----- --Bg2esWel0ueIH/G/--
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |