From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Survey: changing a few default settings for Org 9.4
Date: Wed, 19 Feb 2020 23:58:03 +1100 [thread overview]
Message-ID: <87eeuqivj8.fsf@gmail.com> (raw)
In-Reply-To: <87k14i7r0s.fsf@nicolasgoaziou.fr>
I agree 100%. We have already gone through this pain and as has been
pointed out numerous times, the 'new' approach has significant benefits
over the old <x expansion. Yes, it takes a bit of effort to untrain the
old habits, but once done the new version works fine.
I also think Nicolas' point that adding (require 'org-tempo) is a lot
more trivial than removing it from the list of loaded modules.
The other poinit is that while tempo has been around for years, it is
not the easiest templating solution to use, especially for those
unfamiliar with it who may want to add their own tempo templates. Other
templating solutions, like yasnippets, are likely much easier for new
users to adopt than tempo.
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> Bastien <bzg@gnu.org> writes:
>
>> - Add org-tempo to org-modules
>>
>> Last but not least: we had long discussions about this one in the
>> past. Expansion of the "<s" templates (and other "<*" templates) at
>> the beginning of the line has been turned off. I have IRL met with
>> Org users* who just thought the feature was broken/deleted, without
>> having/taking the time/knowledge/guts to look for the things they
>> can turn on. I am all for turning this on again, letting experts
>> disabling the feature if they don't want it.
>>
>> * We have regular meetings with https://www.emacs-doctor.com/
>
> This is not a good default, at least for beginners, because Org provides
> a better solution out of the box. There are also better solutions
> outside Org (e.g., Yasnippet).
>
> It is only valuable for existing users, who relied on this feature, and
> don't want to switch. It's perfectly understandable, but it is also fair
> to assume they can add (require 'org-module) to their own configuration.
> _Removing_ the module, OTOH, is subtle.
>
> By the way, this does not belong to the same category as other
> defcustoms discussed. This is only tangential to "how does Org should
> look and feel by default". It relates to: should Org provide multiple
> snippet extensions, knowing this is not a central feature, and Org is
> often seen as bloated by Emacs devs? I don't think so, no matter how
> useful this feature can be for some users.
>
> Regards,
--
Tim Cross
next prev parent reply other threads:[~2020-02-19 12:58 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 7:39 Survey: changing a few default settings for Org 9.4 Bastien
2020-02-19 8:57 ` Samuel Wales
2020-02-19 9:01 ` Bastien
2020-02-19 20:02 ` Samuel Wales
2020-02-19 20:15 ` Marcin Borkowski
2020-02-19 21:35 ` Bastien
2020-02-19 22:06 ` Samuel Wales
2020-02-19 11:03 ` Marco Wahl
2020-02-19 11:41 ` Bastien
2020-02-19 13:21 ` Marco Wahl
2020-02-19 13:39 ` Bastien
2020-02-19 17:57 ` Marco Wahl
2020-02-19 20:44 ` Bastien
2020-02-20 4:11 ` Adam Porter
2020-02-19 11:30 ` Nicolas Goaziou
2020-02-19 11:57 ` Bastien
2020-02-19 14:07 ` Nicolas Goaziou
2020-02-19 17:24 ` Bastien
2020-02-19 23:23 ` Vladimir Lomov
2020-02-19 23:53 ` Bastien
2020-02-20 0:20 ` Samuel Wales
2020-02-19 12:58 ` Tim Cross [this message]
2020-02-19 13:22 ` Bastien
2020-02-19 15:06 ` Tim Cross
2020-02-19 13:03 ` AW
2020-02-19 15:41 ` Matthew Lundin
2020-02-19 16:16 ` Joost Kremers
2020-02-19 17:13 ` Bastien
2020-02-19 16:50 ` Detlef Steuer
2020-02-19 17:14 ` Bastien
2020-02-20 4:07 ` Adam Porter
2020-02-20 7:10 ` Bastien
2020-02-20 14:10 ` Kaushal Modi
2020-02-21 15:49 ` Bastien
2020-02-21 19:36 ` Diego Zamboni
2020-02-21 21:28 ` Archenoth
2020-02-22 9:38 ` Bastien
2020-02-22 12:45 ` Nicolas Goaziou
2020-02-22 13:31 ` Bastien
2020-02-22 18:57 ` Archenoth
2020-03-18 2:20 ` Mark E. Shoulson
2020-03-18 8:58 ` Norman Tovey-Walsh
2020-03-18 20:47 ` Hiding emphasis markers Mark E. Shoulson
2020-05-22 16:47 ` 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=87eeuqivj8.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).