Re: Slow usage of capture templates

[Tim Cross <theophilusx@gmail.com>]

Probably no real help, but win10 is (or soon will be) bundling in bash
shell, which may address many of the reasons to use Cygwin. From posts
I've seen on a number of lists, I would not be surprised to see cygwin
slowly decline into obscurity. I see little interest in the emacs devel
list for cygwin since the native windows version has matured (and it has
been suggested, is the largest emacs user base).

Having bash, a native emacs and even a 'better' system shell in
powershell (better than bat scripts and VB that is), at some point, you
will likely have to switch and I can say, it is much less distasteful
than it was (I've been using Linux since 1993 and Emacs since 97 and am
also forced to run windows at work).

Alternatively, do what I actually do - run vmware and Linux as a
virtual - technically, I'm running the work SOE and within policy! When
I absolutely have to do things in windows, I use native Emacs and a
small amount of powershell, but plan to use the bash shell once I find
time to sort it all out. 

Tim

Johan Ekh writes:

> Thanks Adam
>
> I've tried the native windows version and it does not have this problem.
> But I'm an old school Linux user that is forced to use windows at work.
> I've managed to set up Cygwin and it works quite well, in fact I think
> Emacs is working very well except for the issue in this post. Not slow.
> Thanks anyway. / Johan
>
> On Wed, Aug 2, 2017 at 12:55 PM, Adam Porter <adam@alphapapa.net> wrote:
>
>> This isn't much help, but the best suggestion I have is to try the
>> non-Cygwin, native Windows build.  I use the Cygwin build myself, but it
>> is inherently slow compared to Linux builds for some reason.  It takes
>> probably 10-20 times as long to startup, and everything I do it in it is
>> slow compared to in Linux.  Maybe the native Windows build will perform
>> better.
>>
>>
>>


-- 
Tim Cross