Nicolas Goaziou writes:
> I think Org ELPA's release is updated at least every week.
The last update was published with a wrong version number (that package
manager will not consider as an update) and no further updates will be
published at all I suspect unless the version header in org.el gets
p
Sergei Nosov writes:
> 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.
fuzzy are for text search, targets and NAME keywords. I'm not sure what
was the exact definition o
> 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.
Sergei Nosov 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" .
Great! Thanks!
2 questions, though.
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 ("thisfi
Bastien writes:
> Nicolas Goaziou writes:
>
>> I think `org-translate-link' should be updated to provide correct type,
>> including internal ones, to `org-link-translation-function'. E.g.,
>>
>> http://orgmode.org => "http"
>> #something => "custom-id"
>> (ref:line) => "cod
Nicolas Goaziou writes:
> I think `org-translate-link' should be updated to provide correct type,
> including internal ones, to `org-link-translation-function'. E.g.,
>
> http://orgmode.org => "http"
> #something => "custom-id"
> (ref:line) => "coderef"
> whatever
> wild guess: what if you simply make the ":" optional like this:
I believe, the preceding text should be made optional as well (i.e. +
should be *, like (string-match "\\([a-zA-Z0-9]*\\):?\\(.*\\)" s))
But anyway, it doesn't seem to work, because for some reason (I just
noticed this) - the org-t
Hello,
Bastien writes:
> Hi Sergei,
>
> wild guess: what if you simply make the ":" optional like this:
>
> (string-match "\\([a-zA-Z0-9]+\\):\\(.*\\)" s)
>
> (string-match "\\([a-zA-Z0-9]+\\):?\\(.*\\)" s)
> ^^^
>
> ?
I think `org-translate-link' should be upda
Hi Sergei,
wild guess: what if you simply make the ":" optional like this:
(string-match "\\([a-zA-Z0-9]+\\):\\(.*\\)" s)
(string-match "\\([a-zA-Z0-9]+\\):?\\(.*\\)" s)
^^^
?
--
Bastien
10 matches
Mail list logo
