From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Jan Ulrich Hasecke <juh+org-mode@mailbox.org>
Cc: Org-mode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: frustrations
Date: Wed, 01 Dec 2021 12:56:41 +0000 [thread overview]
Message-ID: <87k0goxz3q.fsf@ucl.ac.uk> (raw)
In-Reply-To: <Yado1Oq8saqGDPn2@sokrates> (Jan Ulrich Hasecke's message of "Wed, 1 Dec 2021 13:21:40 +0100")
Hello Jan,
I've extracted the org relevant bit from your post.
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?
Well, first of all, I ensure that my load path is set before anything
else is done so that anything that might need org will cause org to be
loaded from the right place. I have this line as the first line in my
.emacs:
(add-to-list 'load-path "~/git/org-mode/lisp")
where I have downloaded the most recent version of org into
~/git/org-mode.
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.
HTH,
eric
--
: Eric S Fraga, with org release_9.5.1-231-g6766c4 in Emacs 29.0.50
: Latest paper written in org: https://arxiv.org/abs/2106.05096
next prev parent reply other threads:[~2021-12-01 12:57 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 ` Eric S Fraga [this message]
2021-12-01 15:52 ` frustrations Tim Visher
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=87k0goxz3q.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).