From: Earnie B. <ea...@us...> - 2007-04-19 12:47:40
|
Cesar: How are you doing with creating an MSYS release? Jason: How are you doing with templating Drupal? Earnie |
From: Cesar S. <ces...@gm...> - 2007-04-19 16:44:09
|
Earnie Boyd wrote: > Cesar: How are you doing with creating an MSYS release? > Hi, Earnie I have rebuilt most of MSYS. Comparing my /store directory with the dvlpr/var/msys/exe.dat and dll.dat, only the following are still pending: patch.exe vim.exe rxvt.exe libW11.dll I couldn't find patch in the repository, I will fetch the upstream sources. The vim configure script complains about termcap being unusable, even if it is installed. I will investigate this next. In the rxvt compile step, it doesn't find some X include file (Intrinsics.h). It should not be needed, because of the W11 emulation layer. I will take a deeper look at the rxvt configuration options. Regards, Cesar |
From: Earnie B. <ea...@us...> - 2007-04-19 18:08:00
|
Quoting Cesar Strauss <ces...@gm...>: > > I couldn't find patch in the repository, I will fetch the upstream sources. > IIRC patch is a breeze. > The vim configure script complains about termcap being unusable, even > if it is installed. I will investigate this next. > I don't remember VIM too much, probably just a copy of Cygwin's source and adding __MSYS__ for __CYGWIN__, etc. > In the rxvt compile step, it doesn't find some X include file > (Intrinsics.h). It should not be needed, because of the W11 emulation > layer. I will take a deeper look at the rxvt configuration options. > RXVT is a PITA. A lot of manual intervention. You need to build in the source directory and you need to build the libW11.dll first; i.e.: cd into the directory a execute make. Let me know if you have issues. Earnie |
From: Charles W. <cwi...@us...> - 2007-04-19 19:46:27
|
Earnie Boyd wrote: > RXVT is a PITA. A lot of manual intervention. You need to build in > the source directory and you need to build the libW11.dll first; i.e.: > cd into the directory a execute make. Let me know if you have issues. I'd recommend taking a look at the current cygwin rxvt package. Since upstream rxvt development is dead, and our original maintainer for the cygwin port vanished, I've taken over and attempted to smooth the build machinery - at least for cygwin. Upside to my changes: basic sequence of steps to build is well documented (err, well, if you consider a cygport autobuild script "documentation" compared to vague and occasionally incorrect README statements). cygwin -src package includes pristine cvs checkout tarball from rxvt HEAD as of last update patch to fix makefiles for automated building patch to apply the xpm inbuilt sources for --enable-xpm .cygport file "documenting" build procedure I don't *think* I have done anything that would break mingw -- but then, I haven't tried to build under msys, either. -- Chuck |
From: Earnie B. <ea...@us...> - 2007-04-19 21:34:14
|
Quoting Charles Wilson <cwi...@us...>: > Earnie Boyd wrote: > >> RXVT is a PITA. A lot of manual intervention. You need to build in >> the source directory and you need to build the libW11.dll first; i.e.: >> cd into the directory a execute make. Let me know if you have issues. > > I'd recommend taking a look at the current cygwin rxvt package. Since > upstream rxvt development is dead, and our original maintainer for the > cygwin port vanished, I've taken over and attempted to smooth the build > machinery - at least for cygwin. > > Upside to my changes: basic sequence of steps to build is well > documented (err, well, if you consider a cygport autobuild script > "documentation" compared to vague and occasionally incorrect README > statements). cygwin -src package includes > pristine cvs checkout tarball from rxvt HEAD as of last update > patch to fix makefiles for automated building > patch to apply the xpm inbuilt sources for --enable-xpm > .cygport file "documenting" build procedure > > I don't *think* I have done anything that would break mingw -- but then, > I haven't tried to build under msys, either. > There may have been Cygwin specific additions that haven't been added to MSYS that would cause issues witha current Cygwin bundle. Don't know that, just throwing it up in the air for a toss. I remember modifing the .rc file to add the MSYS icon. Oh, and there is a submitted ICON replacement I was looking at and have been using locally. Chuck, would it be possible to Windowize RXVT proper? Earnie |
From: Cesar S. <ces...@gm...> - 2007-04-20 02:35:53
|
Charles Wilson wrote: > Earnie Boyd wrote: > > > RXVT is a PITA. A lot of manual intervention. You need to build in > > the source directory and you need to build the libW11.dll first; i.e.: > > cd into the directory a execute make. Let me know if you have issues. > > I'd recommend taking a look at the current cygwin rxvt package. Since > upstream rxvt development is dead, and our original maintainer for the > cygwin port vanished, I've taken over and attempted to smooth the build > machinery - at least for cygwin. > > Upside to my changes: basic sequence of steps to build is well > documented (err, well, if you consider a cygport autobuild script > "documentation" compared to vague and occasionally incorrect README > statements). cygwin -src package includes > pristine cvs checkout tarball from rxvt HEAD as of last update > patch to fix makefiles for automated building > patch to apply the xpm inbuilt sources for --enable-xpm > .cygport file "documenting" build procedure > > I don't *think* I have done anything that would break mingw -- but then, > I haven't tried to build under msys, either. > Thanks, it was very helpful. I have used your instructions and managed to build the current Cygwin version of rxvt on MSYS, with only minor code adjustments. As it turns out, it also helped me to build the MSYS version that I was having trouble with in the first place. Regards, Cesar |
From: Charles W. <cwi...@us...> - 2007-04-21 03:22:38
|
Cesar Strauss wrote: > Thanks, it was very helpful. I have used your instructions and managed > to build the current Cygwin version of rxvt on MSYS, with only minor > code adjustments. > > As it turns out, it also helped me to build the MSYS version that I > was having trouble with in the first place. Glad to hear both. And if I haven't mentioned it before, thank you for taking on the responsibility for shepherding the 1.0.11 release. -- Chuck |
From: <ja...@so...> - 2007-04-19 17:46:09
|
Earnie Boyd writes: > > Jason: How are you doing with templating Drupal? > I got real busy at work for a bit there, so I had less time for working with the Drupal. I have a template that is pretty similar to the current format, which is basically done except a few tweaks. --Jason Craig |
From: Earnie B. <ea...@us...> - 2007-04-19 18:17:02
|
Quoting ja...@so...: > Earnie Boyd writes: >> >> Jason: How are you doing with templating Drupal? >> > > I got real busy at work for a bit there, so I had less time for working with > the Drupal. I have a template that is pretty similar to the current format, > which is basically done except a few tweaks. > I'm planning in a couple of weeks to add a drupal directory and executing the install script. I'll let you know when that happens so we can get your theme up. Should we allow users to choose there own theme for viewing MinGW? Maybe something to think about for the future. Earnie |
From: <ja...@so...> - 2007-04-19 19:29:41
|
Earnie Boyd writes: > I'm planning in a couple of weeks to add a drupal directory and > executing the install script. I'll let you know when that happens so > we can get your theme up. Should we allow users to choose there own > theme for viewing MinGW? Maybe something to think about for the future. I'm personally not a huge fan of allowing users to change their theme, but like you said, it's something to think about. --Jason |
From: Julien L. <ju...@fa...> - 2007-04-22 07:24:56
|
On 19/04/2007 20:16, Earnie Boyd wrote: > Quoting ja...@so...: > >> Earnie Boyd writes: >>> Jason: How are you doing with templating Drupal? > > I'm planning in a couple of weeks to add a drupal directory and > executing the install script. So is a MediaWiki totally out of the works? Will there be a MediaWiki plugin to Drupal, or some sort of wiki plugin to Drupal? Julien |
From: <ja...@so...> - 2007-04-22 16:56:11
|
Julien Lecomte writes: > On 19/04/2007 20:16, Earnie Boyd wrote: >> Quoting ja...@so...: >> >>> Earnie Boyd writes: >>>> Jason: How are you doing with templating Drupal? >> >> I'm planning in a couple of weeks to add a drupal directory and >> executing the install script. > > So is a MediaWiki totally out of the works? Will there be a MediaWiki > plugin to Drupal, or some sort of wiki plugin to Drupal? > There will be some area for the current 'wiki' pages, wether it will actually be a wiki or not is up in the air. I personally don't think it is necessary to make the area a wiki area, I think we can massage what is already available in Drupal enough to suffice for our needs. --Jason Craig |
From: Earnie B. <ea...@us...> - 2007-04-22 21:38:47
|
Quoting ja...@so...: > Julien Lecomte writes: > >> On 19/04/2007 20:16, Earnie Boyd wrote: >>> Quoting ja...@so...: >>> >>>> Earnie Boyd writes: >>>>> Jason: How are you doing with templating Drupal? >>> >>> I'm planning in a couple of weeks to add a drupal directory and >>> executing the install script. >> >> So is a MediaWiki totally out of the works? Will there be a MediaWiki >> plugin to Drupal, or some sort of wiki plugin to Drupal? >> > > There will be some area for the current 'wiki' pages, wether it will > actually be a wiki or not is up in the air. I personally don't think it is > necessary to make the area a wiki area, I think we can massage what is > already available in Drupal enough to suffice for our needs. > Initially we will link to the current phpwiki with plans to migrate the data into drupal with a content type named wiki. We will allow authenticated users the ability to edit any wiki type page just like we do with phpwiki. Please do not rehash what has already been discussed about this method. I want to thank Julien for his work with MediaWiki and had it progressed a little more quickly perhaps we would have used it. I don't think what Julien did was non important or not good enough. On the contrary I like having options. I just found something else I like better and have promoted it. Earnie |
From: Julien L. <ju...@fa...> - 2007-04-24 09:27:59
|
Earnie Boyd wrote: > Initially we will link to the current phpwiki with plans to migrate the > data into drupal with a content type named wiki. We will allow > authenticated users the ability to edit any wiki type page just like we > do with phpwiki. I'm just burning with excitement to see the new site, even in alpha state; kind of like a kid waiting for midnight on Christmas eve ;-) And I have much documentation on my hands, currently all in plain text format (in txt files!), waiting to be added to the new site. At this moment, I even have free time to do this; thus my anticipation! Julien |
From: Kai T. <Kai...@on...> - 2007-04-25 14:46:46
|
SGVsbG8sDQoNCkkgd2FudCBqdXN0IHRvIGtub3csIGlmIHRoZXNlIHVwbG9hZHMgSSBkaWQgYXJl IG9mIHNvbWUgaW50ZXJyZXN0IHRvIHlvdSA/DQpBbmQgb2YgY291cnNlLCBob3cgdGhlIHBsYW5z IHRvIHN1cHBvcnQgdzY0IGFyZSBnb2luZyBvbiA/DQoNClJlZ2FyZHMsDQogaS5BLiBLYWkgVGll dHoNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQogIE9uZVZpc2lvbiBTb2Z0 d2FyZSBFbnR3aWNrbHVuZ3MgR21iSCAmIENvLiBLRw0KICBEci4tTGVvLVJpdHRlci1TdHJhw59l IDkgLSA5MzA0OSBSZWdlbnNidXJnDQogIFRlbDogKzQ5LigwKTk0MS43ODAwNC4wIC0gRmF4OiAr NDkuKDApOTQxLjc4MDA0LjQ4OSAtIHd3dy5PbmVWaXNpb24uY29tDQogIENvbW1lcnpiYW5rIFJl Z2Vuc2J1cmcgLSBCTFogNzUwIDQwMCA2MiAtIEtvbnRvIDYwMTEwNTANCiAgSGFuZGVsc3JlZ2lz dGVyOiBIUkEgNjc0NCwgQW10c2dlcmljaHQgUmVnZW5zYnVyZw0KICBLb21wbGVtZW50w6RyaW46 IE9uZVZpc2lvbiBTb2Z0d2FyZSBFbnR3aWNrbHVuZ3MgVmVyd2FsdHVuZ3MgR21iSA0KICBEci4t TGVvLVJpdHRlci1TdHJhw59lIDkg4oCTIDkzMDQ5IFJlZ2Vuc2J1cmcNCiAgSGFuZGVsc3JlZ2lz dGVyOiBIUkIgODkzMiwgQW10c2dlcmljaHQgUmVnZW5zYnVyZyAtIEdlc2Now6RmdHNmw7xocmVy OiANClVscmlrZSBEw7ZobGVyLCBNYW51ZWxhIEtsdWdlcg0KDQo= |
From: Chris S. <ir0...@gm...> - 2007-05-01 01:49:10
|
Hey, Sorry for the late reply, I've been out-of-the-loop for a bit... > I want just to know, if these uploads I did are of some interrest to you ? I took a look and they look good. I noticed it looks like you took the whole /mingw/include directory. I can start incorporating the changes in to mingw-runtime / w32api if everyone is in agreement? I'm assuming the changes to these files came from a public source (i.e. msdn.microsoft.com) and not out of MS headers (can't remember if you answered that already, but want to be certain)? > And of course, how the plans to support w64 are going on ? In terms of the GCC integration of the 64-bit additions, I can't comment. From what I remember you were following up with the upstream GCC maintainers? How did that go? Chris -- Chris Sutcliffe http://ir0nh34d.googlepages.com http://ir0nh34d.blogspot.com http://emergedesktop.org |
From: Kai T. <Kai...@on...> - 2007-05-02 08:41:20
|
bWluZ3ctZHZscHItYm91bmNlc0BsaXN0cy5zb3VyY2Vmb3JnZS5uZXQgd3JvdGUgb24gMDEuMDUu MjAwNyAwMzo0ODo1OToNCg0KPiBJIHRvb2sgYSBsb29rIGFuZCB0aGV5IGxvb2sgZ29vZC4gIEkg bm90aWNlZCBpdCBsb29rcyBsaWtlIHlvdSB0b29rDQo+IHRoZSB3aG9sZSAvbWluZ3cvaW5jbHVk ZSBkaXJlY3RvcnkuICBJIGNhbiBzdGFydCBpbmNvcnBvcmF0aW5nIHRoZQ0KPiBjaGFuZ2VzIGlu IHRvIG1pbmd3LXJ1bnRpbWUgLyB3MzJhcGkgaWYgZXZlcnlvbmUgaXMgaW4gYWdyZWVtZW50Pw0K DQpUaGF0IHdvdWxkIGJlIGZpbmUgOykNCg0KPiBJJ20gYXNzdW1pbmcgdGhlIGNoYW5nZXMgdG8g dGhlc2UgZmlsZXMgY2FtZSBmcm9tIGEgcHVibGljIHNvdXJjZQ0KPiAoaS5lLiBtc2RuLm1pY3Jv c29mdC5jb20pIGFuZCBub3Qgb3V0IG9mIE1TIGhlYWRlcnMgKGNhbid0IHJlbWVtYmVyIGlmDQo+ IHlvdSBhbnN3ZXJlZCB0aGF0IGFscmVhZHksIGJ1dCB3YW50IHRvIGJlIGNlcnRhaW4pPw0KDQpJ biBkZWVkLCBJIHRvb2sgdGhlIGhlYWRlciBzdHJ1Y3R1cmUgZnJvbSBtaW5ndyBhbmQgYWRqdXN0 IGl0IHdpdGggdGhlIA0KTVNETiBpbmZvcm1hdGlvbi4gU29tZSBwYXJ0cyAtIGFzIGNvcmJhLCBJ IGFkZGVkIGEgbG90IG5ldyBBUEkncyBhbmQgSSANCnRyaWVkIHRvIG1ha2UgaXQgYXMgbXVjaCBN UyBjb21wbGFpbnQgYXMgcG9zc2libGUuDQpJIHRoaW5rIHRoZXJlIGFyZSBzb21lIGxhY2tzIGlu IG1hdGguaCB1c2luZyBleHRlcm4gX19pbmxpbmUgbWV0aG9kcywgYnV0IA0Kbm9uZSByZWFsbHkg aGFyZCBvbmVzIEFGQUlDUy4NCg0KPiA+IEFuZCBvZiBjb3Vyc2UsIGhvdyB0aGUgcGxhbnMgdG8g c3VwcG9ydCB3NjQgYXJlIGdvaW5nIG9uID8NCj4gDQo+IEluIHRlcm1zIG9mIHRoZSBHQ0MgaW50 ZWdyYXRpb24gb2YgdGhlIDY0LWJpdCBhZGRpdGlvbnMsIEkgY2FuJ3QNCj4gY29tbWVudC4gIEZy b20gd2hhdCBJIHJlbWVtYmVyIHlvdSB3ZXJlIGZvbGxvd2luZyB1cCB3aXRoIHRoZSB1cHN0cmVh bQ0KPiBHQ0MgbWFpbnRhaW5lcnM/ICBIb3cgZGlkIHRoYXQgZ28/DQoNCkdDQyB0cnVuayBoYXMg YWxscmVhZHkgdGhlIHg4Nl82NCBtaW5ndzMyIHRhcmdldCB3b3JraW5nLiBBRkFJIHRyaWVkLCBJ IA0Kd2FzIGFibGUgdG8gbWFrZSBhbGwgbGFuZ3VhZ2VzIGFuZCBhbGwgbGlicyBiZXNpZGUgQURB LCBKQVZBLCBhbmQgdHJlZWNvZGUgDQpjb21waWxpbmcuDQpJIHRoaW5rLCB0byBtb3ZlIHRoZSBw YXRjaCA0LjIgc2hvdWxkIGJlIG5vdCB0byBoYXJkLCBidXQgb24gNC4yIHRoZXJlIGFyZSANCnNv bWUgbWFqb3IgcHJvYmxlbXMgd2l0aCB4ODZfNjQgY29kZSBnZW5lcmF0aW9uIEFGQUlLLg0KDQpS ZWdhcmRzLA0KIGkuQS4gS2FpIFRpZXR6DQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLQ0KICBPbmVWaXNpb24gU29mdHdhcmUgRW50d2lja2x1bmdzIEdtYkggJiBDby4gS0cNCiAg RHIuLUxlby1SaXR0ZXItU3RyYcOfZSA5IC0gOTMwNDkgUmVnZW5zYnVyZw0KICBUZWw6ICs0OS4o MCk5NDEuNzgwMDQuMCAtIEZheDogKzQ5LigwKTk0MS43ODAwNC40ODkgLSB3d3cuT25lVmlzaW9u LmNvbQ0KICBDb21tZXJ6YmFuayBSZWdlbnNidXJnIC0gQkxaIDc1MCA0MDAgNjIgLSBLb250byA2 MDExMDUwDQogIEhhbmRlbHNyZWdpc3RlcjogSFJBIDY3NDQsIEFtdHNnZXJpY2h0IFJlZ2Vuc2J1 cmcNCiAgS29tcGxlbWVudMOkcmluOiBPbmVWaXNpb24gU29mdHdhcmUgRW50d2lja2x1bmdzIFZl cndhbHR1bmdzIEdtYkgNCiAgRHIuLUxlby1SaXR0ZXItU3RyYcOfZSA5IOKAkyA5MzA0OSBSZWdl bnNidXJnDQogIEhhbmRlbHNyZWdpc3RlcjogSFJCIDg5MzIsIEFtdHNnZXJpY2h0IFJlZ2Vuc2J1 cmcgLSBHZXNjaMOkZnRzZsO8aHJlcjogDQpVbHJpa2UgRMO2aGxlciwgTWFudWVsYSBLbHVnZXIN Cg0K |
From: Earnie B. <ea...@us...> - 2007-05-01 11:23:48
|
Quoting Chris Sutcliffe <ir0...@gm...>: > Hey, > > Sorry for the late reply, I've been out-of-the-loop for a bit... > >> I want just to know, if these uploads I did are of some interrest to you ? > > I took a look and they look good. I noticed it looks like you took > the whole /mingw/include directory. I can start incorporating the > changes in to mingw-runtime / w32api if everyone is in agreement? > Patches to the current Cygwin winsup/mingw and winsup/w32api CVS is best to help ease maintainer pain. > I'm assuming the changes to these files came from a public source > (i.e. msdn.microsoft.com) and not out of MS headers (can't remember if > you answered that already, but want to be certain)? > A must. We must be able to point to the documentation for the source changes. Earnie |
From: Chris S. <ir0...@gm...> - 2007-05-01 15:30:27
|
> > I took a look and they look good. I noticed it looks like you took > > the whole /mingw/include directory. I can start incorporating the > > changes in to mingw-runtime / w32api if everyone is in agreement? > > Patches to the current Cygwin winsup/mingw and winsup/w32api CVS is > best to help ease maintainer pain. Agreed, I'd much rather have the patches instead of having to create them myself. If that is problematic, I'll make the patches myself. Chris -- Chris Sutcliffe http://ir0nh34d.googlepages.com http://ir0nh34d.blogspot.com http://emergedesktop.org |
From: Cesar S. <ces...@gm...> - 2007-04-20 02:48:54
|
Earnie Boyd wrote: > Quoting Charles Wilson <cwi...@us...>: > > > Earnie Boyd wrote: > > > >> RXVT is a PITA. A lot of manual intervention. You need to build in > >> the source directory and you need to build the libW11.dll first; i.e.: > >> cd into the directory a execute make. Let me know if you have issues. Thanks, it worked. > > > > I'd recommend taking a look at the current cygwin rxvt package. Since > > upstream rxvt development is dead, and our original maintainer for the > > cygwin port vanished, I've taken over and attempted to smooth the build > > machinery - at least for cygwin. > > This worked too, so we now have a choice. > > > > I don't *think* I have done anything that would break mingw -- but then, > > I haven't tried to build under msys, either. > > > > There may have been Cygwin specific additions that haven't been added > to MSYS that would cause issues witha current Cygwin bundle. Don't > know that, just throwing it up in the air for a toss. I remember > modifing the .rc file to add the MSYS icon. Oh, and there is a > submitted ICON replacement I was looking at and have been using locally. > I think I may have located the icon you refer: http://sourceforge.net/tracker/index.php?func=detail&aid=940998&group_id=2435&atid=302435 I modified the .rc file accordingly. Regards, Cesar |
From: Earnie B. <ea...@us...> - 2007-04-20 12:38:00
|
Quoting Cesar Strauss <ces...@gm...>: >> >> There may have been Cygwin specific additions that haven't been added >> to MSYS that would cause issues witha current Cygwin bundle. Don't >> know that, just throwing it up in the air for a toss. I remember >> modifing the .rc file to add the MSYS icon. Oh, and there is a >> submitted ICON replacement I was looking at and have been using locally. >> > > I think I may have located the icon you refer: > > http://sourceforge.net/tracker/index.php?func=detail&aid=940998&group_id=2435&atid=302435 > > I modified the .rc file accordingly. > That looks like the correct one based on the Accpeted and "Include In The Next Release". Earnie |
From: Keith M. <kei...@us...> - 2007-04-20 22:39:53
|
On Thursday 19 April 2007 19:07, Earnie Boyd wrote: > > In the rxvt compile step, it doesn't find some X include file > > (Intrinsics.h). It should not be needed, because of the W11 > > emulation layer. I will take a deeper look at the rxvt > > configuration options. > > RXVT is a PITA. On the subject of RXVT, Brian Dessent recently suggested on MinGW-MSYS, that the default MSYS startup mode should be made `--norxvt', to avoid recurring questions relating to pty problems. I asked for a vote on this, and while only a handful of users cared enough to reply, those who did were unanimously of this same opinion. I think we should address this, for the upcoming release. Regards, Keith. |
From: Charles W. <cwi...@us...> - 2007-04-21 03:19:14
|
Earnie Boyd wrote: > There may have been Cygwin specific additions that haven't been added > to MSYS that would cause issues witha current Cygwin bundle. Don't > know that, just throwing it up in the air for a toss. Possible -- although I believe Cesar's success with both rxvt variants tends to suggest that any such differences are at best minimal. > I remember > modifing the .rc file to add the MSYS icon. Oh, and there is a > submitted ICON replacement I was looking at and have been using locally. Oooh, shiny. > Chuck, would it be possible to Windowize RXVT proper? Depends on what you mean. If you mean rip the guts out and make rxvt call Windows GDI directly, then no. The whole design of rxvt was "xterm without using the xt library". This means it deliberately makes direct xlib calls all OVER the place. The most localized place to "plug in" GDI is...provide a replacement for xlib -- which is what the current rxvt does. If you mean fork it and clean up the build process, libW11, xpm, and all, sure. But, again, from Cesar's report it seems that is not necessary. -- Chuck |
From: Earnie B. <ea...@us...> - 2007-04-22 21:58:14
|
Quoting Charles Wilson <cwi...@us...>: > >> Chuck, would it be possible to Windowize RXVT proper? > > Depends on what you mean. If you mean rip the guts out and make rxvt > call Windows GDI directly, then no. The whole design of rxvt was "xterm This is what I meant and was just asking. Too bad we can't get the pty working like we need it too. Earnie |
From: Charles W. <cwi...@us...> - 2007-04-21 03:34:38
|
Keith Marshall wrote: > On the subject of RXVT, Brian Dessent recently suggested on MinGW-MSYS, > that the default MSYS startup mode should be made `--norxvt', to avoid > recurring questions relating to pty problems. > > I asked for a vote on this, and while only a handful of users cared > enough to reply, those who did were unanimously of this same opinion. > I think we should address this, for the upcoming release. I believe that all (or almost all?) of those who felt strongly enough about the issue agreed with you and Brian. Personally, I despise the windows cmd box, but I recognize that others with less animosity toward to cmd window might be more upset than I with (a) occasional lockups on resize (b) weird line wrapping issues at the command prompt (c) and the usual pty issues with native apps -- especially as mingw-gcc IS a native app I can deal with a, b, and c -- and I can also change my shortcuts to supply --yes-I-really-want-rxvt. But it's probably best if the default msys shell avoids all of the above. Since, as a matter of policy, I agreed with the trend of the responses -- but didn't feel strongly about it -- I kept my peace. But go ahead and add my vote to the -norxvt of the debate, if you like. -- Chuck |