Comments (7)
Well, I kinda force users to use the bleeding edge of Magit, so that's on me. (I plan to release, but it is complicated.)
When it comes to Emacs master
, I use that too and I only very seldomly have issues with it myself. But yes, if that does not work, then users should try the latest stable release, and if that works stick to it for a while. Or investigate the issue themselves, that would be very useful. Having to investigate alleged issues with the latest Emacs master
, which they cannot reproduce themselves, is not very appealing to package maintainers in general. (Having a short me too is kinda useful though. That does provide a signal, that it's not just one users messed up system. It does not prove that the package, for which the issue is reported, is at fault either. It's a signal, but its a bit vague 😜.)
from magit.
I suppose something must have been wrong with my build even though it worked for at least 6 months.
If you use the development branch, then you should rebuild regularly. Doesn't have to be every week, but six months is way too long. Many package authors support Emacs' master
branch, but assume that users are on a fairly recent build.
from magit.
I don't know what the issue is either and suspect it is not a bug in Magit.
I don't know if you are one of the people in that stackoverflow thread, but if you are not, make sure you perform the same debugging steps as them, in case it fixes the issue for you.
First make sure you exit Emacs. Then make sure all traces of Magit and its dependencies are completely gone. Only then start a new Emacs instance and reinstall Magit.
Try with native compilation disabled.
Since you are having this issue with Emacs 30 (which I use myself), try with a released version too. Again make sure you have left Emacs, before you reinstall everything (in this case really everything, not just Magit and dependencies).
from magit.
The same magit version Magit 20231006.2318 [>= 3.3.0.50-git], Transient 0.4.3, Git 2.42.0
fails under my local emacs 30.0.50 build, but runs fine with emacs 29.1
so yeah, we should investigate what's wrong in our build.
Thanks again @tarsius
from magit.
Hitting this as well, emacs 30.0.50, building magit from tip. Not expecting support seeing as I'm on bleeding edge, but just thought I'd warn others!
from magit.
Agree completely... generally a plus-1 type of message has little value in proving much with regards to an open issue other than what you say.
This morning I completely rebuilt emacs from master
and reloaded all packages and the issue resolved itself. Which probably hints to it being my "messed up system". Hoping the OP can resolve doing the same. Not seeing anything pointing to a problem with magit itself.
from magit.
I also rebuilt emacs from source today and and now everything works! I suppose something must have been wrong with my build even though it worked for at least 6 months. I did not check the AOT compile flag this time which I might have done last time. Anyway, thanks for all the tips and the great project that this is! Really missed it a lot when it didn't work for two weeks. Hated going back to the cli. <3
from magit.
Related Issues (20)
- auto-fill-mode is broken in commit messages when using in git-commit-major-mode HOT 8
- ssh password prompt not matched by regexps HOT 1
- Cannot apply/pop stashes with conflicts HOT 5
- magit-insert-remote-branches: Assertion failed: (equal branch (concat remote "/HEAD")) HOT 2
- Weird void-variable errors regarding magit-section-inhibit-markers HOT 5
- condition-case: Suffix magit-log:--*-order is not defined or autoloaded as a command (interaction with native compilation?))
- How to insert a tab char at the beginning of each file name line like magit 1.x do in status buffer?
- Missing documentation HOT 2
- Reported-by and other git trailers not added below commit message HOT 2
- Forbidden reentrant call of Tramp when creating a signed commit HOT 5
- Commit 1ab107a7 broke M-2 and likely other section-related commands HOT 2
- Symbol’s function definition is void: seq-keep HOT 21
- magit-blame-removal and magit-blame-reverse has some functionality swapped?
- Commit word-wrapping can result in discarded message. HOT 2
- "Applying patches" section repeats already applied patches as "to pick" HOT 4
- How to update? HOT 2
- void-variable alist-get displaying sections HOT 6
- Package-Requires header should be single line HOT 8
- Jump to pushremote-related sections in magit status buffer does not seem to work HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from magit.