Skip to content

Conversation

facelessuser
Copy link
Collaborator

  • At some point the logic of counting backtics and determining if they
    are odd or even was used to parse a row's text into cells.
    Unfortunately this approach broke expected code parsing logic in a
    table. We essentially traded one bug for another. This fixes table
    backtick handling and restores sane backtick logic while preserving
    existing fixes. (Another table and inline code issue #449)

  • Travis should checkout aspell-en (FYI: Spelling silently failing in Travis #521)

facelessuser and others added 5 commits January 10, 2017 12:49
At  some point the logic of counting backtics and determining if they
are odd or even was used to parse a row's text into cells.
Unfortunately this approach broke expected code parsing logic in a
table.  We essentially traded one bug for another.  This fixes table
backtick handling and restores sane backtick logic while preserving
existing fixes.
Travis should checkout aspell-en
One thing got overlooked.  Backslashes don't quite work the same on
backtics.  To keep the same feel as code outside the table, we need to
account for backslash and backtics the same.
@facelessuser
Copy link
Collaborator Author

Sorry for the multiple commits. I had forgotten that inline code is evaluated before escapes. With squash and merge I might be okay, but if you need a rebase anyways, let me know.

@waylan
Copy link
Member

waylan commented Jan 11, 2017

I'd prefer the different things to be in different commits. If you could rebase that would be preferred.

@facelessuser
Copy link
Collaborator Author

Will do. I kind of figured, but I was hoping :).

@facelessuser
Copy link
Collaborator Author

Close for rebase.

@facelessuser
Copy link
Collaborator Author

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