emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: org-mode List <emacs-orgmode@gnu.org>
Subject: Re: How to change a link?
Date: Wed, 15 Oct 2014 23:30:11 +0200	[thread overview]
Message-ID: <87tx35hvh8.fsf@wmi.amu.edu.pl> (raw)
In-Reply-To: <87bnpd4ov7.fsf@nicolasgoaziou.fr>


On 2014-10-15, at 12:19, Nicolas Goaziou wrote:

> Hello,
>
> Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
>
>> assume that I have a link object (e.g., I'm in the ellipsis part of
>> this:
>>
>> (org-element-map (org-element-parse-buffer 'object) 'link
>>   (lambda (elt) ... ))
>>
>> What I want to do is this:
>> 1. check whether it is an internal link, and
>
> (member (org-element-property :type elt) '("custom-id" "fuzzy"))
>
>> 2. if it is, change it so that it points to the analogous place in
>> another file.
>
>   (org-element-put-property elt :raw-link
>                             (concat "file:path/to/other-file.org::"
>                                     (org-element-property :path elt)))

Thanks a lot, that was helpful!  I'm starting to feel more and more
confident with org-element-whatever, that's good.

I have one more question.  What I'm about to do is (basically) put
"file:some-file-name::" in front of the link, without changing the
description.  I could use `org-element-put-property' and (AFAIU)
org-element-link-interpreter to put it into the buffer (and probably
delete the old one).  It would be much easier (and maybe faster) just to
go to the point in the buffer where the link starts, go `(forward-char
2)' (past the brackets) and `(insert (concat "file" name "::"))'.

But, is it safe?  Wouldn't it break something?  And is it considered a
good practice?

Regards,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University

  reply	other threads:[~2014-10-15 21:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15  0:19 How to change a link? Marcin Borkowski
2014-10-15  7:16 ` Thorsten Jolitz
2014-10-15  9:50   ` Marcin Borkowski
2014-10-15 10:02     ` Thorsten Jolitz
2014-10-15 16:17       ` Marcin Borkowski
2014-10-15 22:28         ` Thorsten Jolitz
2014-10-15 22:36           ` Marcin Borkowski
2014-10-15 22:51             ` Thorsten Jolitz
2014-10-15 23:06               ` Thorsten Jolitz
2014-10-15 10:19 ` Nicolas Goaziou
2014-10-15 21:30   ` Marcin Borkowski [this message]
2014-10-15 21:52     ` Nicolas Goaziou
2014-10-16 17:55       ` Marcin Borkowski
2014-10-16 20:10         ` Nicolas Goaziou
2014-10-16 21:46           ` Marcin Borkowski
2014-10-16 22:19         ` Thorsten Jolitz
2014-10-17  8:52           ` Marcin Borkowski
2014-10-17 15:25             ` Nick Dokos
2014-10-18 13:54               ` Thorsten Jolitz
2014-10-18  1:44           ` Marcin Borkowski
2014-10-18 13:48             ` Thorsten Jolitz
2014-10-20  0:02   ` Marcin Borkowski
2014-10-20 13:02     ` Nicolas Goaziou
2014-10-20 13:11       ` Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tx35hvh8.fsf@wmi.amu.edu.pl \
    --to=mbork@wmi.amu.edu.pl \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).