-
-
Notifications
You must be signed in to change notification settings - Fork 100
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
Add ampersand replacement
option
#50
Comments
If we use |
Hmm, as I see it there are 3 approaches
- Option 1 is to use something really long
(`\definatly_unique_cell_seperator`), but that decreases the readability
and editability of the production
- Option 2 is to make it configurable within the webpage
- Option 3 is to no nothing, and make beamer users manually tweak the output
I'm not sure which is best.
…On Mon, Jun 1, 2020 at 11:32 PM Yichuan Shen ***@***.***> wrote:
If we use \& as separator as default, how would one specify a literal &
in one of the cells?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#50 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG3SWKRUWC7KQVCPAQEPKHDRUQT7HANCNFSM4NQE5GKQ>
.
|
One of the StackExchange solutions proposes to specify |
Not that I know of, so I guess I'll just use that. |
Sorry for digging this out again.
See https://tex.stackexchange.com/questions/136240/drawbacks-of-using-fragile-frames-in-beamer:
Especially the first point about slow compilation is a valid concern that I share, hence, I am always using |
Hm... in that case we should allow the user to specify their own ampersand replacement inside the code box. Here are some steps that need to be done:
|
In the
beamer
class, one needs[ampersand replacement=\&]
to make it work. sourceIt would be nice if there was an option to do this, or if it was the default. I'm not sure if there is a situation in which this behaviour isn't desirable
I'd be willing to implement this if you could point out the relevant parts of the code.
The text was updated successfully, but these errors were encountered: