linerif.blogg.se - Magit for aquamacs

MAGIT FOR AQUAMACS HOW TO
MAGIT FOR AQUAMACS UPDATE
MAGIT FOR AQUAMACS CODE
MAGIT FOR AQUAMACS SERIES

MAGIT FOR AQUAMACS HOW TO

The files in that folder will give you additional hints on how to customize the libraries. With very few exceptions, all these packages are anything but well-documented, but perhaps you’ll find some bits useful.

MAGIT FOR AQUAMACS SERIES

#Magit for aquamacs seriesĪ long delayed project of mine is to use this blog to go through all of them in a series of posts that we could call TEOS, The Emacs Operating System. They would be not only about how the individual libraries work together, but, most importantly, about how they integrate with each other and with other stock Emacs packages to provide an operating environment that, in my humble opinion, surpasses any other commonly used operating system in terms of productivity and extensibility. An Elisp Machine where you are in control and have all the fun. Interviews with people so that they can share their tips (incl.(command (nth (random (length commands)) commands))) (let* ((commands (loop for s being the symbols (with-output-to-temp-buffer "*Tip of the day*" If i finally go for it, you may consider this post as the first in the series, but i haven’t made up my mind yet.īe it as it may, i hope you’ll find some elisp snippets above worth stealing for your own Emacs Operation System.Īlthough i don’t use it that much, i’ve had the following defun in my emacs config since i remember: I’ve been playing with the idea of joining PragProWriMo and make this part of a book writing project that would explore in detail TEOS, with intermediate Emacs users in mind.Here’s what I’m looking forward to devoting some of my time to:

MAGIT FOR AQUAMACS CODE

Imagining nonawesomeness: Weak async marginal/niche people moving away to other editors because of growing gaps performance issues unmaintained code developer burnoutĮmacsConf: mailing list for next year, venue? Imagining awesomeness in 5 years: Responsive editor that’s easy to set up SEO so that people can find useful resources context/goal-specific documentation regular virtual show&tell

packages: popularity, reverse dependency graph, URL log for #emacs, 24 packages for Christmas and other blog series, IUseThis, reminders to be lazier / stories for inspiration.

Vim users: configurability envy, migration/emulationĮmacs performance: elp, memory-use-counts, garbage collection, algorithms, cookbook, core work.

IDE users: integration with other parts of life.

Users of defunct editors: migrated features, migration guides.

Pre-built Org starter kits? screencasts, interactive tutorials, games as introductions

Non-developers (writers, scientists, mathematicians, etc.): Context-specific functionality, starter kits, easy installs, articles, screencasts – learn from Aquamacs, Ready Lisp.

Keyboard enthusiasts: keyboard shortcuts, customizability.

MAGIT FOR AQUAMACS UPDATE

Emacs intermediate: tweaking Emacs, getting into Emacs Lisp, contributing upstream need to update Writing GNU Emacs Extensions.

Emacs beginners: getting more into Emacs, learning more about packages, customizing Emacs learning path through packages, maybe with time estimates?.

Performance (especially of code analysis and navigation tools).

IUseThis for Emacs, maybe with annotations.

#emacs word cloud or URL frequency/analysis.

Emacs structures: windows, buffers, text properties, etc.

haskel, rails, java, and other languages….

Here’s what we talked about:Ī rough outline of things to flesh out into articles/chapters: John Wiegley and I had lots of fun brainstorming ways to help move Emacs forward, particularly as I’m carving out more of my time to focus on Emacs.