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

Newline should not create a new HTML paragraph #26

Closed
kaushalmodi opened this issue Feb 24, 2017 · 4 comments · Fixed by #34
Closed

Newline should not create a new HTML paragraph #26

kaushalmodi opened this issue Feb 24, 2017 · 4 comments · Fixed by #34

Comments

@kaushalmodi
Copy link

kaushalmodi commented Feb 24, 2017

The paragraph marking style in org is the same as in markdown.

If I have

abcd
efgh

ijkl
mnop

it should export to HTML as

<p>
abcd
efgh
</p>

<p>
ijkl
mnop
</p>

But instead, it is currently creating a paragraph for each new line.


This is the expected behavior:

  • A single newline does not end a paragraph.
  • Two or more consecutive newlines end a paragraph (basically one ore more blank lines).

I found this issue because I like to enable auto-fill-mode for my posts with fill-column set to 70 in emacs.

@gour
Copy link

gour commented Mar 23, 2017

Any progress on this?

Having support for e.g. writing content in Hugo static-site-generator using org-mode support is great, but this issue is showstopper atm. 😢

@curiouslychase
Copy link
Owner

@gour yep, I'm working on it this week. Sorry, I've had a crazy March (travel for work and moving house) and this week is the first week I've had to even get on the computer outside of working hours. PR coming.

@gour
Copy link

gour commented Mar 23, 2017

@chaseadamsio Np. Let me, however, say that ability to use straight org-mode markup when writing content in Hugo is one of the strong reasons why I'm migrating to Hugo (from python-powered ssg)...and, yes, I plan to start learning Go in order to be able to contribute somehow...

@curiouslychase
Copy link
Owner

If you have any test cases you'd like to add, please comment on #34 with cases. The PR should resolve this issue.

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

Successfully merging a pull request may close this issue.

3 participants