<div dir="ltr">Have you tried specifying an absolute path for the git executable that magit uses, to avoid the overhead of traversing the environment for each call? (M-x customize-var RET magit-git-executable RET) <br><br><div class="gmail_quote"><div dir="ltr">On Tue, Jun 28, 2016 at 2:51 PM Simon Peyton Jones via ghc-devs <<a href="mailto:ghc-devs@haskell.org">ghc-devs@haskell.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">David, Tamar<br>
<br>
I have another issue. I'm using 'magit' (in emacs) to drive git. But it gives half-minute delays to do anything at all. There are lots of people complaining about it (googlable) but no solutions I can see. Do I have to give up magit?<br>
<br>
It used to be fine in earlier versions.<br>
<br>
Just at the moment it's Much Much More Serious. Even opening a file in emacs (nothing to do with git or (ostensibly) magit, takes nearly a minute!! In the process manager I can see lots of git activity -- just when I open a file in ordinary emacs!<br>
<br>
I have utterly no idea why this might be. I'm adding John Wiegley, my Emacs Friend<br>
<br>
Thanks<br>
<br>
Simon<br>
<br>
| -----Original Message-----<br>
| From: David Macek [mailto:<a href="mailto:david.macek.0@gmail.com" target="_blank">david.macek.0@gmail.com</a>]<br>
| Sent: 28 June 2016 13:20<br>
| To: Simon Peyton Jones <<a href="mailto:simonpj@microsoft.com" target="_blank">simonpj@microsoft.com</a>>; <a href="mailto:tamar@zhox.com" target="_blank">tamar@zhox.com</a><br>
| Cc: <a href="mailto:ghc-devs@haskell.org" target="_blank">ghc-devs@haskell.org</a><br>
| Subject: Re: msys2 64 bit: help help!<br>
|<br>
| On 27. 6. 2016 23:33, Simon Peyton Jones via ghc-devs wrote:<br>
| > 1. I just left the machine for 10-15 mins and lo! the shell windows<br>
| opened up. It just took a loooong time.<br>
|<br>
| I could be something with Active Directory. Cygwin (upon which is<br>
| MSYS2 based) integrates with AD, but there are numerous (google-able)<br>
| reports of huge slowdowns related to this.<br>
|<br>
| > At this point, starting a new shell no longer took a long time. It<br>
| all seemed to be working.<br>
|<br>
| Also don't forget to exclude `C:\msys64` from any anti-virus scans.<br>
|<br>
|<br>
| > 2. I then ran pacman -Syuu as instructed on the installation page:<br>
| <a href="https://sourceforge.net/p/msys2/wiki/MSYS2%20installation/" rel="noreferrer" target="_blank">https://sourceforge.net/p/msys2/wiki/MSYS2%20installation/</a><br>
|<br>
| I'm afraid you misread the instructions. You should run `update-core`<br>
| first to upgrade to the newer pacman that handles `pacman -Syuu`<br>
| correctly. (New installer packages with an up-to-date pacman are<br>
| planned.)<br>
|<br>
| > The log of what happened is below. There are numerous failures<br>
| involving Cygwin, which I do not have installed, at least not so far<br>
| as I know. I do not know if these failures matter.<br>
|<br>
| They might. See below.<br>
|<br>
| > 3. After this step, starting a shell failed altogether with<br>
| "c:/msys64/mingw64_shell.bat is not recognised as an internal or<br>
| external command". And sure enough, there is no such file. Presumably<br>
| it existed in step 1. So perhaps step 2 deleted it?<br>
|<br>
| If the post-install script for `filesystem` were able to run, it would<br>
| inform you that `*_shell.bat` are deprecated and were removed. I see<br>
| you have `msys2-launcher-git` installed -- you can then use<br>
| `C:\msys64\mingw64.exe` (and even pin it to the taskbar).<br>
|<br>
| > 4. As you mention, I then tried msys2_shell.cmd. It worked -- with<br>
| a noticeable delay of 5 seconds or so.<br>
|<br>
| May still be AD-related.<br>
|<br>
| > * should I worry about all those install errs<br>
|<br>
| I recommend staying on the safe side and nuke the installation.<br>
| Alternatively, reinstall the packages that had failures (`pacman -S<br>
| gcc-libs gettext gmp ...`).<br>
|<br>
| > * how can I debug what's happening with<br>
| > that long delay<br>
|<br>
| `/etc/nsswitch.conf` allows for some configuration. See<br>
| <<a href="https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nsswitch-" rel="noreferrer" target="_blank">https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nsswitch-</a><br>
| pwdgrp>.<br>
|<br>
| > * Should I nuke the start menu shortcuts that<br>
| > the msys64 installer so carefully installed<br>
| > in favour of msys2_shell.cmd?<br>
|<br>
| Yes or see above. Note that you might need `msys2_shell.cmd -mingw64`<br>
| instead (not sure if it matters for GHC).<br>
|<br>
| --<br>
| David Macek<br>
<br>
_______________________________________________<br>
ghc-devs mailing list<br>
<a href="mailto:ghc-devs@haskell.org" target="_blank">ghc-devs@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br>
</blockquote></div></div>