Daniel Nicolai

I never had the problem that pdf-tools did not start, but I have run into the 'can not encode buffer pop-up' problem also. I have posted a solution already [here](https://emacs.stackexchange.com/a/69158/26163)....

I only get this issue with a PDF that I created using the newest version of latex. Anyway, unfortunately the problem is not yet completely fixed because I now get...

@DrWaleedAYousef Thanks for the feedback, but could you respond to @smile13241324 [his questions](https://github.com/syl20bnr/spacemacs/issues/15106#issuecomment-982060229). Also, did you try if deactivating `git-gutter-mode` (manually) solves the 'encoding popup' problem? Otherwise, maybe you could...

The issue of pdf-view starting in `emacs-state` seems to get triggered by the first form, i.e. `(pdf-tools-install)`, in the `:config` section of `pdf/init-pdf-tools`, but this happens only when the version...

I have created a fix upstream for `pdf-view` starting in `normal-state`. The issue about the coding system message is due to `git-gutter-mode` getting activated somehow. I am not sure if...

Funny that it shows every `push --force` here...

As you find in the links above, both upstream fixes have been merged so that the issues mentioned here should have been solved (and the issue can be closed).

@jsilve24 Does your python command work on the command line? In that case, maybe you can just move/delete the `.spacemacs.env` file in your `.emacs.d` dir and restart Spacemacs. I.e for...

Ah, the .spacemacs.env is probably in your home folder then (I got a bit confused because I use a .spacemacs.d configuratoin directory which holds my .spacemacs.env file). Anyway, you can...

Okay, your python is probably working alright already. So it turns out that when using most send-to-repl functions the ouput does not get printed automatically (like it would when you...