From: Manish <mailtomanish.sharma@gmail.com>
To: Austin Frank <austin.frank@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: RELEASE: Org-mode 6.08a
Date: Mon, 6 Oct 2008 11:33:55 +0530 [thread overview]
Message-ID: <e7cdbe30810052303w147c5799s83158c17ff73986f@mail.gmail.com> (raw)
In-Reply-To: <m01vyufiwn.fsf@gmail.com>
On Mon, Oct 6, 2008 at 9:56 AM, Austin Frank wrote:
> As always, thanks so much for the hard work! And also to John!
>
> On Sun, Oct 05 2008, Carsten Dominik wrote:
>
>> New attachment system
>> ---------------------
>>
>> You can now attach files to each node in the outline tree. This
>> works by creating special directories based on the ID of an entry,
>> and storing files in these directories. Org can keep track of
>> changes to the attachments by automatically committing changes to
>> git. See the manual for more information.
>>
>> Thanks to John Wiegley who contributed this fantastic new concept
>> and wrote org-attach.el to implement it.
>
> Well! My curiosity's certainly piqued, but I confess that I don't quite
> get the applications here. Any chance Carsten or John would be willing
> to let us know how they're using this?
Let me take a stab at it.
1. Create a test file. test.org
2. Add a task to it.
3. Do `C-c C-a' while on the task.
4. Press `a' from the launcher menu to add an attachment.
5. Select a file to be attached to it (somewhere in a subdirectory
named data where org files are contained (careful, it will /move/
the file, not copy it.)
6. Attach another file to it using #3-5 (or use `c'.)
7. Press `C-c C-a' followed by `o' to open an attachment from the
options.
I am sure there's more to it but this was enough for me to be
convinced of it's utility. I just wish that:
1. it copied attachemnts instead of moving them (may be an option),
and
2. there was another option to archive the attachment directory from
the launcher menu itself (a `Z' for zip, just like there is `D' for
deletion.)
>
> Also, the synopsis above and the manual both mention git integration,
> but I don't understand what exactly is done. It sounds like if the org
> file lives in a directory that is a git repo, any additions or changes
> to the files in the auto-generated data/ subdirectory are automatically
> committed? Is this the right idea? What does the synchronize command
> do if the directory isn't a git repo?
If the directory where attchments are kept/maintained (not the Org
files themselves) is turned into a git repo, then org-attach.el will
automatically commit changes to it.
>
> I am thrilled to see a move towards some nice defaults for org and git
> integration. I see that in org-attach.el you're using shell-command to
> call git directly. If you don't mind, may I ask if you considered using
> git.el that is distributed with git (in contrib/emacs/), or even magit
> (http://zagadka.vm.bytemark.co.uk/magit/)?
I am not sure but I think git.el and magit.el etc. make it easier for
the end-user to interact with git but org-attach.el just needs to
execute add and commit on the git repo so an additional dependency can
be avoided.
As always, thank you Carsten and John for the amazing amazing
software.
-- Manish
next prev parent reply other threads:[~2008-10-06 6:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 6:40 RELEASE: Org-mode 6.08a Carsten Dominik
2008-10-05 21:18 ` William Henney
[not found] ` <08B4A2E6-A2DF-4AA6-815D-CBE0F708EDE7@uva.nl>
2008-10-06 0:29 ` William Henney
2008-10-06 2:21 ` Manish
2008-10-06 2:39 ` William Henney
2008-10-06 4:26 ` Austin Frank
2008-10-06 6:03 ` Manish [this message]
2008-10-06 8:47 ` Alan E. Davis
2008-10-06 17:15 ` Carsten Dominik
2008-10-07 9:36 ` Samuel Wales
2008-10-07 11:05 ` Carsten Dominik
2008-10-08 10:51 ` Carsten Dominik
2008-10-08 11:43 ` Manish
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=e7cdbe30810052303w147c5799s83158c17ff73986f@mail.gmail.com \
--to=mailtomanish.sharma@gmail.com \
--cc=austin.frank@gmail.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).