emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Samuel Banya" <sbanya@fastmail.com>
To: "Samuel Wales" <samologist@gmail.com>,
	"Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: Charles Berry <emacs-orgmode@gnu.org>, Eric S Fraga <e.fraga@ucl.ac.uk>
Subject: Re: literate programming, development log -- ideas? (ominbus reply)
Date: Fri, 11 Jun 2021 00:13:31 +0000	[thread overview]
Message-ID: <4b176952-c02f-43ed-80c3-d7eb9a8541d1@www.fastmail.com> (raw)
In-Reply-To: <CAJcAo8vcqexWapgxxG3e27u1bTDYN7N_6h_hjWM946HMYgL8Bw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3011 bytes --]

I actually nuke Emacs's ability to do backups with this in my config:

** Nuke Emacs' ability to make backups and autosaves since its annoying and too bloated
   #+BEGIN_SRC emacs-lisp
     (setq make-backup-files nil)
     (setq auto-save-default nil)
   #+END_SRC

Reason being is that its one of the worst automatic features of any editor. I hate having to deal with ~ files all over the place. However, I've done this for other editors like Vim as well since swapfiles just are a pain to deal with.

I didn't know they had an rsync variant for Emacs. Now that is nice.

I'm okay with git repos for dot files or some kind of programming project but yeah, I've been debating something else for an org based repo cause I too have almost had my 'life.org' be completely destroyed with a merge event.

On Thu, Jun 10, 2021, at 10:07 PM, Samuel Wales wrote:
> undo [or equivalent] in buffer.  no saving to disk.
> 
> emacs auto save to an auto-expiring directory
> 
> emacs backups every save to an auto-expiring directory
> 
> git snapshots when i feel like it.  search as needed.
> 
> branching in the text itself, by use of comments above if it is
> incoming/new and below if it is old/reference.
> 
> many use git branch but i wouldn't remember the branch was in git and
> i don't want to have to rely on git for such things unless it disrupts
> the text without it.  for me it is merely an archive.  it is not an
> active repository of future possibilities and current ongoing
> activities.  even with magit, git ui is complex to me. its storage
> model is not merely an endofuctor of dags.
> 
> so i use only basic features when possible.  many years later i still
> fear merges/rebases and even stashes and find the merge/rebase
> presentation to be quite bizarre and can't believe anybody finds it
> the most useful.  certain sequences of staging, unstaging, and
> snaphotting can actually cause buffer corruption.  git notes feature
> is another complexity which while small i'd rather have git recognize
> all file permissions by default.
> 
> incidentally, rsync wrapper called rsnapshot works well.  i wouldn't
> use it for branching.  you can use unix commands = win.
> 
> 
> On 6/9/21, Dr. Arne Babenhauserheide <arne_bab@web.de <mailto:arne_bab%40web.de>> wrote:
> >
> > Eric S Fraga <e.fraga@ucl.ac.uk <mailto:e.fraga%40ucl.ac.uk>> writes:
> >
> >>> Not sure if it counts as off-topic for this thread, but does everyone
> >>> use Git to manage their Org docs and notes?
> >>
> >> I use a variety of version control systems but for multiple computers I
> >> use unison to keep them all synchronised.
> >
> > I use Mercurial for all my private versiontracking.
> >
> > Best wishes,
> > Arne
> > --
> > Unpolitisch sein
> > heißt politisch sein
> > ohne es zu merken
> >
> 
> 
> -- 
> The Kafka Pandemic
> 
> Please learn what misopathy is.
> https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
> 

[-- Attachment #2: Type: text/html, Size: 4355 bytes --]

  reply	other threads:[~2021-06-11  0:14 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
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 [this message]
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=4b176952-c02f-43ed-80c3-d7eb9a8541d1@www.fastmail.com \
    --to=sbanya@fastmail.com \
    --cc=arne_bab@web.de \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@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.
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).