stardiviner writes:
> After finished this upgrading, I will write a blog post about this for
> helping user migration.
As I said, I wrote a simple blog post about how to upgrade to new link syntax.
https://stardiviner.github.io/Blog/upgrade-Org-link-syntax-to-new.html
--
[ stardiviner ]
Hello,
stardiviner writes:
> I found a simple and better solution to replace those. I use =rg (ripgrep)= to
> search you mentioned escape characters "%20 %25 %5B %5D". I then use =wgrep=
> on
> results. I spend pretty long time to processing all links. There are about
> 4
> links matched.
Nicolas Goaziou writes:
> stardiviner writes:
>
>> Hi, @Nicolas, will you release a method to update all existing Org
>> file links?
>
> On second though, you may want to test the following:
>
> (defun org-update-link-syntax ()
> "Update syntax for links in current buffer."
>
Nicolas Goaziou writes:
> stardiviner writes:
>
>> Hi, @Nicolas, will you release a method to update all existing Org
>> file links?
>
> On second though, you may want to test the following:
>
> (defun org-update-link-syntax ()
> "Update syntax for links in current buffer."
>
Nicolas Goaziou writes:
> Hello,
>
> stardiviner writes:
>
>> So I have to consider a safer and larger method to upgrade link. I can't
>> manually open every Org files and run linter on them.
>
> I already offered a function for replacing it in a file. You can wrap it
> within a `dolist' on
Hello,
stardiviner writes:
> So I have to consider a safer and larger method to upgrade link. I can't
> manually open every Org files and run linter on them.
I already offered a function for replacing it in a file. You can wrap it
within a `dolist' on `directory-files-recursively'.
> (Maybe
Nicolas Goaziou writes:
> Hello,
>
> stardiviner writes:
>
>> Hi, @Nicolas, will you release a method to update all existing Org
>> file links?
>
> This is not limited to file links.
>
> There is no method that can, with certainty, convert old syntax into the
> new one. More accurately, it is
Hello,
stardiviner writes:
> Hi, @Nicolas, will you release a method to update all existing Org
> file links?
This is not limited to file links.
There is no method that can, with certainty, convert old syntax into the
new one. More accurately, it is possible to convert them with:
stardiviner writes:
> Hi, @Nicolas, will you release a method to update all existing Org
> file links?
On second though, you may want to test the following:
(defun org-update-link-syntax ()
"Update syntax for links in current buffer."
(org-with-point-at 1
(let
Nicolas Goaziou writes:
> Hello,
>
> I finally pushed changed about escape syntax in bracket links. Here is
> the excerpt from ORG-NEWS:
>
> Org used to percent-encode sensitive characters in the URI part of the
> bracket links.
>
> Now, escaping mechanism uses the usual backslash
Hello,
Amin Bandali writes:
> On 2019-03-10 1:02 PM, Samuel Wales wrote:
>> the org capture firefox extensions, and similar extensions, or
>> org-protocol, might need changing.
>>
>>
>
> [...]
>
> Also seems like there are a couple more internal Org functions that need
> changing: when opening
Thanks! It works again :)
On Tue, Mar 12, 2019 at 12:07 AM Nicolas Goaziou
wrote:
> Hello,
>
> Diego Zamboni writes:
>
> > I can confirm this behavior. After updating to latest org from master and
> > restarting Emacs, my documents now show the link destinations instead of
> > their
Hello,
Diego Zamboni writes:
> I can confirm this behavior. After updating to latest org from master and
> restarting Emacs, my documents now show the link destinations instead of
> their descriptions (nothing changed in my configuration).
>
> Best,
> --Diego
>
>
> On Mon, Mar 11, 2019 at 6:52
I can confirm this behavior. After updating to latest org from master and
restarting Emacs, my documents now show the link destinations instead of
their descriptions (nothing changed in my configuration).
Best,
--Diego
On Mon, Mar 11, 2019 at 6:52 PM Marco Wahl wrote:
> Hi Nicolas and all,
>
Hi Nicolas and all,
Is it just me or does
[[https://duckduckgo.com][DDG]]
show up now as
https://duckduckgo.com
with `org-link-descriptive' set to t?
I would instead expect
DDG
to appear. Wild guess: this is an issue in `org-activate-links'?
Ciao
--
Marco
On 11-03-2019 10:35, Nicolas Goaziou wrote:
> Hello,
>
> Daniele Nicolodi writes:
>
>> On 10/03/2019 11:19, Nicolas Goaziou wrote:
>>> When in doubt, use the function ~org-link-escape~ in order to turn
>>> a link string into its properly escaped form.
>>>
>>> The old
Hello Nicolas,
With the new syntax, are link descriptions meant to be displayed instead
of the actual links? I only seem to have the actual links
displayed. Have I missed some setting?
Thanks,
eric
--
Eric S Fraga via Emacs 27.0.50, Org release_9.2.2-286-gc020e9
Hello,
Daniele Nicolodi writes:
> On 10/03/2019 11:19, Nicolas Goaziou wrote:
>> When in doubt, use the function ~org-link-escape~ in order to turn
>> a link string into its properly escaped form.
>>
>> The old ~org-link-escape~ and ~org-link-unescape~ functions have
>> been
On 10/03/2019 11:19, Nicolas Goaziou wrote:
> When in doubt, use the function ~org-link-escape~ in order to turn
> a link string into its properly escaped form.
>
> The old ~org-link-escape~ and ~org-link-unescape~ functions have
> been renamed into ~org-link-encode~ and
On 2019-03-10 1:02 PM, Samuel Wales wrote:
> the org capture firefox extensions, and similar extensions, or
> org-protocol, might need changing.
>
>
[...]
Also seems like there are a couple more internal Org functions that need
changing: when opening a new empty org file using latest Org
the org capture firefox extensions, and similar extensions, or
org-protocol, might need changing.
On 3/10/19, Nicolas Goaziou wrote:
> Hello,
>
> I finally pushed changed about escape syntax in bracket links. Here is
> the excerpt from ORG-NEWS:
>
> Org used to percent-encode sensitive
21 matches
Mail list logo
