emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bastien <bastienguerry@googlemail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode meets git a first proposal ?!
Date: Mon, 3 Aug 2009 06:39:31 +0200	[thread overview]
Message-ID: <802D4B50-758E-4BDB-8FAD-1D59F1055F78@gmail.com> (raw)
In-Reply-To: <87tz0zuqid.fsf@bzg.ath.cx>


On Jul 26, 2009, at 10:40 PM, Bastien wrote:

> Hi Totti,
>
> just a few words regarding preserving links.
>
> About /finding/ links, I just added this simple function, which is
> quite handy I guess:
>
>
> (defun org-occur-link-in-agenda-files ()
>  "Create a link and search for it in the agendas.
> The link is not stored in `org-stored-links', it is just created
> for the search purpose."
>  (interactive)
>  (let ((link (condition-case nil
> 		  (org-store-link nil)
> 		(error "Unable to create a link from here"))))
>    (org-occur-in-agenda-files (regexp-quote link))))

Nice one! I have added a menu entry for it.

>
>
> For example, you are in your mailbox, you have the nasty feeling that
> this old mail you are re-reading has been stored in your agenda, this
> function helps you find it.
>
> About preserving links -- yes, this is a problem.  I tried to  
> implement
> a registry long time ago: this is org-registry.el in the contrib/ dir.
> Please have a look.  I don't maintain it anymore, but it might be  
> still
> usable.  If people are interested in using it more, I will look at it
> again.
>
> Another simple and useful approach: I often break links by moving a  
> file
> from dired.  A solution could be to advise dired-do-rename so that it
> checks whether the file(s) at point is/are link(s) in an org file.  If
> so, the function could just send a warning, and maybe update the  
> links.
> That would be a beginning.  Of course, this doesn't fix the problem
> when moving files from the shell...

Please also consider using ID links which are made to survive
when files are moved around.  As long as the link definition remains
in one of the agenda files, the links will still work.

- Carsten

>
> As for linking to specific versions of a file under versioning, I have
> a few ideas I'm working on, I let you know later.
>
> Thanks!
>
> -- 
> Bastien
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

      reply	other threads:[~2009-08-03  4:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24  3:32 org-mode meets git a first proposal ?! Torsten Wagner
2009-07-24  5:18 ` Matthew Lundin
2009-07-24 13:17   ` Jason F. McBrayer
2009-07-24 15:35     ` Torsten Wagner
2009-07-24 15:32   ` Torsten Wagner
2009-07-26 20:40 ` Bastien
2009-08-03  4:39   ` Carsten Dominik [this message]

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=802D4B50-758E-4BDB-8FAD-1D59F1055F78@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=bastienguerry@googlemail.com \
    --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).