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

fill-paragraph doesn't work after codeblock containing [3 #161

Closed
spacecowboy opened this issue Aug 26, 2016 · 3 comments
Closed

fill-paragraph doesn't work after codeblock containing [3 #161

spacecowboy opened this issue Aug 26, 2016 · 3 comments

Comments

@spacecowboy
Copy link

spacecowboy commented Aug 26, 2016

Noticed this weird thing after posting a makefile containing ascii formatting codes into a codeblock.

How to reproduce

Press M-q (fill-paragraph) on the line above and below the code block.

aaaaaaaaaaaaaaaa aaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaa

```
[3
```

aaaaaaaaaaaaaaaa aaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaa

Actual behavior

fill-paragraph does nothing on the line after the code block.

Expected behavior

fill-paragraph should behave the same for both lines

Version

markdown-mode is an installed package.

     Status: Installed in `~/.emacs.d/elpa/markdown-mode-20160803.1848/' (unsigned).
    Archive: n/a
    Version: 20160803.1848
   Requires: emacs-24, cl-lib-0.5
    Summary: Major mode for Markdown-formatted text
   Homepage: http://jblevins.org/projects/markdown-mode/
   Keywords: markdown github flavored markdown itex 
    Other versions: 20160803.1848 (melpa), 2.1 (melpa-stable).
@syohex
Copy link
Collaborator

syohex commented Aug 30, 2016

Could you tell us what is problem and what is your expected behavior in more detail ?
I suppose fill-paragraph works after code block as below, this is not does nothing.

test

jrblevin added a commit that referenced this issue Aug 30, 2016
@jrblevin
Copy link
Owner

I was able to reproduce and (hopefully) fix this in 3f11a4a. The problem was that markdown-mode mistakenly thought the point was inside an inline link due to the unclosed square bracket. Thanks for your report and please reopen if this didn't fix the problem.

@spacecowboy
Copy link
Author

@jrblevin that indeed seemed to do the trick. Thanks.

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