lorem*2 only give one line of lorem

[IronGhost63]

• VSCode Version: 1.24.1
• OS Version: macOS 10.13.5

Steps to Reproduce:

1. Create/Open an HTML file
2. type lorem*2 (also happen with lorem<number>*2) then tab

Result is expected to be 2 lines of lorem. but instead there is just one line with <number>*2 words.

Works fine with lorem*3

Does this issue occur when all extensions are disabled?: Yes

[Cirieno]

I can recreate this.

lorem*n is fine, but lorem*2 gives one long, unbroken line. In each test I have noted an element of punctuation, no break, and then the next word:

hic voluptate!Ab, velit
sint aperiam.Sequi animi
accusamus excepturi?Ad veritatis

VSCode 1.24.1// Windows 10 x64

[ramya-rao-a]

PRs are welcome to fix this bug.

The fix would be to the the upstream module called vscode-emmet-helper. There is a test case there for the case of lorem*3 which passes. As observed in this issue, changing that to 2 fails the test case.

[TheDancingCode]

One way around this is setting this in your vscode user settings:

"emmet.syntaxProfiles": {
    "html":{
        "inline_break": 1
    }
}

[dyong0]

@TheDancingCode Thanks, that gave me a hint to fix this issue!
microsoft/vscode-emmet-helper#26

[dyong0]

@ramya-rao-a, could you please review microsoft/vscode-emmet-helper#26?

[ramya-rao-a]

Thanks for figuring that out @TheDancingCode!

@dyong0 I wouldnt change the default for inline_break to 2 as it changes expectations for how inline elements are expanded.
For example, span*2 is expected to expand to <span></span><span></span> where as span*3 is expected to expand to

<span></span>
<span></span>
<span></span>

@sergeche

When trying out lorem in https://docs.emmet.io/, I noticed that lorem*n always surrounded the text by a div tag when n > 1

But the new emmet modules dont do this and so end up becoming an inline element and forced to follow the inline_break configuration.

How do you suggest we tackle this?

[TheDancingCode]

Surrounding lorem*n with div tags for n > 1 makes sense. Lorem Ipsum is meant to serve as dummy text or data in html elements, so I don't see any use for lorem*n except a quick way to create more elements containing text. If you simply want a longer text, that's what loremN is for. If you want more paragraphs, there's p*n>lorem.

[ramya-rao-a]

I've logged emmetio/expand-abbreviation#23 as an upstream issue with emmet and marking this issue as out of scope.

Once there is a solution from upstream, we can use the same in VS Code

[vscodebot]

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

[rzhao271]

\closedWith dc5a3da

[rzhao271]

Verifier: Ensure that running Emmet: Expand Abbreviation on lorem*2 in an HTML file expands to give two lines of lorem ipsum instead of just one.