From: Archenoth <archenoth@gmail.com>
To: Diego Zamboni <diego@zzamboni.org>
Cc: Bastien <bzg@gnu.org>, Org-mode <emacs-orgmode@gnu.org>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Survey: changing a few default settings for Org 9.4
Date: Fri, 21 Feb 2020 14:28:57 -0700 [thread overview]
Message-ID: <CA+GZiYpk3oMaeoEVS3pjHRzEqR765Gmn=XqXogzPDeGPWJ6tbQ@mail.gmail.com> (raw)
In-Reply-To: <CAGY83Ed85_q8gYeiX2m6P63dNKZGp1g8H6dBQGoTDZiLub2-yg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3414 bytes --]
Yes! Thank you Bastien!
On Wed, Feb 19, 2020 at 10:26 AM Bastien <bzg@gnu.org> wrote:
> > Also, my question is still open: is there any strong reason to provide,
> > out of the box, two template mechanisms in Org? This is genuine
> > question.
>
> No, there is no good reason for two template mechanism, and if we can
> rely on org-insert-structure-template only, while still being able to
> complete <* at the beginning of the line, that'd be perfect to me.
>
I definitely agree with this.
I voted (slightly late) for having org-tempo in org-modules--not out of any
love of org-tempo itself, but more because it feels to me like an extremely
natural way to create blocks.
The tab key is extremely easy to hit, and having a fully formed block
created by typing a short string of characters makes the tab-completion
lizard-part of my brain happy in a way that key chord combos simply don't.
I think this is partly because I personally can't do key chords at the same
rate I can type a string of characters--even if they require technically
the same number of keystrokes.
Like, I can type a 10 character command *significantly* faster than I can
hit a number of different combinations of keys that also happen to be 10
keypresses.
I just personally find it really nice!
On Fri, Feb 21, 2020 at 12:37 PM Diego Zamboni <diego@zzamboni.org> wrote:
> Thanks Bastien for all your work!
>
> --Diego
>
>
> On Fri, Feb 21, 2020 at 4:50 PM Bastien <bzg@gnu.org> wrote:
>
>> Hi all,
>>
>> here are the results of the survey, with *47* voters:
>>
>> - 26+2 : org-loop-over-headlines-in-active-region => t
>> - 25+2 : org-agenda-loop-over-headlines-in-active-region => t
>> - 28+3 : org-fontify-done-headline => t
>> - 17+4 : org-hide-emphasis-markers => t
>> - 10+6 : org-hide-macro-markers => t
>> - 15+5 : org-refile-use-cache => t
>> - 23+6 : org-special-ctrl-k => t
>> - 20+6 : org-allow-promoting-top-level-subtree => t
>> - 22+5 : Add org-tempo to org-modules
>>
>> I've changed the values of these options in master:
>>
>> - 35+2 : org-src-tab-acts-natively => t
>> - 28+3 : org-fontify-done-headline => t
>> - 26+2 : org-loop-over-headlines-in-active-region => t
>> - 25+2 : org-agenda-loop-over-headlines-in-active-region => t
>>
>> I've *not* changed the values of these options:
>>
>> - 23+6 : org-special-ctrl-k => t
>> - 22+5 : Add org-tempo to org-modules
>> - 20+6 : org-allow-promoting-top-level-subtree => t
>> - 17+4 : org-hide-emphasis-markers => t
>> - 10+6 : org-hide-macro-markers => t
>> - 15+5 : org-refile-use-cache => t
>>
>> The reason for not changing the default of org-special-ctrl-k is that
>> 23 < 47/2. Also, I think it was a mistake to propose this: even the
>> org-special- prefix should have warned me. The org-special-* options
>> should be nil by default, and while org-special-ctrl-k may be useful,
>> it is as useful as org-special-ctrl-a/e, which sticks to nil too.
>>
>> The reason for not adding org-tempo to org-modules is, on top of the
>> poll being 22 < 47/2, that the current discussion on the list leaves
>> room for improvements that may lead to move org-tempo from Org's core
>> anyway.
>>
>> The reason for not changing the four other options is that they did
>> not get enough votes.
>>
>> I've push the change for the three options in current master.
>>
>> Thanks again for participating to the poll and to the discussions!
>>
>> Best,
>>
>> --
>> Bastien
>>
>>
[-- Attachment #2: Type: text/html, Size: 4649 bytes --]
next prev parent reply other threads:[~2020-02-21 21:29 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
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 [this message]
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='CA+GZiYpk3oMaeoEVS3pjHRzEqR765Gmn=XqXogzPDeGPWJ6tbQ@mail.gmail.com' \
--to=archenoth@gmail.com \
--cc=bzg@gnu.org \
--cc=diego@zzamboni.org \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).