emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Aaron Ecay <aaronecay@gmail.com>
To: Rasmus <rasmus@gmx.us>, emacs-orgmode@gnu.org
Subject: Re: [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")
Date: Sun, 06 May 2018 21:02:18 +0100	[thread overview]
Message-ID: <87wowgr1rp.fsf@gmail.com> (raw)
In-Reply-To: <87wowi8100.fsf@gmx.us>

Hi Rasmus,

2018ko maiatzak 5an, Rasmus-ek idatzi zuen:

> I don’t like it, I’m afraid.  

Iʼm sorry to hear that.

> It’s a bit nagging.

I wouldnʼt call it nagging.  The user presses “<s[TAB]” expecting
something special to happen.  The status quo is that nothing at all
happens.  My proposal is to make something special happen.  Itʼs
different than what the user expected, but it informs them of what has
changed and how to get the old behavior back if they want.

Note that the only circumstance when the “nagging” happens is when a
user presses “<s[TAB]”, and it goes away when either they add
“(org-tempo-global-mode)” to their .emacs or learn a new habit of
pressing C-c C-, instead of <s[TAB]

(We could make the warning appear only once per emacs session, if that
seems like a better balance.)

(The patch I posted on the mailing list had a bug, which would trigger
the warning more often than it should be.  If you installed and tested
the patch from my email message, you would have seen that bug.  I pushed
a followup commit to the org-tempo branch in the repo that fixes the
bug.)

> There’s tools to mark thinks as obsolete in Emacs should we need to.

There are tools to mark functions and variables obsolete when they are
used in elisp code.  There is no way of warning a user about non-code
changes to the user experience, like (in this case) a changed key
binding.

> > 
>> One remaining decision to make is: what is the future of org-tempo?  I am
>> sympathetic to the idea that the best place for it eventually would be
>> org-contrib or GNU ELPA, and not org core.
> 
> We don’t have make that decision now, do we?

We donʼt strictly have to.  Obviously one approach to making the
decision is to wait and see whether org-tempo is widely adopted/used,
and remove it from core if not.  But if we* can already decide on
principle that something like org-tempo belongs best in contrib or
ELPA, then we can communicate the relevant info all at once when 9.2
is released, rather than for 9.2: “now add (require 'org-tempo) to
.emacs to keep using <s[TAB]” [...time passes, a new org release is
born...]  “now you also have to install org-tempo from somewhere
else.”

*Here Iʼm using “we” loosely, I imagine it will mostly be up to you with
input from Nicolas and Bastien and perhaps others.

-- 
Aaron Ecay

  reply	other threads:[~2018-05-06 20:02 UTC|newest]

Thread overview: 91+ 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 [this message]
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                     ` 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
  -- strict thread matches above, loose matches on Subject: below --
2018-04-29 15:06 Jon Snader
2018-04-30 20:37 ` Richard Lawrence
2018-04-30 20:46   ` Peter Dewey Ore
2018-04-30 21:33     ` Michael Gauland
2018-04-30 21:46   ` Jon Snader
2018-04-30 22:25     ` Tim Cross
2018-04-30 22:35       ` Cook, Malcolm
2018-04-30 22:39       ` Jon Snader
2018-04-30 22:49         ` Kaushal Modi
2018-05-01  1:29           ` Alan Tyree
2018-05-01 14:07             ` Christophe Schockaert
2018-05-01  2:00         ` Tim Cross
2018-05-01  2:27           ` Steve Downey
2018-05-01 12:35             ` Nicolas Goaziou
2018-05-01 16:28               ` Aaron Ecay
2018-05-05 18:07                 ` Rasmus
2018-05-06 20:34                   ` Aaron Ecay
2018-05-06 22:11                     ` Tim Cross
2018-05-07 22:30                     ` Rasmus
2018-05-08  0:25                       ` Aaron Ecay
2018-05-08  7:36                         ` Bastien
2018-05-13 20:52                         ` Rasmus
2018-05-01 16:54               ` Cook, Malcolm
2018-05-05 18:01               ` Rasmus
2018-05-06  5:00                 ` Carsten Dominik
2018-05-07 22:33                   ` Rasmus
2018-05-08  7:37                 ` Bastien
2018-05-21 14:35                   ` Rasmus
2018-05-05 23:26               ` Adrian Bradd
2018-05-05 23:37                 ` Josiah Schwab
2018-05-08  7:31               ` Bastien

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=87wowgr1rp.fsf@gmail.com \
    --to=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).