emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: emacs-orgmode@gnu.org
Subject: Re: How to change a link?
Date: Wed, 15 Oct 2014 18:17:27 +0200	[thread overview]
Message-ID: <877g01joiw.fsf@wmi.amu.edu.pl> (raw)
In-Reply-To: <87iojlzm4k.fsf@gmail.com>


On 2014-10-15, at 12:02, Thorsten Jolitz wrote:

> Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
>
>> Thanks, but...
>>
>> 1. I have no org-dp-contents function in my Org.  (Org-mode version
>> 8.2.5f (8.2.5f-elpa @ /home/marcin/.emacs.d/elpa/org-20140116/)).
>
> org-dp.el (and org-dp-lib.el) are libraries of mine that aim to make
> local programming with org-elements (org-element-at-point) as convenient
> as global programming (org-element-parse-buffer), see
> https://github.com/tj64/org-dp. I find them very useful, unfortunately
> they have been widely ignored so far ;)

I see.  Unfortunately, I'll ignore them, too, for the simple reason that
I do not want to introduce additional dependencies (and I have to walk
through the whole document anyway).

>> 2. What about internal links like
>>
>> [[My Target][Find my target]]
>>
>> (taken from the manual)?
>>
>> In fact, I don't care about /external/ links at all; I'm /only/
>> interested in links pointing to the file they are in.
>
> This was just an example (using local parsing for convenience), giving
> the hint that you could put some links of interest in an Org file, parse
> it, and look at the (link (:type ...)) alists in the parse tree to see
> the properties you need to get and set. The internal link representation
> is the same for all types anyway.

I see.  What is the most interesting for me is the idea of
getting/setting properties, that's what I was looking for.

Thanks,

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

  reply	other threads:[~2014-10-15 16:17 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 [this message]
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
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=877g01joiw.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).