From: Eric S Fraga <esflists@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>, Rasmus <rasmus@gmx.us>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: [ANN] OrgStruct is dead. Long live Orgalist.
Date: Mon, 09 Apr 2018 15:14:07 +0100 [thread overview]
Message-ID: <87d0z8wjps.fsf@gmail.com> (raw)
In-Reply-To: <CAFyQvY212S8-ZNDa6GxuXe1VssDFNQBgktjdUmwfWVHf=q-m2g@mail.gmail.com> (Kaushal Modi's message of "Mon, 09 Apr 2018 12:45:03 +0000")
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
On Monday, 9 Apr 2018 at 12:45, Kaushal Modi wrote:
> On Mon, Apr 9, 2018 at 8:25 AM Eric S Fraga <esflists@gmail.com> wrote:
>
>>
>> Yes, because of byte code incompatibilities. Yes, I probably need to
>> set up major version specific directories. Laziness on my part, I
>> guess. Which is why I am happy for my comment to be ignored. ;-)
>>
>
> OK, but I'll still leave this here in case anyone wants to do that (major
> version specific elpa dir) :)
Thanks for this. Helpful but I have one question: why the difference in
placement of the code? I.e. why cannot I have the directory setting in
my .emacs in both cases? Does emacs 27 initialise package before I do
explicitly?
Thanks again,
eric
--
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-347-gd73a5e
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2018-04-09 14:14 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 [this message]
2018-04-09 14:19 ` Kaushal Modi
2018-04-09 16:33 ` Eric S Fraga
2018-04-09 21:51 ` Tim Cross
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=87d0z8wjps.fsf@gmail.com \
--to=esflists@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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).