Closed Bruno-Sosa closed 8 years ago
I sorry if I mixed up my terminology, as I'm not a programmer (know a bit a python, but definitely not OOP). I'm running Arch Linux if that helps.
I fixed the out of range problem with a simple fix few days ago. Please update and see if the issue still exists?
The main reason is when there is no matched agenda, raw_agenda
is empty. Yet the empty array was not handled properly.
Also, you also need to setup your agenda files with let g:org_agenda_files=['list', 'of'. 'files']
, e.g.,
let g:org_agenda_files=['~/research_Documents/research/journal.org', '~/projects/todo-list.org']
Oh, no. The new changes are not released yet. I suggest you use vim-plug to install it. vim-plug is a good plugin-manager.
Add the line
Plug 'jceb/vim-orgmode'
In your .vimrc
after installing vim-plug and invoke
:PlugInstall
ha, ok guess one more package won't hurt :) (at least its minimalist) Thank you anyways.
Whenever I type
-caa
(where-
is my localleader) I get the following message:I can't figure it out. I looked at the mentioned line, and where raw_agenda is defined.
ORGMODE.agenda_manager
is imported from here, which callsAgendaManager()
. Looking at the imports leads me to where.get_next_week_and_active_todo
is defined. (yes the todos are active and within this week, it works fine in emacs org-mode) It is being called withagenda_documents
, which is defined here. I have no idea whatcls
is or what is callinglist_next_week
in the first place