emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Problems while trying to load feature
Date: Tue, 16 Mar 2021 12:36:22 -0400	[thread overview]
Message-ID: <874khb8395.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: CABd2k000EmGgAki6P6HKk8NYesDwjHao7ZO=dvi3wyGGMftihQ@mail.gmail.com

"Charles R (Charlie) Martin" <chasrmartin@gmail.com> writes:

> This is a problem I’ve noticed as well. Now, I am a programmer — my
> code or it’s descendants is still in the distribution — I do update
> org mode regularly, and I get messages when I start up Emacs about
> Org mode files that can’t be loaded. I wouldn’t be surprised if the
> cause is this renaming. But honestly I stopped having time to hack
> emacs 30 years ago. Wouldn’t it be desirable if changes that aren’t
> backward-compatible included some kind of assistance for users? 
>

You probably don't want to hear this, but you will have to figure out
what those messages are telling you and fix the problems. At best,
they might be innocuous: your init file might be trying to load things
that don't exist any more. At worst, you may be running a mixed
installation: you might be loading things from various versions of Org
mode that might coexist on your system(s) (depending on how exactly
you install Org mode: if you use the version that is bundled with
emacs *only* you should not have any problems; but if you install a
more recent one from ELPA or from git, you should be careful). If you
encounter problems after the initial load, you might have a mixed
installation. See https://orgmode.org/worg/org-faq.html#mixed-install for more
details on how to check. Mixed installations are an unending source of
problems and need to be taken care of.

I install new versions of emacs and Org mode fairly frequently (every
couple of months) at which point I restart emacs to see whether any
such problems crop up. If there are, I fix them right then and there,
until I can get a clean restart. If it's not obvious, I take a look
through the etc/ORG-NEWS file, which you should have locally, but in a
pinch you can look for it online:

    https://code.orgmode.org/bzg/org-mode/src/master/etc/ORG-NEWS

In particular, this is the best place for assistance with backward
incompatibilities that you mentioned above. Assuming you know which
release you came from and which release you are going to, look through
the sections describing them and all intermediate releases, to see
what backward incompatibilites were introduced and what suggested
solutions there are. As a last resort, you can always ask here. In
general, I find that fixing these problems asap is better for my
sanity.

Cleaning up your init file to get rid of the (now) useless loads is
also a good idea (even though they are innocuous): init files tend to
accumulate junk (mine has been doing that for 30 years), so getting
rid of old cruft is, for me, another essential activity to maintain a
semblance of sanity.

My $0.02, YMMV, etc.

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler



      reply	other threads:[~2021-03-16 16:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.43.1613926885.11967.emacs-orgmode@gnu.org>
2021-03-14 15:38 ` Problems while trying to load feature Ypo
2021-03-14 17:05   ` Richard Lawrence
2021-03-15  7:57     ` Ypo
2021-03-15 15:15   ` Nick Dokos
2021-03-15 15:24     ` Charles R (Charlie) Martin
2021-03-16 16:36       ` Nick Dokos [this message]

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=874khb8395.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@gmail.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).