On May 23 21:14, Andy Koppe wrote: > On 23 May 2011 12:50, Corinna Vinschen wrote: > > On May 20 17:09, Yaakov (Cygwin/X) wrote: > >> The setup.exe download is still 2.738. Could it be updated to 2.749 > >> to include jturney's recent bug fixes? > > > > I'd like to fix the mintty issue first. > > > > So, do we swtch to mintty as default terminal, yes or no? > > > > If we switch to mintty we don't need the Cygwin.bat file anymore. But, > > shouldn't we keep it anyway for people who maintain some handmade symlink > > to it? > > Yes, I think so. > > > If so, should we stick to the content of Cygwin.bat as is, or should > > we change it to call mintty, too? > > Better not, so as not to change people's existing setup. And because > it would flash up a console for the .bat. > > > And who's going to create the patches? > > I suppose that should be me, but my spare time is rather limited at > the moment and I still owe a patch or two for other things.
I'm just trying a setup.exe patch which creates "Cygwin Terminal" desktop and start menu entries which point to "mintty -". I just have to get rid of my build environment problems... > What it should do: > 1) Invoke the user's default shell as set in /etc/passwd as a login > shell. (This is what the mintty start menu shortcut currently does) > 2) Invoke bash as a login shell. #1, definitely. > d) "Cygwin Terminal": Linux desktops usually have "Terminal" entries > in their menus. Yep. > I also think the console's start menu entry in the Cygwin folder > should be kept, perhaps with a new name. "Console" vs "Terminal"? Why? Other than that, the docs need some tweaking as well, I guess. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
