> What doesn't work? I.e., what is produced and what did you expect instead? The jump via C-c C-o didn't work for me. But I figured it out in a meanwhile - supposedly, what was previously called "thisfile" link type is now called "fuzzy". Thanks.
> IIUC MELPAe they should already be available. Sorry, I meant, Org ELPA (http://orgmode.org/elpa/) not MELPA (org is not published on MELPA at all). The last published package seem to be http://orgmode.org/elpa/org-20150817.tar which doesn't contain the fix. So, my question is - when the next package (that contains the fix) will be published? Or, alternatively, what's the Org policy for publishing new packages to ELPA? -- Best regards, Sergei Nosov On Fri, Aug 21, 2015 at 3:11 PM, Nicolas Goaziou <m...@nicolasgoaziou.fr> wrote: > Sergei Nosov <sergei.no...@gmail.com> writes: > > > 1. Previously, the type of the link was "thisfile", now it's "custom-id" > > and also, the leading hash is removed from the link. Let's consider > > the [[#about][About]] > > example once again. Previously, I was given ("thisfile" . "#about") and I > > changed this to ("thisfile" . "About"), which then worked like a charm. > > Now, I'm given ("custom-id" . "about"), which I don't know how I should > > translate. Neither of ("custom-id" . "About") or ("id" . "About") work. > > What should it be? > > What doesn't work? I.e., what is produced and what did you expect > instead? > > > BTW, there's a line (require 'ord-id) in org-open-at-point function in > > master. Probably, it's a typo (should be (require 'org-id)) > > Fixed. Thank you. > > > 2. When those fixes will be available in MELPA? > > IIUC MELPAe they should already be available. > > > Regards, >
