emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jason Guiditta <jason.guiditta@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Multiple files and auto-updating
Date: Mon, 12 Jul 2010 14:41:23 -0400	[thread overview]
Message-ID: <AANLkTinJXr-zW5V5w0EsjI6PO1L_OK8DxypKVTqMjPOy@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1969 bytes --]

Hello, apologies if these questions are documented somewhere (in fact, I bet
they are, just haven't been able to find them).  I am a newcomer to both
orgmode and emacs in general, so I am still on the steep side of the
learning curve.  I have spent several days poking around the documentation,
watching some screencasts, looking at gmane, etc with no success solving my
issue, so I hope someone can point me in the right direction.

The group I work with is using orgmode to track tasks for our projects.
This is currently in one big file (with various tags) that has at the bottom
a dynamic table that we periodically export to html and put up on a server
for easier viewing of the current state of tasks.  We store this project
file in a git repo.  I have been asked to do two major things and two minor
(at least in importance) things to streamline this.

== Major ==
1. Move this dynamic table out into its own file to reduce the size of the
main project file (I am not the only one in the group not that familiar with
emacs --yet).
2. Have this table be updated/exported automatically when saving the project
file.

From what I have seen, dynamic tables are meant to just be another view of
the data in a given file, so I am wondering if this is even the right
approach.  The update/export seems likely to be some org-mode post-save
command.  If this is the case, guess I'll have to figure out how to write
some elisp  :-/

== Minor ==
1. After automatically updating/exporting the table file, upload that to our
server as well.
2. Commit the file to git from the buffer (pretty sure this is just a matter
of using the git mode I have seen mentioned, but thought I'd throw it out
there in case there is another suggestion).

Hopefully these questions are reasonable and I haven't missed obvious
directions on how to do these things.  I appreciate any assistance from
members of the list.  (Also, really liking orgmode/emacs in general so far,
fwiw).

Thanks,

-j

[-- Attachment #1.2: Type: text/html, Size: 2068 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

             reply	other threads:[~2010-07-12 18:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-12 18:41 Jason Guiditta [this message]
2010-07-14 20:30 ` Multiple files and auto-updating Carsten Dominik
2010-07-14 21:02   ` Jason Guiditta

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=AANLkTinJXr-zW5V5w0EsjI6PO1L_OK8DxypKVTqMjPOy@mail.gmail.com \
    --to=jason.guiditta@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).