emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: "Cook, Malcolm" <MEC@stowers.org>
Cc: Nick Dokos <ndokos@gmail.com>, Org-mode <emacs-orgmode@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: org 9.2.6 and org 9.1.9
Date: Thu, 28 Nov 2019 08:51:03 +1100	[thread overview]
Message-ID: <CAC=50j9qKb=WmTbk1aBX3R2ZLCK-m+SJAvKn6F86NMg+t0xQCA@mail.gmail.com> (raw)
In-Reply-To: <BN6PR20MB12827764BA9D00F781204092BE440@BN6PR20MB1282.namprd20.prod.outlook.com>

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

>> But I don't think the issue is with package.el per se.

> Maybe it needs fixes elsewhere as well, but it's via package.el that the
> problem is usually exposed.

Yes, but I think that is mainly because that is the most common way people
install it. The manual is fairly clear on this - don't install org-mode vai
package.el if you have already visited an org file (or loaded
org-functionality). Package.el does make it worse as it may install org as
a dependency rather than as a result of an explicit request from the user.

>> You get the same problem if you try to install org-mode manually
>> without package.el.

> Depends how you do it.

True. If you build it using 'make' it is in a separate environment, using
batch and avoiding your init.el, so no issues.

It has been mentioned a few times in this thread that issues need to be
reported so that they can be logged as bugs and fixed. Unfortunately, this
is very difficult as the package.el installation does not fail. Everything
appears to have worked fine and even when you then start working with org
afterwards, it can appear to all be fine until you try some action, at
which point you get an error. This may not happen for hours, days or even
in a later session, so the connection between installation and problem is
lost.

On Thu, 28 Nov 2019 at 04:20, Cook, Malcolm <MEC@stowers.org> wrote:

> Hi Stefan,
>
>
>
> I don’t think I’ve ever seen a root-cause analysis, but I’ve seen many
> problems that are resolved by some version of a “clean build” of org.  Here
> are some:
>
>
>
> - [[
> https://lists.defectivebydesign.org/archive/html/emacs-orgmode/2012-09/msg01365.html][Installing
> Org through the new http://orgmode.org ELPA]]
>
> - [[
> https://lists.defectivebydesign.org/archive/html/emacs-orgmode/2015-08/msg00316.html][latest
> org from Elpa error: Invalid function: org-babel-header-a]]
>
> - [[
> https://lists.defectivebydesign.org/archive/html/emacs-orgmode/2015-08/msg00318.html][Re:
> [O] wrong type argument listp... org-element-set-contents]]
>
>
>
> That's what I got.
>
>
>
> BTW: I now use org-plus-contrib in place of org with this mantra:
>
>
>
> (add-to-list 'package-archives '("org" . "http://orgmode.org/elpa/") t)
>
> (use-package  org
> ;org-plus-contrib                                          ; instead of
> org-mode
>
>   :ensure org-plus-contrib ; following
> http://emacs.stackexchange.com/questions/7890/org-plus-contrib-and-org-with-require-or-use-package
>
> )
>
>
>
> - Cheers
>
> Malcolm
>
>
>
> > Here's what I do, at the shell:
> >
> >
> >
> > emacs -Q -batch -eval "(progn (require 'package) (add-to-list
> > 'package-archives '(\"org\" . \"http://orgmode.org/elpa/\
> <http://orgmode.org/elpa/>"<http://orgmode.org/elpa/%22>;))
> > (package-initialize) (package-refresh-contents) (package-install
> > 'org-plus-contrib))"
>
> I can't blame you for using such workarounds, but it would *really* help
> if you could report the actual problems encountered (and then use the
> workaround until we fix the source of the problem).
>
>
> Stefan
>


-- 
regards,

Tim

--
Tim Cross

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

  reply	other threads:[~2019-11-27 21:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-24 13:37 Jean-Christophe Helary
2019-11-26 19:15 ` Nick Dokos
2019-11-26 21:41   ` Tim Cross
2019-11-27  2:59     ` Cook, Malcolm
2019-11-27  3:13       ` Jean-Christophe Helary
2019-11-27  6:18         ` Stefan Kangas
2019-11-27 13:23       ` Stefan Monnier
2019-11-27 17:20         ` Cook, Malcolm
2019-11-27 21:51           ` Tim Cross [this message]
2019-11-27 22:01           ` Stefan Monnier
2019-11-26 23:14   ` Jean-Christophe Helary
2019-11-27  3:24     ` Stefan Monnier
2019-11-27  5:43       ` Jean-Christophe Helary
2019-11-27  6:00         ` Tim Cross
2019-11-27  6:29           ` Stefan Kangas
2019-11-27  6:42             ` Tim Cross
2019-11-27 10:11               ` Stefan Kangas
2019-11-27 13:21               ` Stefan Monnier
2019-11-27 15:44             ` Eli Zaretskii
2019-11-27  7:04           ` Fraga, Eric
2019-11-27  6:34       ` Stefan Kangas

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='CAC=50j9qKb=WmTbk1aBX3R2ZLCK-m+SJAvKn6F86NMg+t0xQCA@mail.gmail.com' \
    --to=theophilusx@gmail.com \
    --cc=MEC@stowers.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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).