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

Doesn't work with RevealJS HTML Backend #44

Open
1 of 4 tasks
shivams opened this issue Jul 31, 2023 · 1 comment
Open
1 of 4 tasks

Doesn't work with RevealJS HTML Backend #44

shivams opened this issue Jul 31, 2023 · 1 comment

Comments

@shivams
Copy link

shivams commented Jul 31, 2023

I am using it as follows

#+begin_parallel
[[color:orange][Are you excited to learn some Lisp?]] [[blue:Yes!]]

Pop-quiz: How does doc:apply work?
#+end_parallel

In the HMTL backend,

it works fine.

However, when I export it to revealJS HTML

Using the org-reveal package, the generated HTML doesn't reflect the different columns as it does in plain HTML. As I inspect the generated HTML using the reveal backend, it has no special CSS inserted as it had in the plain HTML backend.

Please tick the following, by replacing [ ] with [X]

  1. I am aware of the extensive documentation at http://alhassy.com/org-special-block-extras/
  2. I have read the documentation of doc:org-defblock
  3. I have checked some boxes without reading them.
  4. I am aware that (org-defblock X ⋯) gives me a Lisp function org-block/X
    that I can play with; e.g., C-h o org-block/shout shows a function with its
    docstring and arguments. We can press C-u C-x C-e at the end of the
    closing parens of (org-block/shout 'html "*Hello*, /world/!") to see
    what Org sees when it rewrites a shout block with the given string as its contents.
@suhail-singh
Copy link

This is because org-special-block-extras hardcodes backend checks based on
strict equality (e.g. using (equal backend 'html) or (equal backend 'latex))
instead of using org-export-derived-backend-p from 'ox.

Perhaps @alhassy will have time to either fix it or review a patch that fixes
it.

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