Joshua Levy

Results 115 issues of Joshua Levy

Converting internal section links to slugs in Markdown is a recurring pain. And very confusing for certain sections with numbers or punctuation because nuances of slugging rules (see [github-slugger](https://github.com/Flet/github-slugger)). -...

enhancement
priority

Problem: Spaces around ellipses are a common typographic inconsistency. CMS recommends a thin space. Also breaking before an ellipsis is ugly. (After may be necessary or acceptable.) ![Image 2021-11-22 at...

enhancement
thinking
priority

Some seem to desire breaks on phrases like commas or clauses. This might or might not be a good idea, so listing here to track+discuss.

enhancement
thinking

Need a way to disable enumarations, e.g. paragraphs that start with `1. blah blah` but should not be enumerated. A `1\. blah blah` should do this. See https://github.com/jlevy/atom-flowmark/commit/8883e8cb67b078fe81d1b2ce03a8c28d41f3039b — Flowmark...

bug
priority

See line break reproduced here (not sure if remark or flowmark at fault). https://github.com/jlevy/atom-flowmark/commit/50be48623c8a61376b7b2dd60da479ca8304fbcd#diff-45486205dce63c55188d5aa2d93c4877R34-R35

bug
priority

Use cases: - Word list for commonly misspelled words (e.g. `Airbnb` vs `AirBnb` etc) - Cleaning up URLs e.g. `https://www.amazon.com/Corporate-Directors-Guidebook-Seventh-Committee/dp/1641055928/ref=sr_1_2?dchild=1&keywords=corporate+director%27s+guidebook&qid=1585787999&s=books&sr=1-2` -> `https://www.amazon.com/Corporate-Directors-Guidebook-Seventh-Committee/dp/1641055928/` Ideally this would be literal or regex, as...

enhancement

On save re-run for whole doc. Ideally an option. Also, it should not do the rerun unless Markdown is strictly good syntax, e.g. to avoid #18 Probably should be a...

enhancement

As a convenience, Flowmark should work on a Markdown file with YAML frontmatter, and then auto-format the YAML. This would also catch lots of syntax errors, normalize quote usage in...

enhancement
priority

A few issues with footnotes, reproduced at https://github.com/jlevy/atom-flowmark/commit/a2653ff93840ce1003e003c3964484948d67def3#diff-45486205dce63c55188d5aa2d93c4877R640 Current issues: - [x] When footnote text contains spaces, colon is erroneously escaped - [x] Consistent handling of ``s around bare URLs...

bug

See https://github.com/jlevy/atom-flowmark/commit/699f40a3aca5e9248d8a25ddb65b39e529837f7b#diff-45486205dce63c55188d5aa2d93c4877R96-R97 for an example In most common cases however, this seems like a good thing. So not sure of best change to the rule.

annoyance
thinking