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

Poor rendering of headers? #81

Open
larsks opened this issue Nov 26, 2019 · 2 comments
Open

Poor rendering of headers? #81

larsks opened this issue Nov 26, 2019 · 2 comments

Comments

@larsks
Copy link

larsks commented Nov 26, 2019

I'm feeding patat the follow input:

# An example deck

## This is a test

This is my first slide.

Here is some information.

## This ought to be a slide title

The quick brown fox:

- Jumped over the lazy dog.
- Injured itself upon landing.
- This is unsafe workplace behavior.

While patat is obviously recognizing the headers, it's not rendering them very well: e.g., the rendered headers still include the ## markers. For example, the title slide renders like this:

Screenshot from 2019-11-26 10-13-05

And the first slide renders like this:

Screenshot from 2019-11-26 10-14-10

Is this expected behavior?

@jaspervdj
Copy link
Owner

Yes, this is expected, to stick somewhat close to markdown format (which is good if people seeing the presentation recognize it's a header IMO). I didn't want to draw a line below it because that takes up a whole line of screen real estate. Do you have other suggestions/preferences? I would be happy to make the title rendering more configurable but I'm not sure about changing the default.

@larsks
Copy link
Author

larsks commented Nov 26, 2019

I agree re: not changing the default, but I would love to be able to drop the # markers from the headers and to use some sort of styling to indicate "header-ness".

If styling options included underlined/not underlined, that would be cool.

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