Fork me on GitHub
#emacs
<
2017-10-18
>
andrea.crotti12:10:12

today I upgraded a few packages ( > 30 since it was a while) from melpa and Emacs started acting funny

andrea.crotti12:10:50

it just gets stuck when doing some random things like: - dired on a directory - opening an XML file - visiting the Messages buffer

andrea.crotti12:10:31

I tried to bisect the configuration but so far could not detect what's the actual problem, and reproducing it it's very time consuming since it gets stuck for a while

andrea.crotti12:10:01

any idea how to find out what's going on exactly? Is there a way which functions have been taking most of the time in Emacs?

andrea.crotti15:10:52

mm I tried that but it seems to do nothiing

andrea.crotti15:10:05

the profiler-stop doesn't give me any report or creates any buffer with the results

dpsutton15:10:28

yeah it has a very counter-intuitive interface. calling profiler-stop does not print the report, it turns off the profiler. you have to call the report while the profiler is running

dpsutton15:10:18

profiler-start and then later profiler-report before profiler-stop @andrea.crotti

andrea.crotti16:10:06

hehe wtf ok 😄

andrea.crotti16:10:04

something to do with Helm

dpsutton16:10:41

projectile-current-project-files seems like projectile to me. it's probably building the cache of project files

andrea.crotti16:10:45

yeah well but until I don't kill the file that makes it go bonkers

andrea.crotti16:10:54

it's entirely unusable

andrea.crotti16:10:14

but both projectile and helm-projectile didn't really change

andrea.crotti16:10:19

since last week

andrea.crotti16:10:48

looks like it's projectile though

andrea.crotti16:10:04

if I disable that it all works

gonewest81817:10:43

out of curiosity, are you installing from melpa or melpa-stable?