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

Use newline CR to put on the next line #51

Open
himat opened this issue Mar 1, 2020 · 4 comments
Open

Use newline CR to put on the next line #51

himat opened this issue Mar 1, 2020 · 4 comments

Comments

@himat
Copy link

himat commented Mar 1, 2020

The docs say

And now if you press > again, the content will be:
<table>
    |
</table>

How can I get this same behavior by pressing the <enter> key (i.e. <c-r>) after I type the close > in <table>?

@caioariede
Copy link

@himat please check out this comment: #38 (comment)

@himat himat closed this as completed May 4, 2020
@himat himat reopened this May 4, 2020
@himat
Copy link
Author

himat commented May 4, 2020

@caioariede I didn't realize the formatting in my question was not showing correctly before.
I know that pressing > twice works. But I was wondering if I can make pressing enter do the same thing?

@brendonrapp
Copy link

I think pressing Enter once and getting that behavior is what a lot of us expected before we tried.

There's pretty much never going to be a time where I finish typing a tag, hit Enter, and actually want this:

<table>
|</table>

instead of

<table>
  |
</table>

Double-pressing > is not intuitive. If it's possible to get this behavior with a single instead, even as an option rather than default behavior, I think many of us would really appreciate it.

@JS-junky
Copy link

I think pressing Enter once and getting that behavior is what a lot of us expected before we tried.

There's pretty much never going to be a time where I finish typing a tag, hit Enter, and actually want this:

<table>
|</table>

instead of

<table>
  |
</table>

Double-pressing > is not intuitive. If it's possible to get this behavior with a single instead, even as an option rather than default behavior, I think many of us would really appreciate it.

i'm uninstalling this plugin and moving on to another one just because this is not available, sorry not sorry but it's been like a year since this issue is still open... so i think it's time to move on :)

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

4 participants