Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Profiling init configs built with straight.el #332

Closed
matthew-piziak opened this issue Dec 2, 2018 · 4 comments
Closed

Profiling init configs built with straight.el #332

matthew-piziak opened this issue Dec 2, 2018 · 4 comments

Comments

@matthew-piziak
Copy link

straight.el appears to be incompatible with ESUP, the Emacs Start-Up Profiler. What is the right way to profile dotemacsen that are fixtured with straight.el?

@raxod502
Copy link
Member

raxod502 commented Dec 2, 2018

Works for me, with the following code in init.el and running M-x esup after initial installation from an otherwise empty ~/.emacs.d:

(defvar bootstrap-version)
(let ((bootstrap-file
       (expand-file-name "straight/repos/straight.el/bootstrap.el" user-emacs-directory))
      (bootstrap-version 5))
  (unless (file-exists-p bootstrap-file)
    (with-current-buffer
        (url-retrieve-synchronously
         "https://raw.githubusercontent.com/raxod502/straight.el/develop/install.el"
         'silent 'inhibit-cookies)
      (goto-char (point-max))
      (eval-print-last-sexp)))
  (load bootstrap-file nil 'nomessage))

(straight-use-package 'esup)

This is running command-line Emacs 26.1 from Homebrew --with-cocoa --with-modules on OS X 10.11.6.

Could you provide some steps to reproduce the problem? FWIW, my own Emacs configuration uses ESUP.

@wedens
Copy link

wedens commented Dec 3, 2018

Works for me in emacs 27.0.50 on GNU/Linux.

I had this problem before and I think (but I'm not sure it is the reason) it disappeared after upgrading emacs from 26.1 to 27.0.50.

@jkp
Copy link

jkp commented Apr 10, 2019

I had the same issue here - I tried updating emacs as stated above but it didn't help. In the end I noticed a that some error messages referenced my ~/.recentf file so I disabled that module and deleted the file and esup started working. YMMV.

@raxod502
Copy link
Member

This thread is being closed automatically by Tidier because it is labeled with "waiting on response" and has not seen any activity for 90 days. But don't worry—if you have any information that might advance the discussion, leave a comment and the thread may be reopened :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants