Skip to content
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

error in process filter: Not enough arguments for format string #48

Open
jo7ueb opened this issue Aug 9, 2022 · 2 comments
Open

error in process filter: Not enough arguments for format string #48

jo7ueb opened this issue Aug 9, 2022 · 2 comments

Comments

@jo7ueb
Copy link

jo7ueb commented Aug 9, 2022

Hi, I tried to use markdown-preview-mode but failed.
I have installed markdown command with $apt install markdown.
So my installation may be correct.

Following is from *Messages* buffer

Markdown-Preview mode enabled in current buffer
Websocket opened
You can run the command ‘markdown-preview-mode’ with M-x ma-p-m RET
Websocket opened
error in process filter: Not enough arguments for format string [2 times]

Thanks.

@ancane
Copy link
Owner

ancane commented Aug 9, 2022

Hey. I haven't been looking into the mode for quite some time. Probably it just got outdated and something broke around dependencies, but given the "WebSocket open" message got printed there is a hope the server is running, but the opening of the browser is somehow broken.
You can try the following:

  • Set markdown-preview-auto-open custom var to nil.
  • Call interactive function markdown-preview-open-browser. This should print the URL into Messages. Then you can try opening it manually. If URL is not there, then issue is more severe and I'll try to finally upgrade the deps. Thanks.

@c0001
Copy link

c0001 commented Dec 7, 2023

This is not only the servelet problem, but also some message usage
internally wrong of this package that all of those message wrapper
doesn't safety check the first argument whether containing format
strings, for example:

In line: 290

:on-error (lambda (websocket type err) (message (format "====> Error: %s" err))) 

;; FIXME: we should fixed as '(message "%s" (format "====> Error: %s" err))'

Hope for fixing, since it's not a feature around case, I've not made a
pull-request first, but if needed thus, I'll give one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants