Search Results

If you need them only at compile time, do this: (eval-when-compile (require 'cl)) If you need them also at runtime (with byte-compiled code) then do this: (load-library "cl-macs") …

Just put the directory where dash.el[c] resides in your load-path value, before you require that library: (add-to-list 'load-path "/YOUR/DIRECTORY/CONTAINING/DASH/") (require 'dash) …

If for some reason you don't want to require sh-script.el when you invoke tika-keymap-showhrk, you can instead add a defvar that defines all of the bindings you want, including the default bindings. … (require 'sh-script) ; <============ (dolist (mjmode mdlist) (let (($map (symbol-value (intern (format "%s-map" mjmode))))) (define-key $map (kbd "H-o a") #'outline-show-all))) ) …

IMHO, the right way is to ignore it. ;-) But the standard Emacs answer is to use declare-function - see (elisp) Declaring Functions. All you need to do is add a declare-function statement before …

Put (require 'THE-LIBRARY) inside your definition of safe-mail-send-and-exit, at the beginning (just after (interactive), where THE-LIBRARY is the library that defines function mail-send-and-exit. … (defun safe-mail-send-and-exit () (interactive) (require 'THE-LIBRARY) ; Replace THE-LIBRARY with the right library name. (if (string-equal (read-from-minibuffer "Are you sure? …

If you don't want to change gneve.el then use load-library or similar, instead of require, to load it. …

Use require if your library depends on another. That's the main question to ask yourself: does your library need the other library? If so, require it. … You can also use a "soft-require" if you want to load another library whenever something is true. …

To load a file, put it in your load-path, then require it in your init file. … For example, this will make all files in directory ~/.elisp (but not in subdirectories) loadable using require: (add-to-list 'load-path "~/.elisp") If the defcustom is autoloaded (it has an autoload cookie …

Not at all the same. with-eval-after-load doesn't load its first argument; require does. Even if the require fails in your scenario, (do-something) is invoked. …

A solution to the byte-compiler not evaluating your (non top-level) require statement is to force its evaluation, using (eval-and-compile (require 'clojure-mode)). … The fact that require is evaluated by the byte-compiler when it is at top level is pointed out in the Elisp manual, node Named Features (which I found by using i require in the manual). …