Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with require
Search options answers only
not deleted
user 1979
0
votes
Launching emacs with configured packages
Add
(package-initialize)
or for more modern Emacsen you can use
(package-activate-all)
In either case, it needs to come before the require. …
- 26.7k
3
votes
Prevent byte-compiler warnings after requiring features
Here's how I'd do it:
(require 'markdown-mode nil 'noerror)
...
...
...
(if (fboundp 'markdown-mode)
..use markdown-mode..) …
- 26.7k
2
votes
Accepted
How do you remove compiler warnings for macro usage when running macro with 'with-eval-after...
So to fix your code "right", you have two options:
add a (eval-when-compile (require 'flycheck)) which will fix the compilation problem but at the cost of requiring flycheck to be installed and forcing …
- 26.7k
6
votes
Accepted
require vs. package-initialize?
You should be able to use require, yes, but only after running package-initialize (in Emacs≥27, this is done for you before the beginning of the .emacs file). … Note that for 99% of the packages require should not be needed (the autoloads should cause the package to be loaded as soon as you try to make use of it). …
- 26.7k
7
votes
Deep eager macroexpansion
(require <foo>) is treated specially when it's at top-level (it causes the compiler to require the file also, rather than only do the require at run-time). … If the require is not performed at compilation time, then your code can't be compiled properly since the define-clojure-indent macro won't be known during compilation, leading to mis-compilation, indeed …
- 26.7k
3
votes
Accepted
Should I use "require" or "load" when writing my own configuration?
The point of require is not lazy-loading (that would be autoload instead). Instead, the purpose is to avoid loading the same package multiple times. … In the case of config files, which of load or require is preferable is unclear and will depend on your particular use case (but I think in most cases the difference will be negligible). …
- 26.7k