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

Verbatim not parsing properly when it ends with a quote character? #87

Open
gitonthescene opened this issue Mar 23, 2021 · 3 comments
Open

Comments

@gitonthescene
Copy link

I gather that this tool is what's being used in github to parser to parse orgmode files. I'm seeing an issue with my README.org file.

Specifically here:

   - ~CSVKWARGS~  - Arguments to pass to [[https://docs.python.org/3/library/csv.html][csv.reader]].
     e.g. ~CSVKWARGS={'delimiter': ',',  quotechar='"'}~ for comma delimited files using ~"~ as quote character.

and here:

   - ~CSVECODING~ - Encoding of the CSV file.
     e.g. ~CSVECODING='utf-8-sig'~ is the encoding used for data downloaded from [[https://www.usgs.gov/core-science-systems/ngp/board-on-geographic-names/download-gnis-data][GNIS]].

Org-mode in Emacs has no trouble with it, neither does exporting to md within Emacs.

It looks like it might have to do with the quote character at the end of the verbatim string. I'm not at all familiar with Ruby so I'm not sure how to reproduce using this tool directly or debug the problem. Feel free to close if this is the wrong tool and this tool has no issue with it.

Regards

@angrybacon
Copy link

I can reproduce with single quotes and double quotes at the beginning and end of the verbatim. I can reproduce with the code markup as well (~ pairs)

Other quote characters that I could test work fine: ‘’ and “”

✅ =foo'bar= 
✅ =foo"bar= 
❌ =foobar'=
❌ ='foobar=
❌ =foobar"=
❌ ="foobar=

@Thaodan
Copy link

Thaodan commented Jul 31, 2022

I wonder if this because of the old version used on Github. Github/markup lists Org-Ruby 0.9.9.

See also: github/markup#1581

@Thaodan
Copy link

Thaodan commented Jul 31, 2022

Duplicate of #79, one of the other should be closed.

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

3 participants