Windows 10
Emacs 27.1
From C-x C-f File
Till seeing the file actually open can take almost a minute!
Tried emacs instead of runemacs.
Also Menu-file-visit
All the same
I think there's some Mcafee stuff running
(sorry don't know too much... Office machine!
Just assume standard "corporate setup"??
In any case could'nt get task manager to show some rogue 100% process. But I'm terrible at using windows effectively and am open to being educated 😅)
And maybe this question will find better answers on superuser?? Can move it if that's so...
Is there a more emacs-centric (rather than task-manager — windows centric) way of finding out what emacs is up-to in that long 1 minute?
emacs -q
to avoid your init file and see if the problem lies there. – NickD Sep 27 '20 at 12:51emacs -Q
(orrunemacs -Q
) - no init file. If you no longer see the problem then bisect your init file to find the culprit. (Always suspect your init file first.) Also, please state whether you saw the same problem with an earlier Emacs release, or any other info you think might be relevant. – Drew Sep 27 '20 at 20:46