Oleksii Shmalko

The key is to add a unified plugin between `uniorg-parse` and `uniorg-rehype`. Something like this: ```js unified() .use(parse) .use(() => (node) => { // visit from unist-util-visit visit(node, 'keyword', (keyword)...

unified[1] is an ecosystem of tools for file processing (parsing file to AST, transforming AST, and converting AST to string). There are some tutorials on the unified website and online...

First, I want to say that this is not the default behavior as it requires modifying `org-emphasis-regexp-components` to work. The good news is that uniorg (the org parsing library) supports...

Oh, I see. This is a uniorg bug then. This is likely because javascript's `\s` class does not include ZWS but emacs's `[:space:]` does. The probable fix is to use...

FWIW, I use the following setup for my blog: ```js import prism from '@mapbox/rehype-prism'; const processor = unified() ... .use(prism, { ignoreMissing: true, alias: { lisp: 'common-lisp', }, }) ......

Looks good for me as a quick fix. (Ideally, this option should be set to the corresponding emacs option.) One clarification though: uniorg doesn't check the presence of the attachment—the...

> In the `org-roam-ui` side bar, I noticed that org links, like `pdf:/path/to/pdf`, are not clickable although they work in the emacs org file. `pdf:` links seems to be non-standard...

`uniorg-parse` takes an options object that allows to add more link types to be parsed: ```js import { defaultOptions } from 'uniorg-parse/lib/parse-options'; unified() .use(uniorgParse, { linkTypes: [...defaultOptions.linkTypes, 'eqref'], }) ```...

Hey, thanks for the bug report! It's more likely that space is lost in the `uniorg-stringify` rather than parser. One option to fix that is to add trailing whitespace for...

Hey. This structure is less "org-ish" because it doesn't follow org structure. Examples of cases that would be hard to handle: - inlinetasks (headings in-between content) - headings that don't...