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

What should be a plugin and what should be in the core #55

Closed
sotte opened this issue Aug 3, 2011 · 1 comment
Closed

What should be a plugin and what should be in the core #55

sotte opened this issue Aug 3, 2011 · 1 comment

Comments

@sotte
Copy link
Contributor

sotte commented Aug 3, 2011

I'm not quite sure when i should put something into the core or the plugins. The TODO functionality for example is an essential feature and could get simplified quite a bit if it get's integrated in the lib. I'm not suggesting to do so. I'm simply asking for a guideline.

ALso when should the plugin write in the vim buffer and when should the document object be altered?

Cheers,
Stefan

@jceb
Copy link
Owner

jceb commented Aug 4, 2011

Hi Stefan,

From my point of view everything should be integrated in the lib that is independent of vim. For instance the TODO functionality in liborgmode implements basic reading and writing. Everything more sophisticated like the selection dialog is implemented as a plugin. Did you think of specific functionality that you want to integrate into liborgmode?

Regarding the altering of the vim buffer, I recommend using the VimBuffer class. Because of performance reasons it might be of use to access vim.current.buffer directly, although I don't see many cases for that. VimBuffer.write_heading is a trade-off to speed up changes to just one heading(-tree).

@sotte sotte closed this as completed Apr 1, 2014
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