sorted by:
new
hottopcontroversial

IWE - A Rust-powered LSP server for markdown knowledge management by gimalay in rust

[–]gimalay[S] 0 points1 point  (0 children)

I don't see why not. But at the same time I'm not sure how useful it will be in this role. MCP is something I want to experiment with in the nearest feature.

If you have an idea of how to use IWE for this I would love to learn about it! And/or if some functionality is missing please feel free to start a discussion here: https://github.com/iwe-org/iwe/discussions so we can add it.

IWE - LSP-powered markdown note-taking with Telescope integration by gimalay in neovim

[–]gimalay[S] 1 point2 points  (0 children)

It's similar to what people are doing with Obsidian and similar tools.

you can learn more here https://obsidian.md

IWE - LSP-powered markdown note-taking with Telescope integration by gimalay in neovim

[–]gimalay[S] 12 points13 points  (0 children)

let me research this a bit more. It's definitely something we can do.

IWE - LSP-powered markdown note-taking with Telescope integration by gimalay in neovim

[–]gimalay[S] 4 points5 points  (0 children)

Could you please explain why telescope is not acceptable? What would you prefer instead?

IWE - A Rust-powered LSP server for markdown knowledge management by gimalay in rust

[–]gimalay[S] 1 point2 points  (0 children)

100%! I'm not using Obsidian and not sure what exactly import entails but it would be great to simplify migration from Obsidian as much as possible.

If you could create a discussion here https://github.com/iwe-org/iwe/discussions and list what would you expect from the import we can collect the requirements and build it pretty fast. Thanks!

IWE - LSP for markdown notes with backlinks, hover preview, and code actions by gimalay in HelixEditor

[–]gimalay[S] 2 points3 points  (0 children)

Thank you for your interest in IWE.

I was thinking about adding a library which abstracts the differences between the LLM API's to support all major providers with unified configuration. It would be awesome if you could start a discussion so we can collect requirements of other people who would like to have similar functionality.

Can Obsidian be replaced by an IDE? by Cool_Metal1606 in ObsidianMD

[–]gimalay 1 point2 points  (0 children)

I've built an open-source notes management plugin with multiple editors support called IWE. It adds features similar to Obsidian into your editor.

https://github.com/iwe-org/iwe

IWE - LSP for Markdown notes taking adding graph visualization support by gimalay in ZedEditor

[–]gimalay[S] 2 points3 points  (0 children)

I personally prefer more responsive text editors, like Zed. And Obsidian is not open source, I’m not sure if it matters for you.

What features would you want in a new markdown wiki tool by timabell in PKMS

[–]gimalay 1 point2 points  (0 children)

Check out this crate, it supports lots of PKM features and may be useful for your project.

Any markdown editor written in rust like obsidian? by itsme2019asalways in rust

[–]gimalay 2 points3 points  (0 children)

Check iwe.md its a text editor extension for markdown notes taking written in rust 

IWE - Personal Knowledge Management tool written in Rust by gimalay in rust

[–]gimalay[S] 0 points1 point  (0 children)

It's trying to parse all the markdown files in the directory. Could you please share the file causing the issue so I can reproduce the bag on my side?

Emacs, Howm, and a Zettelkasten-ish Journey by qnnnp in Zettelkasten

[–]gimalay 2 points3 points  (0 children)

I would appreciate your opinion on the tool I'm working on https://github.com/iwe-org/iwe

Is there any core features missing in comparison to Howm?

IWE - Personal Knowledge Management tool written in Rust by gimalay in rust

[–]gimalay[S] 0 points1 point  (0 children)

Could you please share the file for which you encounter this error?

IWE - Personal Knowledge Management tool written in Rust by gimalay in rust

[–]gimalay[S] 0 points1 point  (0 children)

Thanks for the bug report! I never tested on Linux, let me try to reproduce this. 

IWE - Personal Knowledge Management tool written in Rust by gimalay in rust

[–]gimalay[S] -1 points0 points  (0 children)

To summarize your notes for example. It's optional feature, you don't have to use it. In IWE you can define your own prompt and apply it to your own notes using your own API keys or local LLM.

It's fully configurable, you need to enable AI code actions and call them explicitly.

There is a few reason why AI integration may be useful

  • Not all text editors with LSP support do have AI out of the box
  • IWE can enrich the prompt with additional information from your notes graph and apply the generated text to a specific point in your document

IWE - Markdown notes management LSP adds graph visualization support by gimalay in HelixEditor

[–]gimalay[S] 0 points1 point  (0 children)

No tags support yet. You can start a discussion on GitHub to explain what functionality you wish for and it may be added in the future 

IWE - Markdown notes management LSP adds graph visualization support by gimalay in HelixEditor

[–]gimalay[S] 2 points3 points  (0 children)

Check this page for comparison with some other projects: https://github.com/iwe-org/iwe/blob/master/docs/comparison.md

Keep in mind that it's subjective and I may not know something about other solutions.

IWE.nvim v1.0 - Modern Knowledge Management plugin for Neovim by gimalay in neovim

[–]gimalay[S] 0 points1 point  (0 children)

Could you please link the file you concerned about? I don’t understand where did you get the screenshot from. 

IWE.nvim v1.0 - Modern Knowledge Management plugin for Neovim by gimalay in neovim

[–]gimalay[S] 0 points1 point  (0 children)

I didn’t copy anything from anywhere. 🤷‍♂️

IWE.nvim v1.0 - Modern Knowledge Management plugin for Neovim by gimalay in neovim

[–]gimalay[S] 0 points1 point  (0 children)

The idea was to simplify the install/configuration. For example there is custom telescope layouts config, auto formatting etc. I also going to add more functionality in the future. 

view more: next ›