From: Tim Visher <tim.visher@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Cc: Jan Ulrich Hasecke <juh+org-mode@mailbox.org>
Subject: Re: frustrations
Date: Wed, 1 Dec 2021 10:52:42 -0500 [thread overview]
Message-ID: <CAHa53uy98KN-Oga0WXQSsXpgFxxZ0PURiYrMC9M7iV_FpPkwiw@mail.gmail.com> (raw)
In-Reply-To: <87k0goxz3q.fsf@ucl.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]
Hi Jan,
On Wed, Dec 1, 2021 at 7:58 AM Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> On Wednesday, 1 Dec 2021 at 13:21, Jan Ulrich Hasecke wrote:
> > How do you configure your emacs using current versions like org 9.5 but
> > at the same time avoiding problems with incompatible packages or newly
> > introduced bugs?
>
> …
>
> Avoiding problems with incompatible packages or new bugs is impossible,
> however. The solution is to avoid upgrade-itis and only upgrade when
> necessary. Although I track org from git, I don't update all the time
> and only do so when I know I will have some time to deal with any
> repercussions. (like today where I upgraded both Emacs and org because
> I know I have no immediate deadlines)
>
> Most other packages, I seldom upgrade if ever.
>
I just wanted to quickly second this. The old saying "If it ain't broke,
don't fix it." is evergreen.
The other thing I'll say though is that so long as you use the `~/.emacs.d`
or `~/.config/emacs` it's very easy to place the entirety of your emacs
config under source control. The key thing to do here is to _check in_ your
package dependencies (`elpa` directory in my case). That way whenever you
upgrade a package it's very easy to revert to a known working state if you
don't have time to work through the incompatibilities.
--
In Christ,
Timmy V.
https://blog.twonegatives.com
http://five.sentenc.es
[-- Attachment #2: Type: text/html, Size: 1954 bytes --]
next prev parent reply other threads:[~2021-12-01 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 12:21 frustrations Jan Ulrich Hasecke
2021-12-01 12:36 ` frustrations Timothy
2021-12-01 15:43 ` frustrations Arthur Miller
2021-12-01 12:56 ` frustrations Eric S Fraga
2021-12-01 15:52 ` Tim Visher [this message]
2021-12-01 22:12 ` frustrations Tim Cross
2021-12-03 9:36 ` frustrations juh
2021-12-02 1:41 ` frustrations Ihor Radchenko
2021-12-03 11:51 ` frustrations Dr. Arne Babenhauserheide
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=CAHa53uy98KN-Oga0WXQSsXpgFxxZ0PURiYrMC9M7iV_FpPkwiw@mail.gmail.com \
--to=tim.visher@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=juh+org-mode@mailbox.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).