Skip to main content
Bumped by Community user
Bumped by Community user
Bumped by Community user
added 139 characters in body
Source Link
leinad
  • 156
  • 5

I tried updating packages doing list-packages and U only to have emacs freeze half way through. I had to kill emacs. When trying to upgrade again, emacs said all packages are up to date.

However, now when I try to start emacs, I always get the emacs -Q like looking UI with an error prompt: Install missing grammars?

The following tree-sitter grammars are/were missing: janet 

Which I answer y, or even n, but it doesn't matter. Emacs will then startup correctly, but the next time I open it, the same error prompt will show up again.

Any ideas on how to fix this?

Edit: to add a bit of context, I do not use the janet programming language at all.

I'm trying now to see if removing the elpa directory and starting emacs again, which should force it to reinstall everything, will work. If not, I guess some new version of a package is causing issues.

Edit 2: After trying to load emacs, init is breaking because org-roam doesn't seem to work. Now even when I remove the line in my init file that uses it, it still somehow breaks. Using --debug-init it looks like package-install-selected-packages is somehow calling roam to be installed, though I can't see how. I'm wondering if somehow because custom.el contains a roam line, it's getting installed from there. Though I'm not sure what to do about this.

emacs 29.4, macos

Edit 3: I had another error which was failing to install org-roam. I removed that from my init.el file, and yet it was still failing.

I tried updating packages doing list-packages and U only to have emacs freeze half way through. I had to kill emacs. When trying to upgrade again, emacs said all packages are up to date.

However, now when I try to start emacs, I always get the emacs -Q like looking UI with an error prompt: Install missing grammars?

The following tree-sitter grammars are/were missing: janet 

Which I answer y, or even n, but it doesn't matter. Emacs will then startup correctly, but the next time I open it, the same error prompt will show up again.

Any ideas on how to fix this?

Edit: to add a bit of context, I do not use the janet programming language at all.

I'm trying now to see if removing the elpa directory and starting emacs again, which should force it to reinstall everything, will work. If not, I guess some new version of a package is causing issues.

Edit 2: After trying to load emacs, init is breaking because org-roam doesn't seem to work. Now even when I remove the line in my init file that uses it, it still somehow breaks. Using --debug-init it looks like package-install-selected-packages is somehow calling roam to be installed, though I can't see how. I'm wondering if somehow because custom.el contains a roam line, it's getting installed from there. Though I'm not sure what to do about this.

emacs 29.4, macos

I tried updating packages doing list-packages and U only to have emacs freeze half way through. I had to kill emacs. When trying to upgrade again, emacs said all packages are up to date.

However, now when I try to start emacs, I always get the emacs -Q like looking UI with an error prompt: Install missing grammars?

The following tree-sitter grammars are/were missing: janet 

Which I answer y, or even n, but it doesn't matter. Emacs will then startup correctly, but the next time I open it, the same error prompt will show up again.

Any ideas on how to fix this?

Edit: to add a bit of context, I do not use the janet programming language at all.

I'm trying now to see if removing the elpa directory and starting emacs again, which should force it to reinstall everything, will work. If not, I guess some new version of a package is causing issues.

Edit 2: After trying to load emacs, init is breaking because org-roam doesn't seem to work. Now even when I remove the line in my init file that uses it, it still somehow breaks. Using --debug-init it looks like package-install-selected-packages is somehow calling roam to be installed, though I can't see how. I'm wondering if somehow because custom.el contains a roam line, it's getting installed from there. Though I'm not sure what to do about this.

emacs 29.4, macos

Edit 3: I had another error which was failing to install org-roam. I removed that from my init.el file, and yet it was still failing.

added 463 characters in body
Source Link
leinad
  • 156
  • 5

I tried updating packages doing list-packages and U only to have emacs freeze half way through. I had to kill emacs. When trying to upgrade again, emacs said all packages are up to date.

However, now when I try to start emacs, I always get the emacs -Q like looking UI with an error prompt: Install missing grammars?

The following tree-sitter grammars are/were missing: janet 

Which I answer y, or even n, but it doesn't matter. Emacs will then startup correctly, but the next time I open it, the same error prompt will show up again.

Any ideas on how to fix this?

Edit: to add a bit of context, I do not use the janet programming language at all.

I'm trying now to see if removing the elpa directory and starting emacs again, which should force it to reinstall everything, will work. If not, I guess some new version of a package is causing issues.

Edit 2: After trying to load emacs, init is breaking because org-roam doesn't seem to work. Now even when I remove the line in my init file that uses it, it still somehow breaks. Using --debug-init it looks like package-install-selected-packages is somehow calling roam to be installed, though I can't see how. I'm wondering if somehow because custom.el contains a roam line, it's getting installed from there. Though I'm not sure what to do about this.

emacs 29.4, macos

I tried updating packages doing list-packages and U only to have emacs freeze half way through. I had to kill emacs. When trying to upgrade again, emacs said all packages are up to date.

However, now when I try to start emacs, I always get the emacs -Q like looking UI with an error prompt: Install missing grammars?

The following tree-sitter grammars are/were missing: janet 

Which I answer y, or even n, but it doesn't matter. Emacs will then startup correctly, but the next time I open it, the same error prompt will show up again.

Any ideas on how to fix this?

Edit: to add a bit of context, I do not use the janet programming language at all.

I'm trying now to see if removing the elpa directory and starting emacs again, which should force it to reinstall everything, will work. If not, I guess some new version of a package is causing issues.

I tried updating packages doing list-packages and U only to have emacs freeze half way through. I had to kill emacs. When trying to upgrade again, emacs said all packages are up to date.

However, now when I try to start emacs, I always get the emacs -Q like looking UI with an error prompt: Install missing grammars?

The following tree-sitter grammars are/were missing: janet 

Which I answer y, or even n, but it doesn't matter. Emacs will then startup correctly, but the next time I open it, the same error prompt will show up again.

Any ideas on how to fix this?

Edit: to add a bit of context, I do not use the janet programming language at all.

I'm trying now to see if removing the elpa directory and starting emacs again, which should force it to reinstall everything, will work. If not, I guess some new version of a package is causing issues.

Edit 2: After trying to load emacs, init is breaking because org-roam doesn't seem to work. Now even when I remove the line in my init file that uses it, it still somehow breaks. Using --debug-init it looks like package-install-selected-packages is somehow calling roam to be installed, though I can't see how. I'm wondering if somehow because custom.el contains a roam line, it's getting installed from there. Though I'm not sure what to do about this.

emacs 29.4, macos

added 293 characters in body
Source Link
leinad
  • 156
  • 5

I tried updating packages doing list-packages and U only to have emacs freeze half way through. I had to kill emacs. When trying to upgrade again, emacs said all packages are up to date.

However, now when I try to start emacs, I always get the emacs -Q like looking UI with an error prompt: Install missing grammars?

The following tree-sitter grammars are/were missing: janet 

Which I answer y, or even n, but it doesn't matter. Emacs will then startup correctly, but the next time I open it, the same error prompt will show up again.

Any ideas on how to fix this?

Edit: to add a bit of context, I do not use the janet programming language at all.

I'm trying now to see if removing the elpa directory and starting emacs again, which should force it to reinstall everything, will work. If not, I guess some new version of a package is causing issues.

I tried updating packages doing list-packages and U only to have emacs freeze half way through. I had to kill emacs. When trying to upgrade again, emacs said all packages are up to date.

However, now when I try to start emacs, I always get the emacs -Q like looking UI with an error prompt: Install missing grammars?

The following tree-sitter grammars are/were missing: janet 

Which I answer y, or even n, but it doesn't matter. Emacs will then startup correctly, but the next time I open it, the same error prompt will show up again.

Any ideas on how to fix this?

I tried updating packages doing list-packages and U only to have emacs freeze half way through. I had to kill emacs. When trying to upgrade again, emacs said all packages are up to date.

However, now when I try to start emacs, I always get the emacs -Q like looking UI with an error prompt: Install missing grammars?

The following tree-sitter grammars are/were missing: janet 

Which I answer y, or even n, but it doesn't matter. Emacs will then startup correctly, but the next time I open it, the same error prompt will show up again.

Any ideas on how to fix this?

Edit: to add a bit of context, I do not use the janet programming language at all.

I'm trying now to see if removing the elpa directory and starting emacs again, which should force it to reinstall everything, will work. If not, I guess some new version of a package is causing issues.

Source Link
leinad
  • 156
  • 5
Loading