Few things to try: is the sql file still there? Did you try forge fetch all issues, maybe you need to re add it to forge, maybe forge is not loaded after opening magit, maybe forge is pointing to another remote which doesn’t have issues.

Whatsapp/messenger are closed source, there is no API to access them other than the official applications or web access.

consult-fd exists in the code, see code.

consult-ripgrep also exists in the code, see code.

When did you last update your package?

What does it mean?

You are doing something wrong and/or your understanding of git/magit is lacking. Pulling from a divergent remote branch is what we all do, every single day and Magit obviously covers this scenario, by default - without rebasing.

What happens after the magit error? are you in a merge situation? is magit waiting for you to resolve conflicts? if you press m are you asked to to complete or abort the merge?

This. Git pull will never rebase unless told to do so.

Wrong. Vscode server is a binary blob, it only requires glibc. It doesn’t need anything else, like shells. It even brings its own git.

Git project, magit and magit-wip mode which creates intermediate commits automatically. In general file editing, emacs file backups are pretty good; learn to work with them.

It’s trivial, using the emacs-plus tap.

I think emacs should adopt vscode remote dev architecture: install a remote server and communicate with it using some rpc protocol. Maybe someone is working on it, I don’t know.

This discussion should happen on the emacs dev mailing list, if you want to involve the core developers.