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

markdown support #101

Open
pasteley opened this issue Feb 15, 2019 · 8 comments
Open

markdown support #101

pasteley opened this issue Feb 15, 2019 · 8 comments

Comments

@pasteley
Copy link

Hey guys, I am deeply appreciate your work and lifestyle, but maybe I am missing the core idea of this particular app, and what I miss for sure is basic markdown support, so I would like to share the feedback and get your vision on this. To be more precise:

  • The concept of using number sign (#) looks as not disclosed, cause it's hard do distinguish file names form L1, L2 headers. Some tree like view for sidebar would make it so much meaningful:
    image
  • Lack of URLs, code, inline code and quotes highlighting (in sense markdown symbols processing, not the code syntax), what do people really write down?
  • Opening url only working if url is clean of other symbols at the beginning and end of it, so something like this would not be working:
    [EXPLAIN SHELL](https://www.explainshell.com)

BTW don't you mind, if I will add this project as a Homebrew Formulae?

@frozenpandaman
Copy link

frozenpandaman commented Apr 14, 2019

#52 makes it seem like Markdown support is largely not within the original philosophy/scope of this project. However… perhaps a bit unrelated… I think some ability to emphasize certain text (e.g. render in bold) would be great, and helpful for visual distinction + navigation.

@pasteley, maybe check out FoldingText?

Also agreed on your "it's hard to distinguish file names from headers" point. I think even just indenting headers a bit (i.e. moving the "list" of them slightly rightward) would help?

@Memorytaco
Copy link

Can we just add more markers to it?
I really like it! I can do this. I like the way it acts now but if it can be more powerful for editing text that will be awesome!
markdown is somewhat heavy to it and will break what it has done, more markers may be enough.

@neauoire
Copy link
Member

I would totally like new markers, I'd merge that if you wanna give it a shot.

@frozenpandaman
Copy link

I like this idea too!

@Memorytaco
Copy link

I got an idea to find more special character.
white
Here i add one special character to left navi file sign, so we will not mix marker entries with file item.
black
How about that? if we add more markers, we should also add some actions associated with this marker. but special character will be fine.

@neauoire
Copy link
Member

I like this a lot, would you like to make a PR?

@Memorytaco
Copy link

I have noticed you would make a big refactoring for code. If so, could you use one front end framework like vue or react to make code more structure?

I prefer to import a framework into it to do the job and let framework to manage the lifetime of each component instead of manually.

We can import a symbol collection and define quick key note editor for user to define their own unique symbol. How do you think?

@neauoire
Copy link
Member

neauoire commented Jan 9, 2020

I won't be using a frontend for the front-end, sorry.

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

4 participants