Hello, On 04 Mar - 16:06, Lluis wrote: > Well, right now I still have to decide on two independent issues: > - Whether the widget calls emacs to get the agenda or emacs automatically > rebuilds it. > The after-save-hook seems pretty much like the optimal solution, except in > my > case, where I edit from two machines and eventually synchronize agendas with > unison. I know it's not the better way to go. Anyway, I think I could > locally > trigger a th-org-update-agenda whenever I synchronize agendas :) > > - Whether I should use org-mode's default agenda format or build one from the > CSV information. Both are achievable. It's just that I still haven't thought > on which one I prefer :) > I think today I'll try with coloring the default format :)
To me, the main concept behind that module was to use a raw org file without running emacs which is a quite heavy piece of software. Reloading or launching awesome would mean lauching emacs. That's why I feel more comfortable with Tassilo's code, although it is someway emacs dependant because the file needs to be generated before. I'd rather keep the "all-in-awesome" approach. :) Cheers, -- Damien Leone <[email protected]> Web: http://dleone.fensalir.fr/ GPG: 0x82EB4DDF
signature.asc
Description: Digital signature
