[O] Custom time stamps and HTML export and #+BIND
Hi Nicolas, I have a file that I am exporting to HTML, and the file contains #+BIND: org-time-stamp-custom-formats (%d-%m-%Y . %d-%m-%Y %H:%M) #+BIND: org-display-custom-times t Apparently these lines are not used during HTML export. I debugged the org-translate-time function. When it is called during HTML export, both variables do not have the desired values. This should still work, right? - Carsten
Re: [O] Custom time stamps and HTML export and #+BIND
On 27.4.2013, at 08:24, Carsten Dominik domi...@uva.nl wrote: Hi Nicolas, I have a file that I am exporting to HTML, and the file contains #+BIND: org-time-stamp-custom-formats (%d-%m-%Y . %d-%m-%Y %H:%M) #+BIND: org-display-custom-times t Apparently these lines are not used during HTML export. I debugged the org-translate-time function. When it is called during HTML export, both variables do not have the desired values. This should still work, right? Never mind, I had not turned this feature on. Sorry for the noise - Carsten
[O] OT, but not really: todays XKCD
Hi everyone. I am sorry for the spam, but todays XKCD http://xkcd.com/1172/ is just too good to not share here, together with this piece of data: $ grep defcustom lisp/*el contrib/lisp/*el |wc -l 1213 Hurray for Nicolas and Bastien to be brave and switch to the new exporter framework which is a thing of beauty. Lets help them to fix the bugs as quickly as possible and then make those small adaptations in our workflow - it will be worth it. - Carsten
[O] Exporter question
Hi, In a file with some time stamps in headlines, is it still possible to get rid of them only for the Table of Contents, but to leave them in the headlines themselves? Thanks - Carsten
Re: [O] [PATCH] Lookup functions, take two
Hi Bastien, since you copied me, I guess you want my comment? I think this is very useful functionality and I would vote for putting it into the core. The documentation should be kept as compact as possible, I think without an example, just describe the functionality. Maybe Jarmo can write a little tutorial for Worg and document it there more extensively? - Carsten On 25.9.2012, at 03:49, Bastien wrote: Hi Jarmo, thanks for the explanations -- I should I've read your doc patch more closely. It is a nice spreadsheet utility function but my feeling is that having it in Org's core does not really fit, as it introduces functions where we usually have references. Functions are fine for users to add, though, that's the whole point of allowing Elisp in table formulas. Maybe I'm too conservative on this one. I will wait for other users' insight -- especially Carsten, who can better decide what fits and what does not in this area. Thanks, -- Bastien
Re: [O] [BUG] turn-on-org-cdlatex
Updated, thanks. - Carsten On 3.8.2012, at 09:41, Bastien wrote: Hi Rasmus, Rasmus ras...@gmx.us writes: It would seem there is a bug in turn-on-org-cdlatex whenever _ or ^ is called. And perhaps others. This is a problem in cdlatex.el. You need to replace `last-command-char' by `last-command-event'. I'm copying Carsten so that he can take the fix upstream. HTH, -- Bastien
Re: [O] Sticky Agenda buffer: Announcement and request for testing
On 3.4.2012, at 09:06, Bastien wrote: Hi Carsten, Carsten Dominik domi...@uva.nl writes: of course this is how I'd like it to work as well, but this was too hard for the moment... :( No problem -- since `org-agenda-sticky' is nil by default you can proceed with the merge when you think it's okay (also see Martyn's feedback) and we can try to implement such an option later on? Yes. I am not 100% sure that there are no side effects left - but the best way to find out is to merge it. Maybe we need to document the restriction issue. - Carsten Your take. Thanks! -- Bastien
[O] Sticky Agenda buffer: Announcement and request for testing
Hi everyone, already in Januar, Max Mikhanosha had published the first version of his code to implement multiple agenda buffers. I have worked with him over the last few weeks, and we think that it is now quite stable. Sticky agenda buffers (this is how Max calls it now) means the ability to keep multiple agenda buffer around. So while this does not cut down on the time it takes to create an agenda view, it has massive impact in a situation where you would like to switch between different agenda views frequently. The code it available in the git repository, in the branch max-sticky-agenda. And it would be great if a few people could go ahead and do some testing before we merge it. Testing should be done both with sticky buffers turned off and turned on. We have made it now very simple to test it: git pull origin git checkout max-sticky-agenda Then, in Emacs, use the `*' key in the agenda dispatcher to turn sticky buffers on and off. Since sticky buffers are not made new each time you look at them, you need to update them when you think it is needed, by pressing `g' or `r' in the buffer. To make sure all buffer are rebuilt, use `C-c a * *', so press the star twice to toggle sticky buffer off and back on. This will remove all existing agenda buffers, so that they will be made again when you dispatch to them. Regards - Carsten and Max
