* Make utf-8 the preferred coding system. I only noticed issues once switching to Windows 10 * Attempted to make whitespace settings for only seeing bad whitespace, but I failed. I'll have to try again another time * Occur no longer has matching string faces in the results, which I thought were making the results hard to read
|3 years ago|
|EmacsOnWindowsSetup.txt||3 years ago|
|ReadMe.org||3 years ago|
|build-systems.el||3 years ago|
|clipboard.el||3 years ago|
|code-formatting.el||3 years ago|
|core-settings.el||3 years ago|
|desktop-management.el||3 years ago|
|dotEmacs.el||3 years ago|
|drill-customizations.el||3 years ago|
|emacsPackages.txt||3 years ago|
|idomenu.el||3 years ago|
|jam-mode.el||3 years ago|
|keybinds.el||3 years ago|
|minimalDotEmacsDrilling.el||3 years ago|
|navigation.el||3 years ago|
|org-customizations.el||3 years ago|
|org-drill.el||3 years ago|
|org-jira-customizations.el||3 years ago|
|org-learn.el||3 years ago|
|packages.el||3 years ago|
|search.el||3 years ago|
|source-control.el||3 years ago|
|syntaxes.el||3 years ago|
|tags-and-autocompletion.el||3 years ago|
|visual-early.el||3 years ago|
|visual-late.el||3 years ago|
- Macoy's Emacs Configs
Macoy's Emacs Configs
dotEmacs.el is meant to become \~/.emacs once installed. Open it for the latest instructions (below may be out of date; it's included here to give you an idea what you'll have to do).
Note that I recommend you cherry pick features you want instead of trying to use the entire config. This is better because you'll know all the features available to you.
Setting this up isn't very convenient yet, unfortunately.
Note that /code/macoy/editor-preferences/src/commit/3b1fe15965045fc6d02a11aac43014dffb38c5bb/Emacs/packages.el will auto-install several packages which this config requires.
Copy the contents of
user-init-dirin your .emacs to the directory of this ReadMe.org. This will load my config files straight from this repository.
mc/cmds-to-run-onceand restart Emacs
magiton Windows, fix credentials for server folder (may not be necessary, only do if you get errors using
magitcredentials (unnecessary if you have SSL support): https://stackoverflow.com/questions/22580873/how-can-i-configure-magit-to-use-my-github-user-name
If you want to use codesearch (fancy ultra fast indexed code searching), install it: https://github.com/google/codesearch …then set
codesearch-cindex-exeto their respective executable locations Search for codesearch in this file to adjust indexing settings
Look over the Customization section for getting everything working properly per-machine.
Emacs shines in its ease of customization. Get used to tweaking settings and building new features. It's one of the pleasures of working with Emacs: making the perfect setup.
This config is meant only as a starting place. You should tear it to pieces and make it your own, or only refer to pieces of it while building up your own config.
If you take the whole config, you'll need to do a decent amount of setup work to get all features working properly. I can attest that it's well worth it once everything has been configured, so stick to it!
"This machine only" config
To facilitate different settings per machine (e.g. your home config and work config differences), there's a simple mechanism:
;; Stuff unique to certain machines (mine here for reference) (when (or (string-equal (user-login-name) "macoy") (string-equal (user-login-name) "mmadson")) (load-file "~/.emacs-this-machine-only.el"))
string-equal comparisons to your machine(s) name(s). Multiple are there in case you have a home/work machine.
~/.emacs-this-machine-only.el file and put your per-machine settings in it.
Look at /code/macoy/editor-preferences/src/commit/3b1fe15965045fc6d02a11aac43014dffb38c5bb/Emacs/build-systems.el
build-universal-jam for an example build system:
(defun build-universal-jam-clean () "Build using jam (select directory first)" (interactive) (message "Jam clean") (let ((default-directory (read-directory-name "Directory: "))) (compile "jam clean"))) ;; ;; Build system manager - select from multiple different compilation commands ;; ;; Note that names need to be unique (they should be anyways) (setq macoy-build-system-list (list '("Jam (current directory)" build-universal-jam) '("Jam Clean (current directory)" build-universal-jam-clean)))
macoy-build-system-list with your own custom build systems.
F7 to build.
S-F7 allows you to decide what happens when you hit
F7 (it will build right after selection as well).
C-p (projectile), you may want to filter out some files/directories:
(setq projectile-globally-ignored-files (append '("*_ast.*") ;; This syntax might not be right projectile-globally-ignored-files)) (setq projectile-globally-ignored-directories (append '("AutoGen" "3rdparty" ".build" ".cquery_cached_index") projectile-globally-ignored-files))
(You'll need to run
projectile-invalidate-cache to see the changes after evaluating).
Many keybinds are set in /code/macoy/editor-preferences/src/commit/3b1fe15965045fc6d02a11aac43014dffb38c5bb/Emacs/keybinds.el. It's not exhaustive (things are set in other files too), but it's worth looking at.
Set up your org stuff (multiple provided for reference):
;; My org files (setq macoy-org-dir nil) (when (string-equal (user-login-name) "macoy") (setq macoy-org-dir "~/Dropbox/Org/") (setq org-agenda-files (list (concat macoy-org-dir "1_Calendar.org") (concat macoy-org-dir "0_Dump.org")))) (when (string-equal (user-login-name) "mmadson") (setq macoy-org-dir "C:/Users/mmadson/Dropbox/Org/") (setq org-agenda-files (list (concat macoy-org-dir "1_Calendar.org") (concat macoy-org-dir "0_Dump.org"))))
macoy-org-dir makes quick org opening possible via
If you want to use
org-jira, set your company's JIRA url:
(setq jiralib-url "http://jira:8080")
The search functionality (e.g. provided by
C-S-f) is extensive and a bit complicated. I made it to handle searching rather large collections of text quickly (we're talking tens of gigabytes, full text search).
You should open /code/macoy/editor-preferences/src/commit/3b1fe15965045fc6d02a11aac43014dffb38c5bb/Emacs/search.el and read through it. Many directories, regex filters, and index locations should be customized to fit your project.
The tool you should use most often is
codesearch, which is a very fast index-based search tool.
ag serves as the general purpose, non-index-based but better than grep search tool.
C-e serves as a quick menu to searching using any of the techniques I've added. You should add your own techniques if you e.g. have multiple separate
In general, you should use
vc- prefixed commands or
magit for handling source control, but I've provided some TortoiseSVN commands in /code/macoy/editor-preferences/src/commit/3b1fe15965045fc6d02a11aac43014dffb38c5bb/Emacs/source-control.el. You'll need to tweak them for your repository (assuming you want to).
Tags and Autocompletion
Like searching, tag navigation (e.g. Go To Definition-like functionality) and autocompletion is extensive and complicated.
You should open /code/macoy/editor-preferences/src/commit/3b1fe15965045fc6d02a11aac43014dffb38c5bb/Emacs/tags-and-autocompletion.el and read through it, making sure your executable paths and project paths are set.
TODO: I need to make this more convenient for multiple projects…