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

Blank Browser, Unresponsive #31

Closed
lynndylanhurley opened this issue May 20, 2013 · 15 comments
Closed

Blank Browser, Unresponsive #31

lynndylanhurley opened this issue May 20, 2013 · 15 comments

Comments

@lynndylanhurley
Copy link

When I open a markdown file, a blank browser tab opens.

The blank browser tab does not respond to updates to the markdown text. There are no console errors and no failed requests.

When I run echo Hello | instant-markdown-d from the console, a blank page opens.

My $PATH seems to be ok (pygments.rb, redcarpet, and instant-markdown-d are all available from within vim).

Any help is much appreciated.

@lynndylanhurley
Copy link
Author

What is the best way to debug the node server? Is there a log file or something that I can tail?

@emilford
Copy link

emilford commented Jun 7, 2013

I'm also seeing the blank browser tab. Any suggestions helpful. Thanks.

@allenfantasy
Copy link

+1 for this issue. Getting nowhere.

UPDATE: I got them now:

@eclifford
Copy link

I wanted to add that I was getting this problem on some markdown files. It turns out that it doesn't recognize shell as a code block type.

I changed all my instances of shell to bash

For example.

@jojoyuji
Copy link

+1 same here.

@kevin4fly
Copy link

environment:

kevin@kevin:/data/dotvim$ node --version
10.10.28
kevin@kevin:
/data/dotvim$ npm --version
1.4.9

with that latest prerequsites.

  1. open a markdown file as: vim README.rd then chrome pops up and the content display correctly.
  2. close chrome and quit vim.
  3. run vim README.rd again. blank webpage shows up unexpectedly.
  4. run kevin@kevin:~$ echo '---' | instant-markdown-d from terminal, get these:

info - socket.io started
warn - error raised: Error: listen EADDRINUSE`

it seems like the listening address is in use, thus do anything cause no reponse.
hope these could help you to troubleshoot the problem. free to let me know if you need more info.

@kuno
Copy link

kuno commented May 13, 2014

+1

I am using both nvm for installation of node, and rbenv for ruby and gems

@kevin4fly
Copy link

remove set shell=bash\ -i from my .vimrc file and re-install all prerequisites. it works now.

@lorenzogrv
Copy link

I've successfully resolved this issue by following this README instruction:

(...) if you're using RVM, use gem install and NOT sudo gem install (...)

Reinstalling depencendies that way fixed the problem.

@igalic
Copy link

igalic commented May 30, 2014

Could it be that this won't work with ruby 2.1?

@kevin4fly
Copy link

i don't think so 'cause i am using ruby 2.1.1 and it just works fine for me.

@danxshap
Copy link

@kevin4fly thanks for the tip about removing set shell=bash\ -i, seems to have worked for me. Do you know what other unintended consequences that change may have?

@kevin4fly
Copy link

@danxshap negative. everything just works fine for me so far. :)

@kevin4fly
Copy link

hi all, if vim-instant-markdown doesn't work, please try to install curl to see if it can be fixed since the curl appears in vim-instant-markdown/after/ftplugin/markdown/instant-markdown.vim. please refer to #42 for details.

@stale
Copy link

stale bot commented Jan 9, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Would not fix label Jan 9, 2021
@stale stale bot closed this as completed Jan 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants