From: Kevin Bowling <kevin.bowling@kev009.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Document management in Unix, back in the day?
Date: Thu, 12 May 2022 21:01:53 -0700 [thread overview]
Message-ID: <CAK7dMtD-uSwyGTkSQ_5DBmf1OTRG+c1tRxwD=Y2m92xBOTwL_Q@mail.gmail.com> (raw)
In-Reply-To: <8b7daf0d-991a-e8be-9dff-63fe4fb688ab@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
On Fri, Feb 4, 2022 at 10:02 AM Will Senn <will.senn@gmail.com> wrote:
> Today I bit the bullet and dropped my many articles and electronic
> documents related to my technical explorations into Zotero. I was tired of
> constantly having to remember where the documents were located and I wanted
> to be able to curate them better (I tried git for a while, back when, but
> I'm not a fan of non-text data in my repos, and it wasn't really much
> better than the base file system approach). I've been using Zotero for
> years now, for academic works, but not for technical works unrelated to my
> research. I realized the man-years of effort to clean up the entries that I
> had created in about 30-40 seconds of exciting drag and drop, just about
> the time I deleted them from their original locations. I think the work
> will pay off in due time, but we'll see.
>
> Then I thought, surely, I'm not the first person to have had this
> problem... it occurred to me that y'all must have faced this very problem,
> a few years in, back in the late 70's, early 80's. That is, document
> management. What did you do, variously, considering both text and non-text?
>
>
Emacs org-mode comes to mind
> Will
>
>
>
[-- Attachment #2: Type: text/html, Size: 2583 bytes --]
next prev parent reply other threads:[~2022-05-13 4:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 17:01 Will Senn
2022-02-04 17:35 ` Seth J. Morabito
2022-02-04 17:43 ` Adam Thornton
2022-02-04 20:51 ` John Cowan
2022-05-13 1:09 ` Michael Parson
2022-05-13 1:52 ` George Michaelson
2022-05-13 2:04 ` Michael Parson
2022-05-13 2:41 ` Bakul Shah
2022-05-13 4:01 ` Kevin Bowling [this message]
2022-05-13 4:08 ` Adam Thornton
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAK7dMtD-uSwyGTkSQ_5DBmf1OTRG+c1tRxwD=Y2m92xBOTwL_Q@mail.gmail.com' \
--to=kevin.bowling@kev009.com \
--cc=tuhs@minnie.tuhs.org \
--cc=will.senn@gmail.com \
/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.
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 NNTP newsgroup(s).