doomemacs / doomemacs/modules

Editing C source files has been slower since `3fe5ff6`

Open
#65 29 comments 0 reactions 0 assignees View on GitHub
:ui vc-gutter
Dominant language
Emacs Lisp
Stars
61
Forks
37
Avg merge
11h 19m
Merged PRs (30d)
7

Description

### Describe your issue

After 21166d118449ea3ca07334748453bf8151704b25, it became much slower to add or edit declarations of array variables with initializers in C.

```
commit 21166d118449ea3ca07334748453bf8151704b25
Author: Henrik Lissner
Date: Tue Jun 23 19:09:38 2026 -0400

bump: sources/doom+

doomemacs/modules@5a44cf7bdb74 -> doomemacs/modules@4fcb2b1a5063
```

### Steps to reproduce

1. In the `~/.config/emacs` directory, run `git checkout 21166d1` and reinstall Doom Emacs.
2. Open Doom Emacs and try writing the following C code by hand. The input lag should be noticeable.

```c
int main(void)
{
int a = 10;

int b[] = {1, 2, 3};

int c[] = {4, 5, 6, 7};

int d[] = {8, 9, 10, 11, 12};

double e[] = {1.2, 3.4, 5.6};

return 0;
}
```

3. In the previous directory, run `git checkout HEAD~1` and reinstall Doom Emacs.
4. Try writing the C code above again. Typing would be much faster than before.

### System information

[doom-info.txt](https://github.com/user-attachments/files/31302095/doom-info.txt)

### Disclosures

- [ ] This issue was written with/by AI.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start in ~/.config/emacs by comparing the Doom Emacs state at 21166d1 with its previous revision, then reproduce the C declaration example while measuring typing latency. Trace the changed module or configuration responsible for the slowdown. Done means editing the shown C code is responsive again after reinstalling Doom Emacs, without regressing the prior behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, emacs, emacs-lisp
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.