From mboxrd@z Thu Jan 1 00:00:00 1970 From: David O'Toole Subject: Re: Org Radio Date: Mon, 24 Dec 2007 11:01:21 -0500 (EST) Message-ID: <20071224.110121.138697347.dto@pod.lab> References: <64bfe3d50712170623w6ba3af0fifc37398250b492f1@mail.gmail.com> <87odci4la9.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J6pmB-00018j-F9 for emacs-orgmode@gnu.org; Mon, 24 Dec 2007 11:03:35 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J6pm0-00015W-WC for emacs-orgmode@gnu.org; Mon, 24 Dec 2007 11:03:34 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J6pm0-00015T-TN for emacs-orgmode@gnu.org; Mon, 24 Dec 2007 11:03:24 -0500 Received: from py-out-1112.google.com ([64.233.166.177]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J6plu-0006lJ-PJ for emacs-orgmode@gnu.org; Mon, 24 Dec 2007 11:03:24 -0500 Received: by py-out-1112.google.com with SMTP id a73so3530504pye.14 for ; Mon, 24 Dec 2007 08:01:31 -0800 (PST) In-Reply-To: <87odci4la9.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: bzg@altern.org Cc: emacs-orgmode@gnu.org, dto@gnu.org Hello Bastien, I really like the region idea. However it could be very tricky to implement. The annotations in the radio file would be matched to regions in the target file. So presumably we save the region's coordinates in the radio file along with its annotation. We can use markers and overlay properties to keep these data consistent in the face of changes that happen in an Emacs buffer, but if a file can change outside Emacs (i.e. annotating a shared file in version control) then we have a problem, because (in the new model you are suggesting) there was never anything in the file itself to indicate which regions go with which annotations. That model is interesting because it means you can annotate files without changing them (i.e. notes on /etc). But I don't see how to keep the radio file from breaking. But maybe I am missing an obvious solution---can you give more details on the GPLv3 thing you are referring to? --dave From: Bastien Subject: Re: [Orgmode] Org Radio Date: Sat, 22 Dec 2007 19:49:34 +0100 > Hi David, > > "David O'Toole" writes: > > > I'm writing an add-on for Org (again!) > > > > This one is called radio.el. It lets you annotate files (or even > > individual lines within files) with arbitrary org subtrees. > > Great! I played with it a bit, and I like the general idea. I thought > about doing something similar a while ago, because the one thing I lack > in Emacs is the ability to take notes against one particular file and to > see from within the file if there are notes attached to it... > > Maybe one direction for further improvements: I don't really like the > glyph ":>". I would prefer that taking notes is done against a region > and that the whole region get overlayed when you activate radio-mode (or > whatever mode it could be.) > > Remember the GPLv3 comment process and the way comments were overlined. > Turning your mode on could overline regions that are annotated, and > those overlined regions could link to the note in the attached Org > file... > > Does this fit with your use of the tool ? > > -- > Bastien