     man
     magit
     magit-todos
-    ,@(if (bound-and-true-p evil-collection-setup-minibuffer) '(minibuffer))
+    ,@(when evil-collection-setup-minibuffer '(minibuffer))
     mu4e
     mu4e-conversation
     neotree
     notmuch
     nov
     ;; occur is in replace.el which was built-in before Emacs 26.
-    (occur ,(if EMACS26+ 'replace "replace"))
+    (occur ,(if (<= emacs-major-version 25) "replace" 'replace))
+    omnisharp
     outline
     p4
     (package-menu package)


;; We load evil-collection ourselves for these reasons:
;;
;; 1. To truly lazy load it. Some of its modules, like the elisp-mode and
;;    buff-menu ones are loaded immediately, because Emacs loads them
;;    immediately, pulling in all of evil-collection and sometimes other
;;    packages.
;; 2. This ensures a predictable load order, versus lazy loading using :defer or
;;    :after-call. This means users can use (after! org ...) and be sure that
;;    their changes will override evil-collection's.

    (pdf pdf-view)
    popup
    proced
    process-menu
    prodigy
    profiler
    python
