Fwd: graphical took kit

Yes, exactly. Thanks for the references. The error has been pointed out. It is not an emacs error, but one in cygwin's interal libs/code, as pointed out in the e-mail references below. This bug in memory utilization should be fixed by someone familiar with it, should be able to pick out the s

Re: lastlog command?

On March 18, 2007, Larry Hall (Cygwin) wrote: > Dan Harkless wrote: [...] > > Are there any plans to port the lastlog command to Cygwin? It would seem > > like it ought to be a pretty straightforward one. > > Packages (with particular utilities) are contributed by volunteers. See >

Fwd: glib/graphical took kit mem error

Yes, exactly. Thanks for the references. The error has been pointed out. It is not an emacs error, but one in cygwin's interal libs/code, as pointed out in the e-mail references below. This bug in memory utilization should be fixed by someone familiar with it, should be able to pick out the s

Re: graphical took kit

Yes, exactly. Thanks for the references. The error has been pointed out. It is not an emacs error, but one in cygwin's interal libs/code, as pointed out in the e-mail references below. This bug in memory utilization should be fixed by someone familiar with it, should be able to pick out the s

Re: slow bash spawn

* Marc Compere (Sun, 18 Mar 2007 13:27:31 + (UTC)) > The recent setup.exe update has caused bash.exe to have startup times approx. > 10x longer than before. sh.exe starts pretty quickly but bash.exe via > cygwin.bat takes ~30 seconds to start. Took just a couple of seconds before. > > Cp

Re: lastlog command?

Dan Harkless wrote: Howdy. It seems strange that on Cygwin, the /var/log/lastlog file is maintained (at least by openssh -- not sure if other types of logins go there), yet there's no 'lastlog' command. I understand that openssh uses it to let you know when your last login was (once you've logg

RE: Updating cygwin and X

From: Richard Foulk; Sunday, March 18, 2007 2:36 AM > > What is the proper way to install everything and then update it from time to time? > > The setup.exe program says it's to be used for installs and updates but only seems to know how to install, reinstall or uninstall. Nothing specific to upda

RE: slow bash spawn

On 18 March 2007 13:28, Marc Compere wrote: > The recent setup.exe update has caused bash.exe to have startup times > approx. 10x longer than before. sh.exe starts pretty quickly but bash.exe > via cygwin.bat takes ~30 seconds to start. Took just a couple of seconds > before. Cpu is nowhere near

slow bash spawn

The recent setup.exe update has caused bash.exe to have startup times approx. 10x longer than before. sh.exe starts pretty quickly but bash.exe via cygwin.bat takes ~30 seconds to start. Took just a couple of seconds before. Cpu is nowhere near pinned, hovering around 3% or 5%. Each bash pro

w3m on Vista crashing (Ok on XP)

Hi when I try to use w3m on Vista (Ok on XP) I'm getting the dreaded "Your program has stopped working" screen. In fact I cannot even do > w3m --version Tried Googling for any previous posts -- zzapper http://www.rayninfo.co.uk/vimtips.html -- Unsubscribe info: http://cygwin.com/ml/#uns

Quotation request ( white bird group ) VERY URGENT

Dear Sir, Kindly quote your best offer for the following UBS Batteries at the earliest. UBS Hawker Batteries 12v model 155F MADE FRENCH - Qty (128) Your early quotation (C&F Riyadh - Saudi Arabia) will be highly appreciated. Thanks & Regards, Eng. Tariq M. Zaki Sales Maneger White Bird Est. Te