Skip to content

Visual Editor loses raw latex code blocks #558

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

Closed
gtritchie opened this issue Oct 2, 2024 · 0 comments · Fixed by #559
Closed

Visual Editor loses raw latex code blocks #558

gtritchie opened this issue Oct 2, 2024 · 0 comments · Fixed by #559
Assignees

Comments

@gtritchie
Copy link
Collaborator

gtritchie commented Oct 2, 2024

NOTE: This issue is due to a pandoc change, and also impacts the RStudio IDE (rstudio/rstudio#15253). I am working on a fix for both the IDE and the VSCode extension.

See also #552, already fixed.

Steps to reproduce the problem

  • Using extension version 1.115.0 in VSCode 1.93.1
  • Create a new Quarto document, edit in non-visual mode, add following:
---
title: "Raw tex Block Issue"
---

```{=tex}
\LaTeX
```

```{=latex}
\LaTeX
```

Save the file, then Edit in Visual Mode. The latex block looks ok, but the tex block has lost its specialness.

Image

Now switch back to source (non-visual) mode.

Describe the problem in detail

In Visual Mode, the tex block is removed leaving just the contents. The latex block looks ok in Visual Mode initially, but the underlying document has changed to:

---
title: "Raw tex Block Issue"
---

\LaTeX

\LaTeX

Describe the behavior you expected

Preserve the latex raw block as we did before the pandoc change.

Note that {=tex} being removed was already present before the pandoc change, so not covered by this issue.

@gtritchie gtritchie self-assigned this Oct 2, 2024
@gtritchie gtritchie changed the title Visual Editor loses raw tex code blocks Visual Editor loses raw latex code blocks Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant