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

:defer nil and :demand t #738

Closed
raghnysh opened this issue Dec 16, 2018 · 3 comments
Closed

:defer nil and :demand t #738

raghnysh opened this issue Dec 16, 2018 · 3 comments

Comments

@raghnysh
Copy link

I may be mistaken, but :defer nil and :demand t seem to have the same effect. Is that correct? I didn't see anything in the documentation that mentions it.

@Silex
Copy link
Contributor

Silex commented Dec 16, 2018

If you aren't using :commands, :bind, :bind*, :bind-keymap, :bind-keymap*, :mode, :interpreter, or :hook (all of which imply :defer

So if you don't use any of these keywords, then yes :defer nil is the same as :demand t. But see it more as :defer is a way to control defering and :demand a way of bypassing :defer.

@raghnysh
Copy link
Author

So :defer nil doesn't override :commands foo, etc., whereas :demand t does. Thanks for the explanation.

@Silex
Copy link
Contributor

Silex commented Dec 16, 2018

@nyraghu: not sure what happens if you have :commands AND :defer nil. To me it does not make a lot of sense, I guess that yeah it might behave the same as :demand t but I would not count on it.

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

No branches or pull requests

2 participants