emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Charles R (Charlie) Martin" <chasrmartin@gmail.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Problems while trying to load feature
Date: Mon, 15 Mar 2021 11:24:10 -0400	[thread overview]
Message-ID: <CABd2k000EmGgAki6P6HKk8NYesDwjHao7ZO=dvi3wyGGMftihQ@mail.gmail.com> (raw)
In-Reply-To: <878s6o8n3i.fsf@alphaville.usersys.redhat.com>

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

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?

On Mon, Mar 15, 2021 at 11:16 Nick Dokos <ndokos@gmail.com> wrote:

> The renaming was e.g org-bbdb to ol-bbdb, *NOT* to ol-org-bbdb.
>
> Similarly for all the rest: you won't find any of them in any installation.
>
> --
> Nick
>
> "There are only two hard problems in computer science: cache
> invalidation, naming things, and off-by-one errors." -Martin Fowler
>
>
>

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

  reply	other threads:[~2021-03-15 15:27 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 [this message]
2021-03-16 16:36       ` Nick Dokos

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='CABd2k000EmGgAki6P6HKk8NYesDwjHao7ZO=dvi3wyGGMftihQ@mail.gmail.com' \
    --to=chasrmartin@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@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).