Re: [O] Org-mode release 7.8.11
On 25 May 2012, at 08:51, Bastien wrote: Hi all, I've released Org 7.8.11. How do we view changelogs for minor versions? http://orgmode.org/Changes.html only appears to show changes for 7.8 (and, in the top section, changes in 'HEAD'). I would like to know the differences between (for example) 7.8.03 and 7.8.11. Thanks, Jules
Re: [O] Org-mode release 7.8.11
On 29 May 2012, at 10:55, Bastien wrote: ~$ git log release_7.8.03..release_7.8.11 will display the git logs between those two releases. Thanks. I will find myself a git checkout and take a look. The purpose of http://orgmode.org/Change.html is to contain a human-readable log for major releases -- the logs for the development version are not completely written (they are in development too). This is reasonable. Do I take it then that releases like 7.8.x are development releases? As a counter-argument, I remark that if 7.8 contains bugs (I believe it does?) and you have release bug fix releases in the 7.8.x series then normal users might reasonably want to install them, and might reasonably want to understand what bugs are fixed. (normal users I guess would not necessarily have a git checkout handy to run diffs on) Of course I recognise that organising changelogs is time consuming task and the org development team are busy people. Jules
Re: [O] Keeping an advanced dictionary in Org-mode?
On 6 Jun 2011, at 10:38, Christian Moe wrote: ** languir :PROPERTIES: :Word_class: verb :Transitivity: intr :END: (*for* après; *to do* de faire) It's a pain to do, and because of outline folding, it could be a pain to look up meanings, and you might need to do some serious post-processing on the export to make it look anything like a dictionary. But when you're done, you could extract a list of all botanical terms (:bot:), or of words and pronunciations only... etc. Column View is your friend. Both for lookup and for data entry. Jules
[O] Error message could be improved - Specified time is not representable
Hi all, On upgrading to emacs 23.3 (from emacs 23.1) my daily/weekly agenda became unusable, giving the error message Specified time is not representable. After a bit of poking around in the backtrace I tracked this down to an erroneous SCHEDULED date of 1st January 1904 buried inside a task. (This date was created by a bug in a script I was using to import TODOs from another system). Evidently, for some reason, calling (encode-time 0 0 0 1 1 1904) on 23.3 causes the error above, whereas on 23.1 it's silently ignored? I think the best thing for org-mode is to catch this error and report it to the user in a more understandable way so they can locate and fix the buggy timestamp - at least, include the full text of the timestamp so they can easily grep for it? Jules
Re: [O] Error message could be improved - Specified time is not representable
On 24 May 2011, at 09:16, Giovanni Ridolfi wrote: Julian Bean ju...@jellybean.co.uk writes: [...] I tracked this down to an erroneous SCHEDULED date of 1st January 1904 buried inside a task. [...] Evidently, for some reason, calling (encode-time 0 0 0 1 1 1904) on 23.3 causes the error above, This is probably related to the same problem as discussed in this thread: http://thread.gmane.org/gmane.emacs.orgmode/39206 on the limitations of unix time (whether on Unix or not...). Thanks, I missed that. You're right, that describes another manifestation of the same issue. whereas on 23.1 it's silently ignored? Since it is an Emacs problem I think you should ask Emacs's developers: emacs-de...@gnu.org or file a bug report: M-x report-emacs-bug or write to bug-gnu-em...@gnu.org I disagree. It's not a clear emacs bug - the docstring for encode-time says very clearly Years before 1970 are not guaranteed to work. On some systems, year values as low as 1901 do work.. encode-time is working as documented and I certainly don't understand emacs' date-time internals well enough to suggest a better way. The *org-mode* bug is, simply, the error message (hence my message title). If this exception does occur, it would be nice if org-mode would catch it, and provide better information to the user about which timestamp he needs to fix. Jules
