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.

Sign up for GitHub

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

Jump to bottom

Convert Bin + Rel/Close/Punct to Ord + Rel/Close/Punct #4

Closed
sophiebits opened this issue Aug 29, 2014 · 8 comments
Closed

Convert Bin + Rel/Close/Punct to Ord + Rel/Close/Punct #4

sophiebits opened this issue Aug 29, 2014 · 8 comments
Assignees
@xymostech
Labels
bug
Milestone
Version 0.1.1

Comments

@sophiebits
Copy link
Contributor

  1. If the current item is a Rel or Close or Punct atom, and if the most recent previous atom was Bin, change that previous Bin to Ord.
@xymostech xymostech added the bug label Aug 29, 2014
@xymostech xymostech modified the milestone: Version 1.0 Aug 30, 2014
@xymostech xymostech self-assigned this Aug 30, 2014
@xymostech xymostech modified the milestones: Version 1.0, Version 1.1 Sep 3, 2014
@sophiebits sophiebits mentioned this issue Sep 13, 2015
Closed
@sophiebits
Copy link
Contributor Author

(Also bins at the end of an expression, see #355.)

@wchargin
Copy link

Copying the table I posted there for reference (TeXbook, Chapter 18):
Table of atom conversions

@cbreeden
Copy link
Contributor

cbreeden commented May 22, 2016 •
edited

I felt like it's worth clarifying the explanation of * since it certainly is possible to write ++, +. etc...

rules

Source: TeXbyTopic, Section 23.6.1

@wchargin wchargin mentioned this issue May 26, 2016
Closed
@wchargin
Copy link

@cbreeden: Right; this conversion process is the topic of this issue :)

@cbreeden
Copy link
Contributor

@wchargin: Right, sorry 😕 I was just slightly confused for the deduction of converting bin to ords if they are last in the list (#355), until I was able to find this between rules 18 and 19. Knuth tricked me! 😊

@cbreeden
Copy link
Contributor

I did take a look at this issue a few days ago, however, and my conclusion was that given the current model we would probably just need to implement a next for the next token here. But I'm sure this was already known.

cbreeden added a commit to cbreeden/KaTeX that referenced this issue Jun 4, 2016
@cbreeden
Fix KaTeX#4 - Spacing interactions between atoms
af2ab4b
@cbreeden cbreeden mentioned this issue Jun 4, 2016
Closed
@kevinbarabash
Copy link
Member

@cbreeden It seems like pass the next group to all the groupTypes handlers would get you what you need.

@cbreeden
Copy link
Contributor

I did that 😊

@gagern gagern mentioned this issue Sep 29, 2016
Closed
kohler added a commit to kohler/KaTeX that referenced this issue Nov 21, 2016
@kohler
Fix KaTeX#4.
4ea7609 
Post-process the list of atoms after they are created, changing
binary operators to ordinary atoms according to the TeXbook's
rules. This makes the `prev` argument redundant, so drop it.
@kohler kohler mentioned this issue Nov 21, 2016
Merged
kohler added a commit to kohler/KaTeX that referenced this issue Nov 21, 2016
@kohler
Fix KaTeX#4.
e907177 
Post-process the list of atoms after they are created, changing
binary operators to ordinary atoms according to the TeXbook's
rules. This makes the `prev` argument redundant, so drop it.
kohler added a commit to kohler/KaTeX that referenced this issue Nov 22, 2016
@kohler
Fix KaTeX#4.
4a13e84 
Post-process the list of atoms after they are created, changing
binary operators to ordinary atoms according to the TeXbook's
rules. This makes the `prev` argument redundant, so drop it.
kohler added a commit to kohler/KaTeX that referenced this issue Nov 22, 2016
@kohler
Fix KaTeX#4.
2939c4d 
Post-process the list of atoms after they are created, changing
binary operators to ordinary atoms according to the TeXbook's
rules. This makes the `prev` argument redundant, so drop it.
kohler added a commit to kohler/KaTeX that referenced this issue Nov 23, 2016
@kohler
Fix KaTeX#4.
6af1c96 
Post-process the list of atoms after they are created, changing
binary operators to ordinary atoms according to the TeXbook's
rules. This makes the `prev` argument redundant, so drop it.
kohler added a commit to kohler/KaTeX that referenced this issue Nov 26, 2016
@kohler
Fix KaTeX#4.
dfe30fc 
Post-process the list of atoms after they are created, changing
binary operators to ordinary atoms according to the TeXbook's
rules. This makes the `prev` argument redundant, so drop it.
kohler added a commit to kohler/KaTeX that referenced this issue Nov 26, 2016
@kohler
Fix KaTeX#4.
ab614de 
Post-process the list of atoms after they are created, changing
binary operators to ordinary atoms according to the TeXbook's
rules. This makes the `prev` argument redundant, so drop it.
kohler added a commit to kohler/KaTeX that referenced this issue Nov 27, 2016
@kohler
Fix KaTeX#4.
0e60581 
Post-process the list of atoms after they are created, changing
binary operators to ordinary atoms according to the TeXbook's
rules. This makes the `prev` argument redundant, so drop it.
kohler added a commit to kohler/KaTeX that referenced this issue Nov 28, 2016
@kohler
Fix KaTeX#4.
262254e 
Post-process the list of atoms after they are created, changing
binary operators to ordinary atoms according to the TeXbook's
rules. This makes the `prev` argument redundant, so drop it.
kohler added a commit to kohler/KaTeX that referenced this issue Nov 28, 2016
@kohler
Fix KaTeX#4.
82a1b11 
Post-process the list of atoms after they are created, changing
binary operators to ordinary atoms according to the TeXbook's
rules. This makes the `prev` argument redundant, so drop it.
sebastianpantin pushed a commit to sebastianpantin/KaTeX that referenced this issue Sep 17, 2017
@dunfalk
Merge pull request KaTeX#4 from mrAlbert-development/dunfalk-20170524…
8b06fdd 
…-saveUserstate

minor fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xymostech xymostech

Labels
bug
Projects
None yet
Milestone
Version 0.1.1
Development

No branches or pull requests
5 participants
@sophiebits @xymostech @kevinbarabash @wchargin @cbreeden