From mboxrd@z Thu Jan 1 00:00:00 1970 From: Archenoth Subject: Re: Survey: changing a few default settings for Org 9.4 Date: Fri, 21 Feb 2020 14:28:57 -0700 Message-ID: References: <87pnebf2ku.fsf@gnu.org> <878skwos8h.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000053dd34059f1cb6a5" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:33608) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j5FrJ-00076O-BX for emacs-orgmode@gnu.org; Fri, 21 Feb 2020 16:29:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j5FrH-0002ck-Rt for emacs-orgmode@gnu.org; Fri, 21 Feb 2020 16:29:17 -0500 In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org Sender: "Emacs-orgmode" To: Diego Zamboni Cc: Bastien , Org-mode , Nicolas Goaziou --00000000000053dd34059f1cb6a5 Content-Type: text/plain; charset="UTF-8" Yes! Thank you Bastien! On Wed, Feb 19, 2020 at 10:26 AM Bastien 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 wrote: > Thanks Bastien for all your work! > > --Diego > > > On Fri, Feb 21, 2020 at 4:50 PM Bastien 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 >> >> --00000000000053dd34059f1cb6a5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yes! Thank you Bastien!

On Wed= , Feb 19, 2020 at 10:26 AM Bastien <bzg@g= nu.org> wrote:
> Also, my question is still open: is there any strong reason to p= rovide,
> 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-mod= ules--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 i= s 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 bra= in 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 t= echnically the same number of keystrokes.
Like, I can type a 10 c= haracter command significantly faster than I can hit a number of dif= ferent 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> wr= ote:
Hi all,

here are the results of the survey, with *47* voters:

- 26+2 : org-loop-over-headlines-in-active-region =3D> t
- 25+2 : org-agenda-loop-over-headlines-in-active-region =3D> t
- 28+3 : org-fontify-done-headline =3D> t
- 17+4 : org-hide-emphasis-markers =3D> t
- 10+6 : org-hide-macro-markers =3D> t
- 15+5 : org-refile-use-cache =3D> t
- 23+6 : org-special-ctrl-k =3D> t
- 20+6 : org-allow-promoting-top-level-subtree =3D> 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 =3D> t
- 28+3 : org-fontify-done-headline =3D> t
- 26+2 : org-loop-over-headlines-in-active-region =3D> t
- 25+2 : org-agenda-loop-over-headlines-in-active-region =3D> t

I've *not* changed the values of these options:

- 23+6 : org-special-ctrl-k =3D> t
- 22+5 : Add org-tempo to org-modules
- 20+6 : org-allow-promoting-top-level-subtree =3D> t
- 17+4 : org-hide-emphasis-markers =3D> t
- 10+6 : org-hide-macro-markers =3D> t
- 15+5 : org-refile-use-cache =3D> t

The reason for not changing the default of org-special-ctrl-k is that
23 < 47/2.=C2=A0 Also, I think it was a mistake to propose this: even th= e
org-special- prefix should have warned me.=C2=A0 The org-special-* options<= br> 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,

--
=C2=A0Bastien

--00000000000053dd34059f1cb6a5--