From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Samuel Wales" Subject: Re: Re: RELEASE: Org-mode 6.08a Date: Tue, 7 Oct 2008 02:36:11 -0700 Message-ID: <20524da70810070236k1fb60226jb82d024417b224af@mail.gmail.com> References: <98C068B3-0930-444E-A17B-E01D3E583BCA@uva.nl> <39130699-960D-4896-A27D-1161618A73F6@uva.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Kn8zH-0002Cu-Es for emacs-orgmode@gnu.org; Tue, 07 Oct 2008 05:36:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Kn8zF-0002BR-S4 for emacs-orgmode@gnu.org; Tue, 07 Oct 2008 05:36:14 -0400 Received: from [199.232.76.173] (port=37401 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kn8zF-0002BG-B8 for emacs-orgmode@gnu.org; Tue, 07 Oct 2008 05:36:13 -0400 Received: from nf-out-0910.google.com ([64.233.182.191]:33364) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Kn8zE-0004hW-Np for emacs-orgmode@gnu.org; Tue, 07 Oct 2008 05:36:13 -0400 Received: by nf-out-0910.google.com with SMTP id c7so1307275nfi.26 for ; Tue, 07 Oct 2008 02:36:11 -0700 (PDT) In-Reply-To: <39130699-960D-4896-A27D-1161618A73F6@uva.nl> Content-Disposition: inline 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: Carsten Dominik Cc: emacs-orgmode@gnu.org Comments on the interesting attachment feature. 1. This function needs "(interactive)", i think. (defun org-attach-open-in-emacs () "Open attachment, force opening in Emacs. See `org-attach-open'." (org-attach-open 'in-emacs)) 2. This is trivial to rebind, but my guess is that emacs types would prefer to open things in emacs using the nonshifted keys. e.g. dired instead of file browser, emacs instead of text editor. 3. I'm getting the idea that the attachment system is partly to avoid linking files? This is good because links are easy to break. The key is to have a directory that is only for org, and to use the filesystem to identify the attachments. Then there is no broken link to a file. I like the idea. The current implementation explicitly lists the attachments. Perhaps they could be retrieved from the dir? 4. Another possibility, if we have a directory dedicated to a node, might be to inline the files under the node. Each subnode would be the name of a file in the dir associated with the node. The contents of the subnode are the contents of the file. Then any editing of a headline would change the filename, and any editing of the contents would change the file contents. Searching would find things in the contents. Yet data are only stored in the files themselves, not in the org file. For what it's worth.