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

support for wiki syntax, including internal links #3

Open
joshsh opened this issue Aug 1, 2016 · 2 comments
Open

support for wiki syntax, including internal links #3

joshsh opened this issue Aug 1, 2016 · 2 comments

Comments

@joshsh
Copy link
Member

joshsh commented Aug 1, 2016

Currently, atom values are opaque. Formatting syntax in the text of atoms has been avoided, as it makes special logic for display necessary, and complicates automated analysis of text.

However, certain wiki syntax would be very useful, such as [internal links][7cYd8xt] and external links.

Brain-mode already uses wiki-style bulleted, indented lists. Certain markup such as font face and color might clash with Brain-mode's use of fonts to encode information about an atom, but would be useful in creating content for the Web. Existing tools such as Markdown Mode could be used for rendering.

@JeffreyBenjaminBrown
Copy link
Member

The clash you describe could be helped by single-character colored flags prepended or appended to individual nodes. As a Freeplane importer, I would enjoy being able to assign the property " don't (unless it is asked for) display this node as a child, but prepend any display of any parent of this node with a blue flag" to the node that represents what was in Freeplane the blue font.

@joshsh
Copy link
Member Author

joshsh commented Aug 1, 2016

A, colorized column would carry the same information, although I wonder whether it would have the same visual impact as styling the entire line. There is always room for another view style.

I think what you describe -- styling a node on the basis of its neighbors -- goes beyond wiki text and gets into dynamic views. Also a future possibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants