Re: [O] [bug] Export to FreeMind (HTML) fails due to ampersant in URL

2015-02-08 Thread Karl Voit
* Nicolas Goaziou wrote: > Achim Gratz writes: > >> Nicolas Goaziou writes: >>> This looks like valid HTML code to me. Also it exports fine to HTML. Is >>> there any restriction related to this specific to FreeMind? >> >> Valid HTML, maybe (I've not checked). Valid XML, no. >> http://freemind.so

[O] Simple in-buffer links?

2015-02-08 Thread Lawrence Bottorff
I'm a beginner and I can't figure out how to build a simple link. All I want to do is have numbered footnotes throughout my org file that, when clicked, jump down to that footnote. Eg: -- This is in my org file and I'm describing Emacs fill (1). You can also do auto-fill (2) . . . (1) A fill

Re: [O] [patch] Formatting of {{{DATE}}}

2015-02-08 Thread Rasmus
Hi Nicolas, Thanks for the tips. Pushed as 8f38f03. I added a org-NEWS entry, but I don't know if it should be there. Feel free to let me know or remove it yourself if it shouldn't. BTW: when figuring out how the heck macros works I came across two other undocumented macros, namely {{{input-fi

Re: [O] [patch] Formatting of {{{DATE}}}

2015-02-08 Thread Nicolas Goaziou
Correcting myself, Nicolas Goaziou writes: > I suggest > > (cons "date" > (format > "(eval (if (org-string-nw-p \"$1\") %s %S))" > "(org-export-get-date info \"$1\")" > (or (org-element-interpret-data (plist-get info :date)) > ""))) Please scrat

Re: [O] [patch] Formatting of {{{DATE}}}

2015-02-08 Thread Nicolas Goaziou
Hello, Rasmus writes: > I'd quite like to be able to pass a formatting argument to {{{date}}}, > much like {{{time(FMT)}}}. This patch allows this. I think macros don't > normally have optional arguments, but I find it OK here since it's time > and modification-time works anyway... > > On the

Re: [O] Citations, continued

2015-02-08 Thread Thomas S. Dye
Aloha all, I'm having a hard time relating the various syntax proposals to a common, shared goal for Org mode users. This might just be me--I often struggle to understand conversations on the Org mode list. However, I'm also convinced that lack of clearly shared goals really gets in the way of p

[O] [patch] Formatting of {{{DATE}}}

2015-02-08 Thread Rasmus
Hi, I'd quite like to be able to pass a formatting argument to {{{date}}}, much like {{{time(FMT)}}}. This patch allows this. I think macros don't normally have optional arguments, but I find it OK here since it's time and modification-time works anyway... On the other hand there might be a goo

Re: [O] [Patch] Fix date-based sorting of tags and tags-todo agenda views

2015-02-08 Thread Nicolas Goaziou
y...@mit.edu (Yuri D. Lensky) writes: > Done. Thank you. However, you didn't tell me your status wrt FSF assignment (or forgot the TINYCHANGE part in your commit message). > +(defun org-agenda-entry-get-agenda-timestamp (pom) > + "Given a point or maker POM, returns a cons cell of the > +times

Re: [O] [Patch] Fix date-based sorting of tags and tags-todo agenda views

2015-02-08 Thread Yuri D. Lensky
Done. >From 131435ac43d950bad2bb42b92982f498de74a31f Mon Sep 17 00:00:00 2001 From: "Yuri D. Lensky" Date: Sat, 7 Feb 2015 13:37:46 -0500 Subject: [PATCH] Fix timestamp-based sorting of tags-based entries in agenda * lisp/org.el (org-scan-tags): Fix agenda org tags scans to properly add timest

Re: [O] Citations, continued

2015-02-08 Thread Nicolas Goaziou
Richard Lawrence writes: > But doesn't the first case pose the same performance problems as the > Pandoc syntax, since it does away with the tag? Or are you thinking > it's easier to parse because the key occurs immediately after the > bracket, without a prefix...? Correct. It is easier to dism

Re: [O] Citations, continued

2015-02-08 Thread Rasmus
Nicolas Goaziou writes: > Rasmus writes: > >> PS: Here's a quick link "proof-of-concept" (not really) with biblatex >> only, and cite it textcitation. Documents with this type of syntax are >> indeed pleasant to the eye. >> >> [[cite: pre1 @bohringer14 post1; pre2 @davis14 post2]] > > As pointe

Re: [O] Citations, continued

2015-02-08 Thread Richard Lawrence
Hi Nicolas and all, On Sun, Feb 8, 2015 at 1:58 AM, Nicolas Goaziou wrote: > > - in-text citation > > [KEY] or [KEY suffix] > > [@item1] or [@item1 p. 30] or [@item1 p. 30, with suffix] > > - out-text citation > > [cite: prefix? key suffix?; prefix2? key2 suffix2? ...] > >

Re: [O] Citations, continued

2015-02-08 Thread Richard Lawrence
Hi John and all, On Sun, Feb 8, 2015 at 1:46 AM, John Kitchin wrote: > My only concern is that it remains possible to support this relatively > full set of citation options on export: > ... > which we are currently able to do. I never type any of those in, org-ref > does it automatically from a k

Re: [O] Citations, continued

2015-02-08 Thread Nicolas Goaziou
Rasmus writes: > PS: Here's a quick link "proof-of-concept" (not really) with biblatex > only, and cite it textcitation. Documents with this type of syntax are > indeed pleasant to the eye. > > [[cite: pre1 @bohringer14 post1; pre2 @davis14 post2]] As pointed out already, the double square brac

Re: [O] Citations, continued

2015-02-08 Thread Nicolas Goaziou
Rasmus writes: > In that case I prefer the explicit extraction of keys below, since I don't > understand why [-@k1] is invalid ("in her seminal -@k @k:journal article, > @k:author demonstrated that ⋯"). Probably I don't understand pandoc well > enough... In the initial suggestion @k:journal or

[O] HTML export should leave IRIs as is

2015-02-08 Thread Vladimir Alexiev
I have this in a file: - [[https://chrome.google.com/webstore/detail/copy-url/mkhnbhdofgaendegcgbmndipmijhbili][CopyURL]] Chrome Plugin - Many URLs in dbpedia are International Resource Identifiers (IRIs) - When you copy from the browser's address bar, an IRI is URL-encoded - Unreadable ug

Re: [O] Citations, continued

2015-02-08 Thread Rasmus
Nicolas Goaziou writes: >> Another issue is that it's not transpose-words safe. E.g. this output >> seems bad: [-@k1 @k2 30] => Y1 A2 (Y2, 30). > > This citation is invalid. The point of [@k1] is that the author is > mandatory, since it is in-text, so [-@k1] doesn't make sense. In that case I

Re: [O] Citations, continued

2015-02-08 Thread Nicolas Goaziou
Rasmus writes: 2. [cite:@item1: p. 30] says blah. ... 2. Doe (2005, 30) says blah. ^^^ According to Erik, this is just a possible output. It belongs to export configuration. 3. [cite:@item1: p. 30, with suffix] says blah. 4.

Re: [O] Citations, continued

2015-02-08 Thread Rasmus
Hi, Thanks for the quick reply. A very colorful (in Gnus at least) reply follows. >>> 1. [cite:@item1] says blah. >>> 2. [cite:@item1: p. 30] says blah. >> >> Why is "p." stripped here? > > I don't understand. Anyway, I now suggest This is what I'm talking about: >>> 2. [cite:@item1: p. 3

Re: [O] Citations, continued

2015-02-08 Thread Nicolas Goaziou
Rasmus writes: > Nicolas Goaziou writes: > >> Using the example from Erik Hetzner in the same thread, what about: >> >> 1. [cite:@item1] says blah. >> 2. [cite:@item1: p. 30] says blah. > > Why is "p." stripped here? I don't understand. Anyway, I now suggest [@item1] and [@item1 p. 30]

Re: [O] Citations, continued

2015-02-08 Thread Nicolas Goaziou
Richard Lawrence writes: > On Sat, Feb 7, 2015 at 2:43 PM, Nicolas Goaziou > wrote: > >> What about the following set? >> >> bold code entity italic latex-fragment line-break strike-through >> subscript superscript underline superscript > > That would work fine for me in prefixes and suffixes

Re: [O] Citations, continued

2015-02-08 Thread John Kitchin
My only concern is that it remains possible to support this relatively full set of citation options on export: (defcustom org-ref-cite-types '("cite" "nocite" ;; the default latex cite commands ;; natbib cite commands, http://ctan.unixbrain.com/macros/latex/contrib/natbib/natnotes.pdf "

Re: [O] Citations, continued

2015-02-08 Thread Rasmus
Nicolas Goaziou writes: > Using the example from Erik Hetzner in the same thread, what about: > > 1. [cite:@item1] says blah. > 2. [cite:@item1: p. 30] says blah. Why is "p." stripped here? > 3. [cite:@item1: p. 30, with suffix] says blah. > 4. [cite:@item1: -@item2 p. 30; see also @ite

Re: [O] How do you structure your org-drill file?

2015-02-08 Thread Bernhard Pröll
Dear Marcin, with org-drill-hide-item-headings-p set to t the heading text is irrelevant to me. I use this capture template: ("v" "Vocabulary Item" entry (file "~/path/to/vocabulary.org") "* Drill :drill:\n:PROPERTIES:\n:DRILL_CARD_TYPE: twosided\n:END:\n** Item\n%^{New Item