From: Bastien <bzg@gnu.org>
To: Aaron Ecay <aaronecay@gmail.com>
Cc: emacs-orgmode@gnu.org, Rasmus Pank Roulund <rasmus@gmx.us>
Subject: Smooth transition for modules (was: [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]"))
Date: Tue, 08 May 2018 08:49:29 +0200 [thread overview]
Message-ID: <871semhcau.fsf_-_@gnu.org> (raw)
In-Reply-To: <87sh7a9e33.fsf@gmail.com> (Aaron Ecay's message of "Wed, 02 May 2018 18:12:16 +0100")
Hi Aaron,
Aaron Ecay <aaronecay@gmail.com> writes:
> OK, thatʼs good to know. Iʼve held off on any pushing of the patch to
> master until everything is worked out. In the meantime, Iʼve put it in
> a branch “org-tempo”.
thanks for this.
> I also added a second commit to that branch which implements my vision
> of the upgrade path (deprecation warnings, etc.) For convenience, that
> patch is also attached to this email.
Thanks -- I tested it. I like the idea of sending a warning to the
user for backward-incompatible changes but in this case, well, we take
for granted that org-tempo will be turned off by default in the next
release... but this is not decided yet.
To be clear, the whole change still needs work for sure, and nothing
is decided so far.
But here is some food for thought on how to deprecate an Org feature
more nicely.
We have org-modules, which is an internal mechanism to load default
Org modules. Yes, this predates Emacs package system, and yes, we
should question the usefulness of it now (I do).
But: what if we could use org-modules (or a similar mechanism) to tell
the user: "Hey! We, the AlMighty Developers of Org think this feature
is better not to be loaded by default for *every* user - but you, the
independant rebel, might think otherwise, so here is your chance to
turn it on by default in your configuration. Proceed (y/n)?" And
voilà!
For example, the default value of org-modules could be an alist like:
'((org-bbdb . t)
(org-eww . t)
(org-tempo . 'confirm)
Then on first load, traverse this alist and prompt for confirmation
for packages marked 'confirm.
What do you think?
--
Bastien
next prev parent reply other threads:[~2018-05-08 6:49 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 ` Bastien [this message]
2018-05-08 9:26 ` Smooth transition for modules (was: [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")) Aaron Ecay
2018-05-08 9:46 ` Smooth transition for modules Bastien
2018-05-08 13:28 ` 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=871semhcau.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).