emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Eric S Fraga <esflists@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>,
	Nicolas Goaziou <mail@nicolasgoaziou.fr>, Rasmus <rasmus@gmx.us>,
	Kaushal Modi <kaushal.modi@gmail.com>
Subject: Re: [ANN] OrgStruct is dead. Long live Orgalist.
Date: Tue, 10 Apr 2018 07:51:41 +1000	[thread overview]
Message-ID: <87efjo6ob6.fsf@gmail.com> (raw)
In-Reply-To: <877epg2vct.fsf@gmail.com>


Eric S Fraga <esflists@gmail.com> writes:

>> Yes.. there was a tome of discussion on this on emacs-devel. I have saved
>> this link for my reference:
>> http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=24acb31c04b4048b85311d794e600ecd7ce60d3b
>
> Ah, so in emacs 27, package initialisation happens whether you want it
> or not...  I guess I have to give in and move with the times!  Thanks
> for the link.  I do read emacs-devel but not all of it sticks.
>

I think there is some confusion regarding package initialisation as many
people have used same/similar terms to mean different things. As I
understand it, the packages are initialised to the 'autoload' point
i.e. all the actual code associated with the package is not 'loaded'
into the system, but various entry points are setup so that should you
call a core function, open up an associated file, run an associated
mode, then the package will be loaded. In many respects, not terribly
different from how most emacs 'built-in' packages used to work (many of
which have now been moved out into ELPA packages.

I have also found the 'use-package' package to be extremely useful in
making my setup clearer, further controlling package setup/load and
deferring package loading to get faster startup times.

I wouldn't worry about emacs 27 too much. We are still waiting on emacs
26, so emacs 27 is probably 5+ years away yet! 

-- 
Tim Cross

  reply	other threads:[~2018-04-09 21:51 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-31 12:02 [ANN] OrgStruct is dead. Long live Orgalist Nicolas Goaziou
2017-12-31 14:46 ` Eric S Fraga
2017-12-31 15:40   ` Nicolas Goaziou
2017-12-31 16:05     ` Eric S Fraga
2017-12-31 16:57       ` Nicolas Goaziou
2017-12-31 18:50         ` Eric S Fraga
2018-01-01 10:15           ` Nicolas Goaziou
2018-01-01 16:58             ` Eric S Fraga
2018-01-01 18:06             ` Eric Abrahamsen
2018-04-08 12:58             ` Rasmus
2018-04-08 13:23               ` Nicolas Goaziou
2018-04-08 19:16                 ` Samuel Wales
2018-04-08 20:18                   ` Nicolas Goaziou
2018-04-09  2:47                     ` stardiviner
2018-04-12  1:42                       ` stardiviner
2018-04-09 12:10                     ` Eric S Fraga
2018-04-09 12:18                       ` Kaushal Modi
2018-04-09 12:25                         ` Eric S Fraga
2018-04-09 12:45                           ` Kaushal Modi
2018-04-09 14:14                             ` Eric S Fraga
2018-04-09 14:19                               ` Kaushal Modi
2018-04-09 16:33                                 ` Eric S Fraga
2018-04-09 21:51                                   ` Tim Cross [this message]
2018-04-10  5:20                                     ` Eric S Fraga
2018-04-10  5:51                                       ` Tim Cross
2018-04-10  5:57                                         ` Eric S Fraga
2018-04-26 23:34                     ` Bastien
2018-04-27 14:15                       ` Nicolas Goaziou
2018-04-27 16:13                         ` Bastien
2018-04-09  8:25 ` [Radio tables???] (was: [ANN] OrgStruct is dead. Long live Orgalist.) Uwe Brauer
2018-04-09 12:11   ` [Radio tables???] Nicolas Goaziou
2018-04-09 16:03     ` Uwe Brauer
2018-04-09 21:30   ` Rasmus
2018-04-10  2:20     ` Nick Dokos
2018-04-10 21:47       ` Rasmus
2018-04-10 22:39         ` Nick Dokos
2018-04-10 10:22     ` Uwe Brauer
2018-04-10 21:57       ` Rasmus

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=87efjo6ob6.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=esflists@gmail.com \
    --cc=kaushal.modi@gmail.com \
    --cc=mail@nicolasgoaziou.fr \
    --cc=rasmus@gmx.us \
    /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).