-
Notifications
You must be signed in to change notification settings - Fork 260
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
use-package-with-elapsed-timer: respect option at runtime #96
Conversation
Previously the option `use-package-verbose' was consulted at macro expansion time, and as a result customizing the option did nothing, without also recompiling `use-package.el'.
What does |
use-package-with-elapsed-timer: respect option at runtime
|
Ah, ok so it's not something you use directly. I've been using it without knowing it because of |
Why add use-package-with-elapsed-timer to font locking ? It's an internal macro isn't it ? |
It probably was intended as that initially, but it is actually quite useful in places where you would also use |
@jwiegley: shouldn't that be I'm wondering if I accidentally changed it from the original intention in 0b088fb, though as far as I can tell, it was always this way.
Yup. |
No, it always reports really long load times. |
hmm (let ((use-package-verbose nil))
(pp-macroexpand-expression
'(use-package-with-elapsed-timer "text"
(do-stuff))))
(progn
(do-stuff)) That's before this patch, now the |
I don't understand. So what has changed exactly? |
I don't think the behaviour has changed, but it doesn't appear to match your description. |
use-package-with-elapsed-timer: respect option at runtime GitHub-reference: jwiegley/use-package#96
use-package-with-elapsed-timer: respect option at runtime GitHub-reference: jwiegley/use-package#96
Previously the option
use-package-verbose
was consulted at macroexpansion time, and as a result customizing the option did nothing,
without also recompiling
use-package.el
.The other two commits are cosmetics.