Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/mooerslab/emacs30venturatreesitterconfig

Configuration file for Emacs 30.0.5 with tree-sitter and combobulate for macOS
https://github.com/mooerslab/emacs30venturatreesitterconfig

academic-productivity academic-research academic-writing combobulate concrete-syntax-trees emacs structured-editing time-management tree-sitter

Last synced: 9 days ago
JSON representation

Configuration file for Emacs 30.0.5 with tree-sitter and combobulate for macOS

Awesome Lists containing this project

README

        

![Version](https://img.shields.io/static/v1?label=emacs30venturatreesitterconfig&message=0.3&color=brightcolor)
[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)

# Emacs Configuration with Support for Structured Editing

## Moved to Codeberg
I will try to keep this updated, but
go [here](https://codeberg.org/MooersLab/emacs30init/src/branch/main/README.org) for the most recent version.

## Purpose
This configuration supports structured editing of computer code with concrete syntax trees.
The built-in package tree-sitter and the new package combobulate support this editing.
Emacs has to be compiled with support for tree-sitter.
See [[https://github.com/MooersLab/emacs30macos13treesitter][this repo]] for a protocol for compiling Emacs 30 from source code on macOS and this [[https://github.com/MooersLab/emacs30ubuntu22][one]] for doing likewise with Ubuntu.
These protocols should work with Emacs 29.0.5.

This configuration file is also a rewrite of my basic configuration file with the packages in use listed at the top to speed up the start-up of Emacs.
The *package* package is used to install the missing packages rather than by using the `:ensure t` option in
*use-package*, but *use-package* is still used to customize and load packages when needed.
This massive rearrangement reduced the start-up time by about 30%.
Many thanks go to Jeff Bowman for this suggestion.

However, after two weeks of use, I am having trouble with only some of the elisp files in the *elpa* folder compiled after upgrading packages.
Fixing this issue can take 30 minutes.
I did not have this issue when I used `:ensure t` with use-package.

As of September 2024, my private version of the init.el has grown to include 350 packages.
It takes my current config about a minute and a half to upload.
The operation of Emacs is still smooth despite this ridiculously large number of packages.
I probably do not remember what three-quarters of those packages do!

Note that Emacs without a configuration opens instantly.
You can use the `emacs -Q` command in the terminal to open Emacs without loading its initialization file.
This is very useful when you want to make quick edits to simple files and do not need fancy tooling.

The other way that people contend with the slow loading of the initialization file is to keep Emacs running constantly.
Some people have Emacs sessions that last for months.

Yet, another way to have instant access is to utilize the *emacs-server* via the *emacsclient*.
This is okay if your configuration file is stable.
If you feel compelled to make additions and changes to the configuration file frequently, you can reload the initialization file.
This is not always sufficient to get the changes fully deployed.
Sometimes you have to shut down Emacs and start up again to get some changes fully deployed.
I tend to forget how to shut down and restart the server.
I need to write a protocol and map it to a bash alias or function that displays the protocol in the terminal to have it at my fingertips.

The *init.el* file was developed on Ventura (macOS 13.2), but it should be transferrable to older Mac operating systems.
Several Mac-specific lines in the basic configuration section can be quickly switched for use in Linux or Windows.
Several file paths may need customizing.
Both sites are marked with *;; ==> adjust here* in the init.el file.

The *manual-packages* folder contains the packages not added via accessing MELPA and company.
Their ~*.elc~ files will only work on Ventura with a version of Emacs compiled the same way I compiled mine.
You may have to `byte-recompile` these packages.

## Features

The configuration file's content supports my academic research writing with occasional code writing for research purposes.

- Configured for structured editing with combobulate and tree-sitter.
- Uses the Vertico and friends for completion by default. I love the in-line documentation from Marginalia.
- Fuzzy matching is turned on for use in Ido.
- Can opt for the use of Helm or Icicles.
- Helm's helm-google-suggest command is very cool. Use *google-this* when helm-mode is toggled off.
- Configured for org-mode, org-agenda, org-babel, and org-roam to get organized, track notes, and do literate programming.
- Supports org-pomodoro.
- Supports pdf-tools.
- Uses booksmarks+, dired+, and iscicles (the last is off by default--it is a heavy-duty completion engine for the minibuffer). These require custom installation because they are on the Emacs Wiki and not in a repository.
- Uses evil-nerd-commenter for smart commenting of lines and regions.
- Configured for Clojure, Python, and R programming.
- Supports the use of LaTeX via AUCTeX.
- Supports *google-this*. Make a selection and enter `C-c / g` to submit the selected region as a search term to Google in the default browser.
- Eglot is built into this version of Emacs.

I invoke org-Pomodoro with the point on a Project's headline in an org file to generate the logbook for storing the record of Pomodoros.
I store my lists of manuscripts, grant applications, service activities, etc, in separate org files rather than a single task.org folder because I have too many projects for a single org file.
I bookmarked the headlines for specific projects to accelerate my access to a project via the *Bookmarks List* buffer.

I use the area under a project headline to store the logbook and relevant information.
I may not need the bookmarks if I used org-agenda for scheduling my daily activities, which I do not because it is too hard to stay on top of everything.
I just use org-agenda to schedule upcoming meetings.
The [`org-gtd`](https://www.youtube.com/watch?v=YNqFZ4VBppA&t=846s) package promises smoother management of TODOs.

Note that the bookmarks+ package runs on top of the built-in `bookmarks.e`l package.
Bookmarks+ can bookmark a much more comprehensive array of items.
You can bookmark PDFs for later reading and websites of interest.
I find it much easier to bookmark URLs of heavily visited sites than to store them in my private index.html file.
You can also bookmark project directories and even `dired` buffers.

## What the landing page (dashboard) will resemble when first loaded

The default image for the dashboard is the Emacs logo.
I substituted another image that is included above for testing.
The bottom of the dashboards has the top 10 Hackernews items.
This is an attention trap, so you may comment it out.

The startup time should be shorter on Linux and longer on Windows.

I tried zsh and Bash.
On the Mac, Emacs startup times were the same, although these two shells differ in the startup times of new tabs.
The Emacs binary starts up in a flash without an `init.el`.

Note that bookmarks are usually accessed via the *bookmarks list* buffer, but some can be automatically listed on the dashboard.
For example, clicking on the icon in a book's PDF dashboard opens the book in Emacs for immediate reading.
The bookmarks are a way of keeping track of material that needs to be read soon.
You can configure Emacs to use the *bookmarks* file as the startup page.

With bookmarks+, you add bookmarks to websites with the `C-x x c u` keybinding.
You can also add bookmarks to directories.
You can navigate to the directory of interest in a Dired buffer.
With the directory name selected in the Dired buffer, enter `C-x x m` to add the directory as a bookmark.
Remember to save the *bookmarks list* buffer.

I add bookmarks to my writing projects on Overleaf, the project folder in my local drive, and a PROJ headline in my `journalArticles.org` file where I store my logbook for tracking my Pomodoros on a project.
Thanks to Bookmarks+ and its developer, Drew Adams, I can quickly access any of those three locations with the click of a mouse.

## Funding

- NIH: R01 CA242845, R01 AI088011
- NIH: P30 CA225520 (PI: R. Mannel)
- NIH: P20GM103640 and P30GM145423 (PI: A. West)

|Version | Changes | Date |
|:----------- |:---------------------------------------------------------------------------------------------------------------------|:---------------------|
| Version 0.2 | Added funding and update table. | 2024 May 3 |
| Version 0.3 | Added several paragraphs to the README.md file to clarify several points. | 2024 September 7 |