-
Notifications
You must be signed in to change notification settings - Fork 115
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
New lines should be interpreted. #46
Comments
Hi, If you propose a pull request which implements the newline behavior you desire behind an option, where the default remains what it is today, that'd be a reasonable way forward. |
I can't wait for a truncate_html allowing line breaks. It's currently unusable with long code. |
Did you end up fixing this for yourself? Getting the same problem for my new blog engine... |
@jipiboily nope, as far as I know, nobody has come up with a patch yet. |
…bols from source)
I know there was this issue: #43
But should it not just interpret the new line?
Take my website for example: http://www.dchapman.io/ (here the code examples look wonky because the new line chars are getting replaced with spaces).
Here's what the post should look like: http://www.dchapman.io/posts/changing-column-type-in-postgresql-rails
Here's what the index looks like where
truncate_html
is being used: https://github.com/dchapman1988/dchapman.io/blob/master/app/views/posts/index.html.slim#L10The text was updated successfully, but these errors were encountered: