Closed wallace11 closed 4 years ago
You can use <C-r>
.
Alright, now we're talking! The Only problem is that it won't refetch tasks. Would you like me to open a separate issue for that?
Also, maybe phrasing in the help file could be improved since I completely misunderstood the function of that xD
On Sun, Jul 12, 2020 at 4:45 AM itchyny notifications@github.com wrote:
You can use
. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/itchyny/calendar.vim/issues/177#issuecomment-657160980, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJ6HIN2WNMQYL77EK2ZKKLR3EIVDANCNFSM4OXQI4CQ .
The Only problem is that it won't refetch tasks.
This has been fixed.
@wallace11 about your reference to #166 , sorry for being unclear, I was more talking about event upload to Google Calendar adding a lag of a second or two when creating new events on the Calendar.vim GUI, as opposed to event download from Google Calendar. Though I suppose the <C-r>
idea would be helpful if there were a way to turn off automatic upload to Google Calendar and then sync both the up and down directions on demand with <C-r>
. Maybe that's what you were talking about?
Having to relaunch
:Calendar
each time there's an update to the calendar (new invitation, for example), is quite a pain, so I thought maybe there's an easy way to solve this problem.Simply add a mapping to manually fetch data from Google which will effectively refresh the calendar + tasks just as it does when launching. Maybe R (shift+r) is a good idea for a default keybinding.
Also, it may be be a good idea to implement a threshold for manual refreshing, that'd prevent multiple API calls (10s maybe?).
This is a different and probably more sane approach to #166.