From: "Samuel Banya" <sbanya@fastmail.com>
To: "Charles Berry" <emacs-orgmode@gnu.org>
Subject: Re: literate programming, development log -- ideas? (ominbus reply)
Date: Tue, 08 Jun 2021 13:21:36 -0400 [thread overview]
Message-ID: <da7024b2-2d35-4176-89ec-7421730fbbca@www.fastmail.com> (raw)
In-Reply-To: <643664.1623172504@apollo2.minshall.org>
[-- Attachment #1: Type: text/plain, Size: 1923 bytes --]
Not sure if it counts as off-topic for this thread, but does everyone use Git to manage their Org docs and notes?
I ask because of Greg's previous post.
I've noticed that some times after git merge events across a few machines (ex: I forgot I had already pushed notes for my private notes on one machine, and had to merge the results from another machine), I'll get weird "HEAD" and "END" statements inserted by Git.
Also, combined with some tasks duplicating as a result was annoying.
Was debating if this is just something I'd have to deal with, or if there might be a better versioning workflow (ex: just using rsync, etc)
Would be curious on everyone's thoughts.
~ Sam
On Tue, Jun 8, 2021, at 1:15 PM, Greg Minshall wrote:
> Juan Manuel, Eric, Jack, Arne,
>
> thank you all very much for your thoughts.
>
> i've sort of come to grips with Jack's + Arne's, solution, and defined a
> "capture template" that adds something to a pre-named headline. (note
> and capture are among the org features of which i have maintained to
> date a studied ignorance; alas, or a-luck, no more.)
>
> i realized i would like to have headlines (mostly to have the
> convenience of =consult-org-heading=), which i think rules out putting
> my logs inside property drawers.
>
> Eric, when you use something RCS-like as your version control system, i
> assume that makes grepping to find some old note easy enough. but,
> these days i tend to use git. when (assuming) you use git, do you have
> some easy way to say "well, i had this code that looked sort of like
> this... where was it?"? (sorry, that's really a git question, but ...)
>
> cheers, Greg
>
> ps -- for completeness, or code review...
> ----
> ("l"
> "add a logbook entry"
> entry
> (file+olp+datetree buffer-file-name "Logbook")
> "* lbe: %?logbook entry\n :PROPERTIES:\n creation-date: %t\n
> :END:"
> :empty-lines 1
> :tree-type month)
> ----
>
>
[-- Attachment #2: Type: text/html, Size: 2801 bytes --]
next prev parent reply other threads:[~2021-06-08 17:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 11:43 literate programming, development log -- ideas? Greg Minshall
2021-06-07 12:00 ` Juan Manuel Macías
2021-06-08 17:15 ` literate programming, development log -- ideas? (ominbus reply) Greg Minshall
2021-06-08 17:21 ` Samuel Banya [this message]
2021-06-09 8:59 ` Eric S Fraga
2021-06-09 22:21 ` Dr. Arne Babenhauserheide
2021-06-10 22:07 ` Samuel Wales
2021-06-11 0:13 ` Samuel Banya
2021-06-11 14:30 ` Juan Manuel Macías
2021-06-11 15:02 ` Samuel Banya
2021-06-09 14:52 ` Maxim Nikulin
2021-06-10 13:28 ` Greg Minshall
2021-06-11 19:51 ` Christian Barthel
2021-06-13 0:46 ` Tim Cross
2021-06-13 15:48 ` Samuel Banya
2021-06-13 23:13 ` Tim Cross
2021-06-09 8:57 ` Eric S Fraga
2021-06-13 0:31 ` Tim Cross
2021-06-13 4:27 ` Greg Minshall
2021-06-13 7:29 ` Tim Cross
2021-06-14 6:14 ` Greg Minshall
2021-06-07 12:08 ` literate programming, development log -- ideas? Eric S Fraga
2021-06-13 0:24 ` Tim Cross
2021-06-13 15:44 ` Samuel Banya
2021-06-14 12:57 ` Greg Minshall
2021-06-07 13:53 ` Dr. Arne Babenhauserheide
2021-06-07 17:59 ` briangpowell
2021-06-07 23:17 ` Dr. Arne Babenhauserheide
2021-06-08 2:06 ` Samuel Banya
2021-06-08 3:23 ` Greg Minshall
2021-06-08 3:31 ` Samuel Banya
2021-06-08 6:15 ` Greg Minshall
2021-06-08 16:59 ` Greg Minshall
2021-06-07 19:19 ` Jack Kamm
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=da7024b2-2d35-4176-89ec-7421730fbbca@www.fastmail.com \
--to=sbanya@fastmail.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).