On Tue, Mar 29, 2011 at 18:24, Ken Brown wrote:
> On 3/29/2011 9:26 AM, Ken Brown wrote:
>>
>> On 3/29/2011 8:48 AM, J. David Boyd wrote:
>>>
>>> I'm not certain of the exact version of these, but they are the latest,
>>> as I upgrade at least once a week.
>>>
>>> Lately, everytime I do almost any
On Mon, Mar 29, 2010 at 15:13, Ken Brown wrote:
> On 3/29/2010 6:33 AM, Dan Tsafrir wrote:
>>
>> Hi,
>>
>> After I've upgraded to cygwin-1.7 my emacs takes 30-40 seconds to
>> open. Following
>> http://x.cygwin.com/docs/faq/cygwin-x-faq.html#poor-p
> I confirm that gv is practically unusable since I updated to x.org
> 7.4. It is very very slow. For the example you give, it takes only 2
> seconds to load (same version 3.6.5, Windows XP, Dual Core2 Duo 2.6
> GHz) but on the large ps files I use it takes ages to show compared to
> before I upgra
Hi,
It used to be the case that opening a postscript file with gv on
cygwin was more or less immediate. I've recently updated cygwin and
now it takes about 2-5 seconds (a clock is displayed while gv is
"thinking"). This happens even if the postscript file contains only a
few words. For example, if
Hi,
When given certain long options, Cygwin's getopt_long() function
erroneously fails on "ambiguous option". The short program below
illustrates the problem: getopt_long() wrongfully reports the "--xy"
option as ambiguous.
Strangely, if flipping the order of the 2nd and 3rd entries in the
option
On 1/18/07, Dan Tsafrir <[EMAIL PROTECTED]> wrote:
Hi,
When I open a postscript document (any document) with 'gv', the text
in the document appears doubled in height and halved in width, making
the document virtually unreadable.
Well apparently there was something messed up i
6 matches
Mail list logo
