From: Ista Zahn <istazahn@gmail.com>
To: Michael Strey <mstrey@strey.biz>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Modification dates in Worg
Date: Tue, 29 Sep 2015 10:38:44 -0400 [thread overview]
Message-ID: <CA+vqiLHO4u3vRDmoA4tX5Qwj4rz8h=W8tDYUOt2dq+=jOZytWA@mail.gmail.com> (raw)
In-Reply-To: <874midwsy9.fsf@strey.biz>
Hi Machael,
Well, you're welcome to add modification dates to the worg files. IMO
this won't help much, since some sections of the same file may be up
to date while other sections may be out of date. Something like
git-blame is needed I think in order to get a sense of how up-to-date
a particular section might be.
Best,
Ista
On Tue, Sep 29, 2015 at 4:06 AM, Michael Strey <mstrey@strey.biz> wrote:
> On Mo, 2015-09-28 at 17:04, Ista Zahn wrote:
>> I've created a worg mirror on github at
>> https://github.com/izahn/worg-mirror/, so you can see the modification
>> dates via git-blame.
>
> Thank you. That will help me and maybe some other people who follow this
> thread. Unfortunately it does not solve the general problem. Most
> people access Worg via HTML.
>
> --
> Michael Strey
> http://www.strey.biz * https://twitter.com/michaelstrey
>
>
next prev parent reply other threads:[~2015-09-29 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-26 18:39 babel header arguments tutorial? Lawrence Bottorff
2015-09-26 21:39 ` Charles C. Berry
2015-09-27 8:22 ` Modification dates in Worg (was: babel header arguments tutorial?) Michael Strey
2015-09-28 15:04 ` Ista Zahn
2015-09-29 8:06 ` Modification dates in Worg Michael Strey
2015-09-29 14:38 ` Ista Zahn [this message]
2015-09-26 22:09 ` babel header arguments tutorial? Nick Dokos
2015-09-26 22:43 ` Thomas S. Dye
2015-09-27 2:41 ` Nick Dokos
2015-09-27 16:28 ` Lawrence Bottorff
2015-09-27 19:51 ` Nick Dokos
2015-09-27 16:47 ` Thomas S. Dye
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='CA+vqiLHO4u3vRDmoA4tX5Qwj4rz8h=W8tDYUOt2dq+=jOZytWA@mail.gmail.com' \
--to=istazahn@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mstrey@strey.biz \
/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).