From: Bastien <bzg@gnu.org>
To: Aaron Ecay <aaronecay@gmail.com>
Cc: emacs-orgmode@gnu.org, Rasmus Pank Roulund <rasmus@gmx.us>
Subject: Re: Smooth transition for modules
Date: Tue, 08 May 2018 11:46:43 +0200 [thread overview]
Message-ID: <877eoev5rw.fsf@gnu.org> (raw)
In-Reply-To: <87vabysdks.fsf@gmail.com> (Aaron Ecay's message of "Tue, 08 May 2018 10:26:27 +0100")
Hi Aaron,
thanks for your feedback.
Ecay <aaronecay@gmail.com> writes:
> Indeed, the patch was written under that assumption. If the situation
> changes, (at least) some tweaks would be needed.
I will think again about the whole issue and propose a change when
I have some code to show.
> I like this idea, but I also think that emacsʼ packages feature is a
> better/newer way to implement something like this. What if:
>
> 1. We donʼt include org-tempo in org releases
(Assuming we don't want org-tempo to live in Org's core.)
> 2. We teach GNU ELPA to include org-tempo as a package (corresponding to
> stable org releases)
> 3. We teach <https://orgmode.org/elpa/> to also do so (corresponding to
> nightly org releases)
(I doubt https://orgmode.org/elpa/ is still very useful, it might go
away eventually.)
> 4. We implement your suggested user prompt, but it will ask them if they
> want to install the org-tempo package from ELPA
You mean: instead of simply requiring other packages from a package,
add a new Suggest: header for packages suggestions?
I find this to be a great idea indeed, mimicking what apt-get does
when suggesting other packages to install.
On top of that, you could have an option in package.el that, when
turned on, would explicitely ask the user if she wants to install
suggested packages.
> In this way, users who either install org from GNU ELPA or use the
> version bundled with emacs will get the latest release version of
> org-tempo from GNU ELPA.
I fail to see how users who don't install Org at all and use the
version that is bundled with Emacs are asked whether they want to
install a soon-to-be-deprecated package - let me know if I missed
something.
> Those who install the nightly version of org
> will get the corresponding nightly version of org-tempo.*
>
> WDYT?
I think this discussion shows there is room for nice ideas when it
comes to enhance the user experience!
> * Those of us who install org from git might have to do something else
> to make sure the right version of org-tempo is loaded, but weʼre used to
> living on the edge. :P
Well, I think that even experienced users would enjoy discovering new
packages when suggested by the packages they use -- and also enjoy the
fact that they are asked whether they accept to disable a feature (now
externalized as a package) when they upgrade a package.
I hope we can digg in that direction!
--
Bastien
next prev parent reply other threads:[~2018-05-08 9:47 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-29 10:24 [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]") Bastien
2018-04-29 10:50 ` Nicolas Goaziou
2018-04-29 11:05 ` Bastien
2018-04-29 12:01 ` Nicolas Goaziou
2018-04-29 13:22 ` Bastien
2018-04-29 17:40 ` Thomas S. Dye
2018-04-29 20:56 ` Bastien
2018-04-29 22:05 ` Tim Cross
2018-04-29 22:31 ` Bastien
2018-04-29 22:27 ` Tim Cross
2018-04-29 23:03 ` Bastien
2018-04-30 10:29 ` Nicolas Goaziou
2018-04-30 14:03 ` Kevin Foley
2018-04-30 14:17 ` Kevin Foley
2018-05-05 17:20 ` Rasmus
2018-05-02 12:43 ` Bernt Hansen
2018-05-08 6:23 ` Bastien
2018-05-05 17:17 ` Rasmus
2018-05-08 6:27 ` Bastien
2018-05-01 15:49 ` Aaron Ecay
2018-05-01 19:31 ` Eric S Fraga
2018-05-02 9:10 ` Rasmus Pank Roulund
2018-05-02 17:12 ` Aaron Ecay
2018-05-05 17:29 ` Rasmus
2018-05-06 20:02 ` Aaron Ecay
2018-05-07 22:53 ` Rasmus
2018-05-08 0:57 ` Aaron Ecay
2018-05-08 6:56 ` Bastien
2018-05-21 14:24 ` Rasmus
2018-05-08 6:52 ` Bastien
2018-05-21 14:19 ` Rasmus
2018-05-08 6:49 ` Smooth transition for modules (was: [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")) Bastien
2018-05-08 9:26 ` Aaron Ecay
2018-05-08 9:46 ` Bastien [this message]
2018-05-08 13:28 ` Smooth transition for modules Aaron Ecay
2018-05-08 6:34 ` [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]") Bastien
2018-04-30 8:47 ` Eric S Fraga
2018-05-08 8:37 ` Bastien
2018-04-29 13:24 ` Christian Moe
2018-04-29 13:55 ` Charles Millar
2018-04-29 19:08 ` Diego Zamboni
2018-04-29 20:30 ` Rasmus
2018-04-29 20:44 ` Bastien
2018-04-29 23:32 ` Bernt Hansen
2018-05-02 20:24 ` Bernt Hansen
2018-05-03 9:44 ` Carsten Dominik
2018-05-03 13:30 ` William Denton
2018-05-04 7:34 ` Neil Jerram
2018-05-04 7:45 ` Bastien
2018-05-05 1:37 ` Samuel Wales
2018-05-05 2:16 ` Tim Cross
2018-05-05 2:28 ` Samuel Wales
2018-05-05 2:37 ` Tim Cross
2018-05-05 12:42 ` Nicolas Goaziou
2018-05-05 17:33 ` Rasmus
2018-05-01 11:57 ` Nick Helm
2018-04-29 20:25 ` Rasmus
2018-04-29 21:53 ` Nicolas Goaziou
2018-05-02 9:03 ` Rasmus
2018-04-30 16:36 ` Steve Downey
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=877eoev5rw.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=aaronecay@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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).