From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Org Radio Date: Sat, 29 Dec 2007 14:01:20 +0100 Message-ID: <87abntsli7.fsf@bzg.ath.cx> References: <64bfe3d50712170623w6ba3af0fifc37398250b492f1@mail.gmail.com> <87odci4la9.fsf@bzg.ath.cx> <20071224.110121.138697347.dto@pod.lab> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J8bJd-0005mJ-Eg for emacs-orgmode@gnu.org; Sat, 29 Dec 2007 08:01:25 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J8bJc-0005lS-Qc for emacs-orgmode@gnu.org; Sat, 29 Dec 2007 08:01:25 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J8bJc-0005lG-L6 for emacs-orgmode@gnu.org; Sat, 29 Dec 2007 08:01:24 -0500 Received: from fg-out-1718.google.com ([72.14.220.156]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J8bJc-0008Vw-Ai for emacs-orgmode@gnu.org; Sat, 29 Dec 2007 08:01:24 -0500 Received: by fg-out-1718.google.com with SMTP id d23so2436114fga.30 for ; Sat, 29 Dec 2007 05:01:23 -0800 (PST) In-Reply-To: <20071224.110121.138697347.dto@pod.lab> (David O'Toole's message of "Mon, 24 Dec 2007 11:01:21 -0500 (EST)") 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: David O'Toole Cc: emacs-orgmode@gnu.org David O'Toole writes: > 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 Of course, you're right. Maybe the easy solution would be to implement two ways of annotating: region-wise or pseudomarker-wise. You would annotate regions in files that are not supposed to change (e.g. pdftotext'ed text files) and you would "insert" annotations in texts that are likely to change. The process I have in mind for first kind of annotations is something like this: 1. you're in your text buffer (file.txt) 2. M-x org-remember 3. Use a template that knows about the filename and the region When you open file.txt, you can turn org-annotation-minor-mode on, and *see* whether the text is annotated. The minor-mode would do this: 1. fetch annotations in files that are reached by M-x org-remember 2. put an overlay on these regions (if a region is annotated twice, show this by modifying the overlay - maybe different colors) What do you think? > But maybe I am missing an obvious solution---can you give more details > on the GPLv3 thing you are referring to? See this: http://gplv3.fsf.org/comments/gfdl-draft-1.html As you can see, commented regions get colored. More commented ones are darker. It would be *really* nice if we could implement something like this in Emacs, with Org. The one thing I currently miss in Emacs is the ability to annotate a file and directly see those annotations in the buffer. -- Bastien