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

[Bug] Colon triggers a new "line" in line-by-line #139

Open
KronosTheLate opened this issue Jan 22, 2024 · 3 comments
Open

[Bug] Colon triggers a new "line" in line-by-line #139

KronosTheLate opened this issue Jan 22, 2024 · 3 comments

Comments

@KronosTheLate
Copy link
Contributor

The following code:

#slide(title: "title")[
  #line-by-line[
    test:theese:words
  ]
]

Ends up producing subslides that reveal one word or colon at a time:
image

So it seems like a colon introduces a new "line" both before and after itself. This makes it impossible to write "The solution: more duct tape" in a line-by-line environment (with each line actually revealed one at a time).

@KronosTheLate
Copy link
Contributor Author

Interestingly, when putting the same content into a bullet, this does not happen.
Code:

#slide(title: "title")[
  #line-by-line[
    - test:these:words
    - also:these:words
  ]
]

Output:
image

@andreasKroepelin
Copy link
Owner

andreasKroepelin commented Jan 22, 2024

#line-by-line is implemented in quite a hacky way, so this failure is not surprising. It actually one-by-ones the children of the given sequence. Often, those are the lines, but not always. So yeah, use #one-by-one for a more robust behaviour.

@KronosTheLate KronosTheLate changed the title [Bug] Colon trigger a new "line" in line-by-line [Bug] Colon triggers a new "line" in line-by-line Jan 23, 2024
@KronosTheLate
Copy link
Contributor Author

Fair. I have also found just using #pause quite perfect. I will keep this issue around for a future fix.

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

2 participants