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

cache notes #18

Open
mrtazz opened this issue Oct 27, 2011 · 9 comments
Open

cache notes #18

mrtazz opened this issue Oct 27, 2011 · 9 comments
Labels
harder idea up for grabs Maintainer has no plans to work themselves. Feel free to tackle.

Comments

@mrtazz
Copy link
Member

mrtazz commented Oct 27, 2011

Maybe there's a use case for offline access to notes. Caching should be simple, syncing might be the harder part.

@juanpabloaj
Copy link
Contributor

this is a great necessary feature, maybe you can search suggestions in stackoverflow.com

@juanpabloaj
Copy link
Contributor

Why don't use a ~/.simplenote dir?

@mrtazz
Copy link
Member Author

mrtazz commented Nov 29, 2011

The problem is more a general one. Caching notes means the plugin also needs more functionality to manage the cache. This is not a complicated or impossibly hard thing. However, I like that simplenote.vim is a rather thin interface layer for simplenote. I'm not set on not implementing caching, but I'm not sure that it would make the plugin actually better. But I'm open to suggestions :).

@tkb
Copy link

tkb commented Feb 10, 2012

Just a +1 from me here - caching notes for offline use + ability to search them would be awesome - Notational Velocity on the Mac is the gold standard for this kind of functionality - having the same function in vim across platforms would rock hard.

@ghost ghost assigned mrtazz Sep 25, 2012
@atomicules
Copy link
Collaborator

Some thoughts on caching, pretty much echoing what has been said above: I've flagged it against milestone v1.1.0 (currently we are on v0.7.0) to say that I will think about it, but not right now.

@mvance
Copy link

mvance commented Nov 19, 2014

Searching across all notes is the main feature I came to the issue queue hoping for, but it seems that would probably require caching to happen first. So, +1 from me.

@atomicules
Copy link
Collaborator

There is probably scope for using some of @insanum 's work on sncli to implement caching. Or it could be that for sncli does what you want already @mvance?

That's kind of been my worry/concern with caching all along. In a way, as soon as you've got something that handles caching and synchronising with Simplenote you just need any old text editor, is there a real need for Simplenote.vim then? I'm not sure.

On the other hand though, once the Simperium API becomes a requirement, then caching probably will be needed as it pretty much assumes applications work that way (you can't get the same information as you can with the Simplenote API).

I am still using Simplenote and Simplenote.vim day in and out so maybe I'll find time to look at this next year.

@jtoy
Copy link

jtoy commented Feb 19, 2017

+1

atomicules added a commit that referenced this issue Nov 4, 2018
Relies on upstream changes in simplenote.py to fetch only notes changed
since a cursor.

This way though the initial load of a list index is slow, but any
subsequent updates of `:SimplenoteIndex` are _much_ faster.

This is paving the way for then storing this lightweight cache on disk
so startup from scratch is also faster. Baby steps. It's still not a
full offline cache of notes, but I still don't know if simplenote.vim
should ever do that. There are other solutions.

Also remove some blank lines, fix some typos/grammar, etc that I
noticed.

References: #102
References: #96
References: #18
@atomicules
Copy link
Collaborator

Meant to reference this issue with this commit: a561166

@atomicules atomicules removed this from the v1.4.0 milestone Apr 8, 2019
@atomicules atomicules added the up for grabs Maintainer has no plans to work themselves. Feel free to tackle. label Jun 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
harder idea up for grabs Maintainer has no plans to work themselves. Feel free to tackle.
Projects
None yet
Development

No branches or pull requests

6 participants