gfm: headers with no space after hash about grip

[joeyespo]

This is working.

Try using the latest version of grip, deleting any styles downloaded from GitHub (currently grip/instance/style-cache), and clearing your browser cache.

GitHub

localhost

[faxm0dem]

okay, sorry about the noise. Would you be so kind to provide instructions to install grip from a source tree?

[joeyespo]

Not a problem, @faxm0dem. Certainly!

First some questions. What version of Python do you have installed (python -V)? Do you have pip (pip -V)? If not, do you have setuptools?

With pip, upgrading should be as easy as

$ pip install --upgrade grip

But you said you can't currently do that. Perhaps you should get that fixed? It's the underlying problem, and I'm sure you'll have issues with other Python libraries if you don't. Try uninstalling Python completely, then re-installing it. If you install Python 3.4, it should come bundled with pip. (If you want Python 2.7, follow these instructions to get pip.) If you do this, you should be able to run pip install grip normally.

Anyway. If you can't do any of that for whatever reason, you can still download grip separately. Either by grabbing the latest release and unzipping it, or by cloning the repository with git clone http://github.com/joeyespo/grip.git.

From there, open a terminal in the new grip directory and enter the following:

$ python setup.py install

Note that using setup.py directly, as opposed to using pip, you'll have to manually upgrade and uninstall the package later by deleting files in Python's site-packages directory.

Does that help?

[faxm0dem]

Thanks a lot for taking this much time to answer a pynoob. This helped a lot.
That being said, I really must be something wrong, as the two issues still don't seem to be solved ( #62 and #63). I removed my ~/.local directory and reinstalled grip using pip install grip --user (pip is working again after a system upgrade).

[joeyespo]

You're welcome!

Did you mean pip install grip --upgrade or pip install grip --user?

Also, try prefixing it with sudo, i.e. sudo pip install --upgrade grip and see if that helps. (The next version of grip shouldn't require sudo access.)

[faxm0dem]

pip install grip --upgrade --user
Not using sudo

Requirement already up-to-date: grip in ./.local/lib/python2.7/site-packages
Requirement already up-to-date: Flask==0.10.1 in ./.local/lib/python2.7/site-packages (from grip)
Requirement already up-to-date: Jinja2==2.7.3 in ./.local/lib/python2.7/site-packages (from grip)
Requirement already up-to-date: Markdown==2.4.1 in /usr/lib/python2.7/dist-packages (from grip)
Requirement already up-to-date: MarkupSafe==0.23 in ./.local/lib/python2.7/site-packages (from grip)
Requirement already up-to-date: Pygments==1.6 in /usr/lib/python2.7/dist-packages (from grip)
Requirement already up-to-date: Werkzeug==0.9.6 in ./.local/lib/python2.7/site-packages (from grip)
Requirement already up-to-date: docopt==0.6.1 in ./.local/lib/python2.7/site-packages (from grip)
Requirement already up-to-date: itsdangerous==0.24 in ./.local/lib/python2.7/site-packages (from grip)
Requirement already up-to-date: path-and-address==0.2.0 in ./.local/lib/python2.7/site-packages (from grip)
Requirement already up-to-date: requests==2.3.0 in /usr/lib/python2.7/dist-packages (from grip)
Cleaning up...

[joeyespo]

Hmm. That looks normal. I do know sometimes pip has trouble upgrading packages. If you can fully uninstall grip first, that might help. You can confirm Grip's version with grip --version. If it's "2.0.1", then this really could be a Grip bug.

Also, I haven't used pip install --user before, so perhaps that's causing trouble. Could you sudo pip install just to see if that works, then uninstall and try again with --user? That way we at least know if it's working or if Python / pip really is broken on your setup.

(If security is your concern, you could try it on a VM or cloud machine.)

[faxm0dem]

I just checked with a collegue with a clean install who tried too using virtualenv and he's having the exact same issues: ###title != ### title and the links not working. Version is indeed 2.0.1

[joeyespo]

Ok, great.

That's still bizarre though--all rendering actually happens on GitHub with its Markdown API, not locally by Grip. Could you copy / paste the following into a new README.md file, render it with grip, take a screenshot and post that here?

###Title 1

Body 1

### Title 2

Body 2

I wonder if I'll see an artifact I'll recognize. Thanks for being patient with this.

[faxm0dem]

https://gist.github.com/faxm0dem/cfd66c9747611884c7d9

[joeyespo]

Haha, ok. I know what's going on. I didn't think to try it with grip --gfm until just now; I thought you were running grip normally without arguments.

This is actually working as expected. If you want Title 1 to render like a README.md file, simply drop the --gfm argument. That's actually used when you want to render like user comments or issues. (More details here.)

Try it out. Copy / paste that into a new comment here and preview it. It'll look like your screenshot.

Cheers.