-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
Full Textile support #271
Comments
stkb
added a commit
that referenced
this issue
Feb 7, 2022
Starting in pre-release version 17.6 Textile files will be treated as markdown, which should cover most cases but won't be perfect. For full support I will need someone to help by writing the specs. See this comment |
stkb
added
help wanted
in pre-release version
Is in pre-release version but not in stable yet
labels
Feb 7, 2022
stkb
added a commit
that referenced
this issue
Feb 14, 2022
stkb
added a commit
that referenced
this issue
Feb 14, 2022
- Support .rmd files as markdown (#245) - Basic support for Textile files as markdown (#271) - Support FIDL (#255), Pascal/Delphi (#97) & pylintrc files (#121) - Shell script: Ignore shebangs (#129) - Add '//'-comments to CSS (workaround for #309) - Fix batch files: case-insensitive "REM" and "@" prefix (#313) - Fix the document being 'modified' if there were no actual changes (#308, #315)
The markdown fallback in now also in stable v1.16.2. I'm going to leave this issue open for full Textile support. |
stkb
changed the title
[Feature Request] Rewrap Support for Textile
Full Textile support
Feb 14, 2022
stkb
added
feature request: needs votes 👍
and removed
in pre-release version
Is in pre-release version but not in stable yet
labels
Feb 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Textile documents are not currently supported by Rewrap. By switching the language to plain text (
Ctrl
+K
,M
), wrapping is done perfectly, but the syntax highlighting is broken. It would be great to support this markup language.The text was updated successfully, but these errors were encountered: