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

Allow choosing the heading level to use for frames. #2

Merged
merged 1 commit into from
Jun 20, 2011
Merged

Allow choosing the heading level to use for frames. #2

merged 1 commit into from
Jun 20, 2011

Conversation

punchagan
Copy link

Added a new variable EPRESENT_FRAME_LEVEL (similar to BEAMER_FRAME_LEVEL) which allows choosing the heading level to use, for frames.

Headings above the EPRESENT_FRAME_LEVEL should show an outline, but (org-cycle '(16)) doesn't seem to be working. Can you please fix that?

@eschulte eschulte merged commit f4b4a86 into eschulte:master Jun 20, 2011
@eschulte
Copy link
Owner

Hi punchagan,

Thanks again for another nice addition to epresent.

I've spent a good deal of time wrestling with the display of subtrees at
the line you mentioned. To my great frustration many of the build-in
outline-* functions seem to error out, throwing "before first heading"
errors.

I've implemented a different solution, which although maybe not as nice
as showing a folded subtree at intermediate outline levels with
`show-children' should be sufficient for now.

Thanks -- Eric

punchagan
reply@reply.github.com
writes:

Added a new variable EPRESENT_FRAME_LEVEL (similar to BEAMER_FRAME_LEVEL) which allows choosing the heading level to use, for frames.

Headings above the EPRESENT_FRAME_LEVEL should show an outline,
but (org-cycle '(16)) doesn't seem to be working. Can you please
fix that?

Eric Schulte
http://cs.unm.edu/~eschulte/

@shakthimaan shakthimaan mentioned this pull request Aug 22, 2015
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

Successfully merging this pull request may close these issues.

2 participants