-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Magit fails to start with 'Selecting delete buffer' #535
Comments
The issue also happens on FreeBSD with following conditions.
|
I bisected the emacs-29 branch, the first bad commit is this:
The "selecting deleted buffer" error does not actually happen on that commit, magit is able to show the status buffer, but the failure to initialize the forge DB (which seems to be the root cause) does. |
Bug report on the emacs side: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=60872 |
This fixes an issue that was merely triggered by a change in Emacs [1]. [2: 127bb98] started binding `coding-system-for-write' and `coding-system-for-read' to `utf-8-auto'. As Eli points out at [3] `utf-8-auto' was probably a mistake and `utf-8' should have been used instead. 1: emacsmirror/emacs@cfd2b3504ab5de6eb5 2: 2014-02-02 127bb98 Set coding system to utf-8-auto for sqlite. 3: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=60872#11. > Setting coding-system-for-write to utf-8-auto makes no sense; > that coding-system's _only_ raison d'être is for using in > coding-system-for-read, i.e. when decoding stuff that may or > may not start with a BOM. Since EmacSQL is not a general-purpose database but instead stores data encoded by Emacs for later retrieval by Emacs only, we do not have to with the unlikely appearance of a BOM, so we can use `utf-8' instead of `utf-8-auto' for writes *and* reads. Re #104, #106, magit/forge#533, magit/forge#535, bug#60872.
@tarsius Hi Jonas, I can confirm that forge/emacsql works again after that change. Thanks a lot! |
Thanks for confirming that. I've also just added a commit to prevent the secondary error |
Hi, I keep running into this issue. I'm on Emacs 29 using emacs-pus homebrew on MacOS ( Any help would be greatly appreciated! I'd love to be able to use forge again. I've had it disabled for a few months now and just had some free time to mess with it, but the last few hours have been futile. |
Do you get a backtrace if you enable debugging? |
It does not throw a backtrace with debugging enabled.... and is |
It is a function defined in All libraries are now included in just one package |
Ahhh thanks! I use
I deleted the |
So |
It's kinda weird because when I run |
When you say you deleted the |
I ran |
Wow it worked like a charm! Thanks so much for your help! |
Conditions
Steps to reproduce the issue
git clone https://github.com/magit/forge.git
.emacs -q --no-site-file
.(require 'magit)
and evaluate it withC-j
.(require 'forge)
and evaluate it withC-j
.M-x magit
and select the repositoy cloned at step 1.Expected behavior
Magit successfuly starts and buffer named
magit: forge
is created.What really happens
Magit fails to start with
Selection deleted buffer
.Backtrace
Other things I know about this issue
The text was updated successfully, but these errors were encountered: