[O] bug#13820: 24.3.50; Cannot switch to Org mode
Sebastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: This is *solved* in GNU Emacs 24.3.50.1 (i386-mingw-nt6.2.9200) of 2013-03-14 on VBOX, Great, thanks for confirming! -- Bastien
Re: [O] org-caldav will cease to work with Google Calendar
David Engster d...@randomsample.de writes: 'rasmus' writes: For now I'm using fluux, but I haven't managed to get org-CalDAV to sync yet. What is that? I'm afraid I cannot find it. Sorry, that's a typo. http://fruux.com. It works with the aCal package which is in the F-Droid archive for Android software. I'm also looking to sync bbdb via CardDAV, although I would be willing to switch to org-contacts if a solution emerged here before. CardDAV shouldn't be very hard to add. There are two reasons however why at least I won't work on this in the near future: I don't need it, and it's boring. Fair enough. A natural place to add it is the ASynK package. . . Baïkal and Radicale are nice, small CalDAV servers. The latter also provides CardDAV. I just discovered Radicale. I think it is very nice for people who don't want/need a full-blown Workgroup or Cloud solution like SOGo/Owncloud. org-caldav does not currently work with it, but this should be fixable. What I would need would be something I can install as an unprivileged user on a remote host. For instance something that could be called over SSH. . . I could install/compile Radicale on my remote host, but I don't know whether I would be able to access it when it's not running as a 'root' service. . . –Rasmus -- Vote for proprietary math!
Re: [O] [RFC] Org version of the Org manual
Hi Tom,
I'm playing around with the current version, here is what I have so far:
The arguments to #+attr_texinfo need to lose the double quotes
Index entries in description lists must be separated from their entry by
at least one blank line like in the example below, otherwise the second
such entry gets indented in the exported .texi file and that somehow
confuses texinfo for some of them.
--8---cut here---start-8---
- {{{kbd(v d)}}} or short {{{kbd(d)}}}, ~org-agenda-day-view~ ::
{{{kindex(v d)}}}
{{{kindex(d)}}}
{{{vindex(org-agenda-span)}}}
--8---cut here---end---8---
With these hanges I get the manual exported correctly to all formats.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
[O] make footnotes appear as tooltips on HTML export?
Hey everyone, I had a thought. So, I export most of my org files to both HTML and PDF. I was thinking that for HTML, the behavior of putting footnotes at the end of the document, as you would for a printed page, is a bit outdated. In a printed document, you put the footnotes at the end because you have to. But with HTML, it doesn't really make sense to make the user click through to the bottom of the document in order to discover the footnote content. It would be more in keeping with the spirit of hypertext to create a tooltip that the user could hover over and view the content instantly inline. This is trivial to implement using CSS3: http://www.webdesignerdepot.com/2012/11/how-to-create-a-simple-css3-tooltip/ and only slightly more complicated using jQuery: http://www.chillwebdesigns.co.uk/chilltip I was thinking about trying to create a way for org-mode to automatically create tooltips from footnotes, but I'm a beginner, so before I take a crack at it, I thought I would ask: has anyone already done this? Or, does anyone have ideas about how to easily automate this behavior using org export to HTML? Best, Peter
Re: [O] org-caldav will cease to work with Google Calendar
Hi, Supporting the Google Calendar API in org-caldav wouldn't be hard. It's actually a very clean, RESTful service; much better than CalDAV, in fact. Just what you would expect from Google. However, this is not a technical issue. This is also why I said that anyone who wants to implement support for the Google Calendar API in org-caldav should fork it; I won't accept pull requests which implement that. Actually I had a look at the API. It is indeed very clean, but there _is_ a technical issue, namely they limit access to a certain number of connections per day, and this is accounted per application rather than per user. Right now it is 10.000 a day, but just listing all events in a single calendar involves paging: for 200 or so events, I had to connect 7 times, and this counts as 7 connections. I have no idea how many org users would actually sync with google using their proprietary API (given there is support), but reaching the limit would be very quick, and very problematic. [Admittedly it is not a technical issue on their side, but it would be on ours, somehow.] If Google decides to discontinue a well established, IETF-standardized API in favor of a proprietary one for which there exist no free server implementations, I will not support that. I think the best solution for anyone using Google Calendar is to migrate away from that service. Agreed. Now to look for a replacement ... /v PS: In the mean time, for those who sync only from org to gcal, the option of exporting an ics file and hosting it somewhere for google to subscribe to is still available, but it is far from being as good.
[O] A mix of habits and effort estimates?
Hi list, say that I'd like to learn a new language or something. I'd like to devote, say, 180 minutes to it each week. Does anyone have an idea how to achieve something like that in Org-mode: * I create a task (say, Learn Italian) * I clock in/out when I start/stop doing this * I have a few other tasks like that * and somehow, org-magically, I can view a weekly report summarizing whether I spent too much or too little time on different projects. Is such a thing possible in Org-mode? I suspect that it might be doable, maybe with effort estimates and/or column view (which I don't use, but I can as well start using it), but it might also require some elisp hacking. Does anyone have a setup for something like this? Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Adam Mickiewicz University
Re: [O] A mix of habits and effort estimates?
Hi Marcin, Marcin Borkowski mb...@wmi.amu.edu.pl writes: Is such a thing possible in Org-mode? Did you check (info (Org)Tracking your habits) ? HTH, -- Bastien
Re: [O] make footnotes appear as tooltips on HTML export?
Hi Peter, Peter Salazar cycleofs...@gmail.com writes: I had a thought. So, I export most of my org files to both HTML and PDF. I was thinking that for HTML, the behavior of putting footnotes at the end of the document, as you would for a printed page, is a bit outdated. In a printed document, you put the footnotes at the end because you have to. But with HTML, it doesn't really make sense to make the user click through to the bottom of the document in order to discover the footnote content. It would be more in keeping with the spirit of hypertext to create a tooltip that the user could hover over and view the content instantly inline. This is trivial to implement using CSS3: http://www.webdesignerdepot.com/2012/11/ how-to-create-a-simple-css3-tooltip/ Trivial but a bit heavy -- at least this is not an option for the default HTML exporter, which tries to stick to the Old Good Way®. and only slightly more complicated using jQuery: http://www.chillwebdesigns.co.uk/chilltip I was thinking about trying to create a way for org-mode to automatically create tooltips from footnotes, but I'm a beginner, so before I take a crack at it, I thought I would ask: has anyone already done this? Or, does anyone have ideas about how to easily automate this behavior using org export to HTML? I don't know, but I think this would make a great entry for the Org hacks page! Good luck, -- Bastien
Re: [O] org-mode's HEAD org-remember bug?
Hi Marcelo, Marcelo de Moraes Serpa celose...@gmail.com writes: I just updated org to HEAD, and I'm getting the following error when trying to run the org-remember function (bound to C-c r): Sébastien is right, `org-remember' is now obsolete, so please update your capture templates accordingly if that's necessary. But your error seems to come from a dirty installation: make sur you follow the steps described in the manual: http://orgmode.org/org.html#Installation HTH, -- Bastien
Re: [O] [PATCH] Fix uncaught error when trying to open a link at point
Hi, Bastien b...@altern.org writes: No problem at all. I decided to go and accept patches from people that did not confirm they got the FSF papers because merging 8.0 into Emacs trunk is not likely to happen to soon... So. Good news, I got the confirmation that my assignment/disclaimer process with the FSF is currently complete. I do not know however if I have to do something to prove that in order to submit patches to this mailing list. I then propose in attachment a set of four tests testing the problem mentioned in this thread: the behavior of org-open-at-point in front of bracket links and plain links. From 5bd8eb52cb047b5290300fe850fca894babf05ff Mon Sep 17 00:00:00 2001 From: Samuel Loury konubinix...@gmail.com Date: Sat, 16 Mar 2013 20:12:42 +0100 Subject: [PATCH] Test the org-open-at-point function. * testing/examples/open-at-point.org: new file. * testing/lisp/test-org-open-at-point.el: new file. This tests only the function when inside or before bracket links and plain links. --- testing/examples/open-at-point.org |8 + testing/lisp/test-org-open-at-point.el | 61 2 files changed, 69 insertions(+) create mode 100644 testing/examples/open-at-point.org create mode 100644 testing/lisp/test-org-open-at-point.el diff --git a/testing/examples/open-at-point.org b/testing/examples/open-at-point.org new file mode 100644 index 000..b3bb92d --- /dev/null +++ b/testing/examples/open-at-point.org @@ -0,0 +1,8 @@ + +* Header 1 + :PROPERTIES: + :ID: header1_with_great_id + :END: +* Header 2 + [[id:header1_with_great_id][Header 1]] + id:header1_with_great_id diff --git a/testing/lisp/test-org-open-at-point.el b/testing/lisp/test-org-open-at-point.el new file mode 100644 index 000..78724c8 --- /dev/null +++ b/testing/lisp/test-org-open-at-point.el @@ -0,0 +1,61 @@ +;;; test-org-open-at-point.el + +;; Copyright (c) Samuel Loury +;; Authors: Samuel Loury + +;; Released under the GNU General Public License version 3 +;; see: http://www.gnu.org/licenses/gpl-3.0.html + + Comments: + +;; Test for the org-open-at-point function + +;;; Code: + +(save-excursion + (set-buffer (get-buffer-create test-org-open-at-point.el)) + (setq ly-here +(file-name-directory + (or load-file-name (buffer-file-name) + +(defun test-org-open-at-point/goto-fixture () + (find-file-other-window + (concat ly-here ../examples/open-at-point.org)) + (set-buffer open-at-point.org)) + +(ert-deftest test-org-open-at-point/bracket-link-inside () + Test `org-open-at-point' from inside a bracket link. + (test-org-open-at-point/goto-fixture) + ;; go inside the bracket link + (goto-char 113) + (org-open-at-point) + ;; should now be in front of the header + (should (equal (point) 2))) + +(ert-deftest test-org-open-at-point/plain-link-inside () + Test `org-open-at-point' from inside a plain link. + (test-org-open-at-point/goto-fixture) + ;; go inside the plain link + (goto-char 126) + (org-open-at-point) + ;; should now be in front of the header + (should (equal (point) 2))) + +(ert-deftest test-org-open-at-point/bracket-link-before () + Test `org-open-at-point' from before a bracket link but in the same line. + (test-org-open-at-point/goto-fixture) + ;; go before the bracket link + (goto-char 83) + (message point %s (point)) + (org-open-at-point) + ;; should now be in front of the header + (should (equal (point) 2))) + +(ert-deftest test-org-open-at-point/plain-link-before () + Test `org-open-at-point' from before a plain link but in the same line. + (test-org-open-at-point/goto-fixture) + ;; go before the plain link + (goto-char 124) + (org-open-at-point) + ;; should now be in front of the header + (should (equal (point) 2))) -- 1.7.10.4 -- Konubinix GPG Key: 7439106A Fingerprint: 5993 BE7A DA65 E2D9 06CE 5C36 75D2 3CED 7439 106A pgpJOvuA5BCP_.pgp Description: PGP signature
Re: [O] [bug] [new exporter] [markdown] Underline exports as HTML
On Fri, Mar 15, 2013 at 09:58:40PM +0100, Bastien wrote: Rick Frankel r...@rickster.com writes: This should happen in a derived back-end. There are a few Markdown flavours, ox-md.el is only vanilla Markdown. Agreed. Or maybe as a set of filters that people would grab from Worg? It would be good to educate (power-)users about filters, this may be a way to do it. I looked at filters for the slideshow exporters, but my understanding is that they are passed the converted text output, so, in the case of table conversion, the column and row separators would already have been remove by the markdown export function. rick
Re: [O] [PATCH] Fix uncaught error when trying to open a link at point
Hi Samuel, Samuel Loury konubi...@gmail.com writes: Bastien b...@altern.org writes: No problem at all. I decided to go and accept patches from people that did not confirm they got the FSF papers because merging 8.0 into Emacs trunk is not likely to happen to soon... So. Good news, I got the confirmation that my assignment/disclaimer process with the FSF is currently complete. I do not know however if I have to do something to prove that in order to submit patches to this mailing list. Great. Normally I should receive the confirmation myself, I will ping the copyright clerk if I don't receive it in a week or so. I have added you to the list -- welcome! http://orgmode.org/worg/org-contribute.html#contributors_with_fsf_papers I then propose in attachment a set of four tests testing the problem mentioned in this thread: the behavior of org-open-at-point in front of bracket links and plain links. Applied, thanks. PS: The test suite is not (yet) included in GNU Emacs, so there is no need to provide an assignment for this, I will state this in Org's README and in Worg. -- Bastien
Re: [O] A mix of habits and effort estimates?
Dnia 2013-03-16, o godz. 19:23:21 Bastien b...@altern.org napisał(a): Hi Marcin, Marcin Borkowski mb...@wmi.amu.edu.pl writes: Is such a thing possible in Org-mode? Did you check (info (Org)Tracking your habits) ? As I mentioned (though only in the subject), yes. This is close, but my point is not I want to do this at least once each three days or something like this, but rather I want to spend at least 180 minutes every week on this - regardless of days. Of course, I could do it with the habits module (and if there's no other solution, I will do it like this), but what I'd like to have is actually a mixture of habits and effort estimates/clocking. HTH, Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Adam Mickiewicz University
Re: [O] A mix of habits and effort estimates?
Marcin Borkowski mb...@wmi.amu.edu.pl writes: As I mentioned (though only in the subject), yes. This is close, but my point is not I want to do this at least once each three days or something like this, but rather I want to spend at least 180 minutes every week on this - regardless of days. Of course, I could do it with the habits module (and if there's no other solution, I will do it like this), but what I'd like to have is actually a mixture of habits and effort estimates/clocking. Ah, okay. This is not possible for now but maybe you can hack something. -- Bastien
Re: [O] A mix of habits and effort estimates?
Hi Marcin, Marcin Borkowski wrote: Bastien b...@altern.org napisał(a): Marcin Borkowski mb...@wmi.amu.edu.pl writes: Is such a thing possible in Org-mode? Did you check (info (Org)Tracking your habits) ? As I mentioned (though only in the subject), yes. This is close, but my point is not I want to do this at least once each three days or something like this, but rather I want to spend at least 180 minutes every week on this - regardless of days. Of course, I could do it with the habits module (and if there's no other solution, I will do it like this), but what I'd like to have is actually a mixture of habits and effort estimates/clocking. No problem for that. - For the sake of facility, give a unique tag to your educational task - Clock to your task each time you work on it - Whenever you want to check whether you did work enough or not, launch the agenda view for the current week (`v w' in case you say the current day by default) - Ask for the display of the clock report (`C-u R') - Filter on your educational task Have fun! Best regards, Seb -- Sebastien Vauban
[O] Publish to html issue
Dear List, I try to set up a simple org -- html publishing system. If I configure it according to the manual [ http://orgmode.org/org.html#Project-alist]: (setq org-publish-project-alist '((org :base-directory ~/tmp/org/ :publishing-directory ~/tmp/html :section-numbers nil :table-of-contents nil :style link rel=\stylesheet\ href=\../other/mystyle.css\ type=\text/css\/))) I have a following error: org-publish-file: No publishing function chosen OK, so I try to fix it using the configuration posted in the publishing tutorial [ http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.html#text-3-1], namly by providing the publishing-function. (setq org-publish-project-alist '((org :base-directory ~/tmp/org/ :publishing-directory ~/tmp/html :section-numbers nil :table-of-contents nil* :publishing-function org-publish-org-to-html*:style link rel=\stylesheet\ href=\../other/mystyle.css\ type=\text/css\/))) With no luck though: Publishing file /home/igor/tmp/org/remember.org using `org-publish-org-to-html' org-publish-file: Symbol's function definition is void: org-publish-org-to-html On the mail list archives I see some references to the new exporter, unfortunately I'm an org-mode newbie and it does not ring any bells. If this is relevant I can export a single file with a command org-html-export-to-html And my emacs/org versions are: Org http://orgmode.org mode 8.0-pre in Emacshttp://www.gnu.org/software/emacs/ 24.3.50.1. I'm on ubuntu and got my emacs from cassou-emacs-quantal PPA repo, but with the stock 24.2 the issue was the same. I have org mode from el-get, which in turn downloads it from git://orgmode.org/org-mode.git I'd really appreciate your help with this issue. Thanks Cheers, Igor Kupczyński
Re: [O] Publish to html issue
Dear Igor, On Sat, Mar 16, 2013 at 7:12 PM, Igor Kupczyński puszc...@gmail.com wrote: Dear List, I try to set up a simple org -- html publishing system. [snip] (setq org-publish-project-alist '((org :base-directory ~/tmp/org/ :publishing-directory ~/tmp/html :section-numbers nil :table-of-contents nil :publishing-function org-publish-org-to-html :style link rel=\stylesheet\ href=\../other/mystyle.css\ type=\text/css\/))) [snip] Would you please try keeping everything the same except for the following change: :publishing-function org-html-publish-to-html Then (after restart) open one of the *.org files in your ~/tmp/org directory and do the keybinding C-c C-e P p. It should do some thinking and there should be (at least one) *.html file(s) in ~/tmp/html. Also, please see the following information on Worg which has lots of updates/changes that haven't made it to the manual yet: http://orgmode.org/worg/org-8.0.html I hope this helps, -- Jay
Re: [O] [RFC] Org version of the Org manual
Hi Achim,
Achim Gratz strom...@nexgo.de writes:
Hi Tom,
I'm playing around with the current version, here is what I have so far:
The arguments to #+attr_texinfo need to lose the double quotes
Index entries in description lists must be separated from their entry by
at least one blank line like in the example below, otherwise the second
such entry gets indented in the exported .texi file and that somehow
confuses texinfo for some of them.
- {{{kbd(v d)}}} or short {{{kbd(d)}}}, ~org-agenda-day-view~ ::
{{{kindex(v d)}}}
{{{kindex(d)}}}
{{{vindex(org-agenda-span)}}}
With these hanges I get the manual exported correctly to all formats.
Done. Thanks.
I brought the manual up-to-date and used @@info:@@ for the problem macro
characters, so it should be completely converted to Org now.
I want to finish editing the Installation instructions, then tag the
commit to indicate that it is current with org.texi.
Then, unless you think there is more to fix with the conversion, I'll
get down to documenting Nicolas' work according to the instructions he
gave me months ago.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] [RFC] Org version of the Org manual
On 17.3.2013, at 02:19, Thomas S. Dye t...@tsdye.com wrote:
Hi Achim,
Achim Gratz strom...@nexgo.de writes:
Hi Tom,
I'm playing around with the current version, here is what I have so far:
The arguments to #+attr_texinfo need to lose the double quotes
Index entries in description lists must be separated from their entry by
at least one blank line like in the example below, otherwise the second
such entry gets indented in the exported .texi file and that somehow
confuses texinfo for some of them.
- {{{kbd(v d)}}} or short {{{kbd(d)}}}, ~org-agenda-day-view~ ::
{{{kindex(v d)}}}
{{{kindex(d)}}}
{{{vindex(org-agenda-span)}}}
With these hanges I get the manual exported correctly to all formats.
Done. Thanks.
I brought the manual up-to-date and used @@info:@@ for the problem macro
characters, so it should be completely converted to Org now.
I tried the file on github, and export to texinfo fails with the attached
backtrace (exports to other backends as well).
I love this idea, so I really want to try. Any ideas what might be wrong on my
side?
- Carsten
Debugger entered--Lisp error: (error Unknown marker at 281861)
signal(error (Unknown marker at 281861))
error(Unknown marker at %d 281861)
org-element-text-markup-successor(281883)
#[(res) \302\303\304\! !\207 [res limit intern format
org-element-%s-successor] 4](text-markup)
mapcar(#[(res) \302\303\304\! !\207 [res limit intern format
org-element-%s-successor] 4] (export-snippet footnote-reference
inline-babel-call inline-src-block latex-or-entity line-break link macro
radio-target statistics-cookie sub/superscript target text-markup timestamp))
org-element--get-next-object-candidates(281883 (export-snippet
footnote-reference inline-babel-call inline-src-block latex-or-entity
line-break link macro radio-target statistics-cookie sub/superscript target
text-markup timestamp) initial)
byte-code(\306
\n#\211\203\230\307\310\311\312\313\n\\\n\\211A\fV\203$ \314\315
\\210\202\224 Ab\210\316\317\320 @\!
\321 ;\203I \322\323 #\202Q \324 A@ \*
\325 ;\203k \322\323 #\202s \324 A@ \* !\326 ;\203\215 \322\323 #\202\225 \324 A@ \*\211 \\fX\203\340 \U\204\254 \b\210\202\223\314\315 \327
# \211 ;\203\311 \330 \331 #$\202\332 A\332 A@ ##\240\210 +\\210\202\223
\203\363 \fV\204\363 !\fW\203'\314\315 \327
# \211 ;\203\330 \331 #$\202! A\332 A@ ##\240\210 +\\210\202\223
b\210 \327
# \211 ;\203F\330 \331 #$\202W A\332 A@ ##\240\210 +\210 \211 9\203j \202\210 \211 :\204} ;\205\207\333\202\207 @9\205\207 @)$\236A)\334!,)\202
\207 [end restriction candidates closest-cand origin parent
org-element--get-next-object-candidates rassq apply min mapcar cdr throw exit
intern format org-element-%s-parser :contents-begin get-text-property 0
plist-get :contents-end :end :parent org-add-props nil plist-put plain-text
initial object element property cbeg cend obj-end value
org-element-object-restrictions] 8)
org-element-context()
org-macro-replace-all(((modification-time . (eval (format-time-string
\$1\ '(20805 22656 (input-file . om.org) (time . (eval
(format-time-string \$1\))) (property . (eval (org-entry-get nil \$1\
'selective))) (page . @@info:@page@@) (result . @@info:@result{}@@)
(enddefopt . @@info:@end defopt@@) (defopt . @@info:@defopt@@)
(enddefun . @@info:@end defun@@) (defun . @@info:@defun@@) (noindent
. @@info:@noindent@@) (kbdkeys . {{{kbd($1{{{key($2)}}}{{{key($3)}}})}}})
(ksksksksk . {{{kbd($1 {{{key($2)}}} $3 {{{key($4)}}} {{{key($5)}}})}}})
(ksksksk . {{{kbd($1 {{{key($2)}}} $3 {{{key($4)}}})}}}) (kbdspckey .
{{{kbd($1 {{{key($2)}}})}}}) (kbdkey . {{{kbd($1{{{key($2)}}})}}})
(printindex . @@info:@printindex $1@@) (value . {{{markup(value,$1)}}})
(cite . {{{markup(cite,$1)}}}) (var . {{{markup(var,$1)}}}) (file .
{{{markup(file,$1)}}}) (command . {{{markup(command,$1)}}}) (samp .
{{{markup(samp,$1)}}}) (key . {{{markup(key,$1)}}}) (kbd .
{{{markup(kbd,$1)}}}) (markup . @@info:@$1{@@$2@@info:}@@) (kindex .
{{{index(k,$1)}}}) (vindex . {{{index(v,$1)}}}) (findex .
{{{index(f,$1)}}}) (pindex . {{{index(p,$1)}}}) (cindex .
{{{index(c,$1)}}}) (index . @@info:@$1index $2@@)))
org-export-as(texinfo nil nil nil nil)
org-export-to-file(texinfo ./om.texi nil nil nil nil)
org-texinfo-export-to-texinfo(nil nil nil nil)
org-export-dispatch(nil)
call-interactively(org-export-dispatch nil nil)
I want to finish editing the Installation instructions, then tag the
commit to indicate that it is current with org.texi.
Then, unless you think there is more to fix with the conversion, I'll
get down to documenting Nicolas' work according to the instructions he
gave me months ago.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
