emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: org-annotate/collaboration?
Date: Thu, 09 Feb 2017 14:07:00 -0800	[thread overview]
Message-ID: <87fujnuigr.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CAF-1L2QsPLYDOtkjbFTD1U=Gpn7R73d05pkntg8tykC-_WWqmA@mail.gmail.com

"Alan E. Davis" <lngndvs@gmail.com> writes:

> I am looking for something a little different than this: annotated ls
> listings.  I have been searching blindly for years for this.  
>
> Back in the 90s was a Dos clone called 4dos, which featured directory
> listings with annotations, such that typing whatever the command was
> (dir?), gave a listing with the file name just like "dir" but also a
> description of the file.  
>
> It was exceedingly useful for me, in keeping track of a large number
> of files.  I have never seen anything like it.
>
> Could org-annotate fulfill at least part of this requirement?  (I have
> posted to this list a similar question quite some years ago.)

org-annotate could do the annotation part of it, but really that part
pales compared to the challenge of creating and maintaining directory
listings in Org. Doing it once would be easy, but tracking
additions/deletions/renames in the directory sounds like a *lot* of
work, not to mention making sure the annotations follow the correct
entry.

I suppose if you *only* edited the directory listing through custom
commands you implement from Org mode you could keep it under control,
but still... Some challenges energize you when you start imaging how to
solve them. Others make you exhausted just thinking about them!

Eric

  reply	other threads:[~2017-02-09 22:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09  1:10 org-annotate/collaboration? Matt Price
2017-02-09  5:21 ` org-annotate/collaboration? Eric Abrahamsen
2017-02-09  7:09   ` org-annotate/collaboration? Alan E. Davis
2017-02-09 22:07     ` Eric Abrahamsen [this message]
2017-02-10  4:43       ` org-annotate/collaboration? Alan E. Davis
2017-02-10 21:19         ` org-annotate/collaboration? Cook, Malcolm
2017-02-10 22:59           ` org-annotate/collaboration? Alan E. Davis
2017-02-11 18:07   ` org-annotate/collaboration? Uwe Brauer
2017-02-14  1:55     ` org-annotate/collaboration? Eric Abrahamsen
2017-02-14 21:44       ` org-annotate/collaboration? Uwe Brauer
2017-02-16  1:45         ` org-annotate/collaboration? Eric Abrahamsen
2017-02-16 18:53           ` org-annotate/collaboration? Uwe Brauer
2017-02-11 22:20 ` org-annotate/collaboration? Eduardo Mercovich

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=87fujnuigr.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).