Mark E. Shoulson writes:
> On 2/19/20 2:39 AM, Bastien wrote:
>> - org-hide-emphasis-markers => t
>
> Just to note: I've been working on a minor-mode in which the emphasis
> markers are "invisible" but not hidden (i.e. they still take up space,
[…]
> size, so the extra space is not quite as
On 2/19/20 2:39 AM, Bastien wrote:
- org-hide-emphasis-markers => t
Just to note: I've been working on a minor-mode in which the emphasis
markers are "invisible" but not hidden (i.e. they still take up space,
they're just in 'org-hide face or something similar), except when the
point is
Oh yeah, I agree that it's redundant--and that's why I was more just
advocating for the functionality it provided rather than for the module
itself.
It's just a piece of functionality that a lot of people seem to use and
enjoy, and if there were a way to keep it without holding onto a second
Hi,
Nicolas Goaziou writes:
> In this case, a strong argument against it is: there is already a
> template mechanism available out of the box, why would we provide
> two of them?
I bet most users of the <* completion mechanism provided by org-tempo
don't even notice it is a "template"
Hello,
Bastien writes:
> Archenoth writes:
>
>> 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.
>
> You say it
Hi,
Archenoth writes:
> 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.
You say it better than I did - I will see if I
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
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 :
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
>
> > However, hiding emphasis and macro markers can make editing text at
> > the boundaries of emphasized text non-intuitive, which I can imagine
> > might frustrate some new users, so that should probably be carefully
> > considered.
>
+1e6
> Interestingly, hiding emphasis and macro markers
Hi Adam,
Adam Porter writes:
> I generally approve of all of these changes.
Thanks for sharing your opinion.
> However, hiding emphasis and macro markers can make editing text at
> the boundaries of emphasized text non-intuitive, which I can imagine
> might frustrate some new users, so that
Marco Wahl writes:
- org-loop-over-headlines-in-active-region => t
>>>
>>> I vote for => 'start-level. Loop over headlines with same level as the
>>> first.
>>
>> Yes, good suggestion.
>
> Let's see what others say.
I can see how that could be useful, but I feel like it would be less
I generally approve of all of these changes. However, hiding emphasis
and macro markers can make editing text at the boundaries of emphasized
text non-intuitive, which I can imagine might frustrate some new users,
so that should probably be carefully considered. The other changes seem
like
recent org stackoverexchangeflowwhatgever post queries why <* is broken. :)
On 2/19/20, Bastien wrote:
> Hi Vladimir,
>
> Vladimir Lomov writes:
>
>>> I'm tempted to count the number of fingers involved ;)
>>
>> C-c C-, s --> Ctrl c , s
>> < s TAB --> Shift , s TAB
>>
>> ???
>
> I added the
Hi Vladimir,
Vladimir Lomov writes:
>> I'm tempted to count the number of fingers involved ;)
>
> C-c C-, s --> Ctrl c , s
> < s TAB --> Shift , s TAB
>
> ???
I added the smiley to make it clear it was a joke.
>> Which may not be *that* stupid when considering "fast" typing.
>> But eh, I
Hello
** Bastien [2020-02-19 18:24:43 +0100]:
> Hi Nicolas,
> Nicolas Goaziou writes:
>> I don't understand. C-c C-, combination is as fast as Org Tempo:
>>
>> C-c C-, s : 3 keys
>> < s TAB : 3 keys
> I'm tempted to count the number of fingers involved ;)
C-c C-, s --> Ctrl c , s
in my old version at least, pretty entities talks about utf-8 and \name.
and the option under discussion does not mention pretty entitities.
dunno abou the implementation or any changes since my version,
but i am arguing from empiricism. the errors are all over the web. :)
On 2/19/20,
Hi Samuel and Marcin,
Marcin Borkowski writes:
> There is already an option for that (~org-use-sub-superscripts~).
> Changing the default to `{} seems a great idea.
I didn't identify this possible change -- other ideas for new defaults
are welcome, of course.
I'm not sure about this one:
Hi Marco,
Marco Wahl writes:
> Fair enough. I tried to implement the sentence "When after the headline
> text, kill the tags" from the documentation for org-special-ctrl-k,
> which I interpreted as kill _all_ tags. Just to make clear my decision
> for the patch.
Yes, I understand - but the
On 2020-02-19, at 21:02, Samuel Wales wrote:
> just an idea but changing the subscript and superscript export feature
> to ‘{}’ would reduce accidental invocation. i have seen solecistic
> subscripts on websites created with org (probably by experts who
> babelize their .emacs!), and on this
just an idea but changing the subscript and superscript export feature
to ‘{}’ would reduce accidental invocation. i have seen solecistic
subscripts on websites created with org (probably by experts who
babelize their .emacs!), and on this ml :).
i have seen it used accidentally more than i have
Hi Bastien and all,
>> Subject: [PATCH 1/2] org: Fix corner case for org-kill-line
>>
>> * lisp/org.el (org-kill-line): Kill _all_ tags when the cursor is on the
>> tags part.
>
> There is a problem with this patch: when on a empty heading with tags,
> killing the tags will let the cursor back
Hi Nicolas,
Nicolas Goaziou writes:
> I don't understand. C-c C-, combination is as fast as Org Tempo:
>
> C-c C-, s : 3 keys
> < s TAB : 3 keys
I'm tempted to count the number of fingers involved ;)
Which may not be *that* stupid when considering "fast" typing.
But eh, I don't want
Hi Detlef,
if you can, please add your vote to the poll:
https://framadate.org/Ufc42EVxS2jO1Ajz
This is not to say that qualitative comments such as Matt's one
won't be taken into account, I read them carefull, especially when
they come from (very-)long-time users, but I hope the poll can be
Hi Joost,
thanks for your feedback. If you can, please add your vote to the
poll, so that we collect all votes in a single place.
Thanks,
--
Bastien
Am Wed, 19 Feb 2020 09:41:21 -0600
schrieb Matthew Lundin :
> Bastien writes:
>
> > - org-fontify-done-headline => t
> >
> > This is useful to visualize done headlines and can be easily
> > turned off, while not being easily discovered for Org newcomers.
>
> I find this a bit visually
On Wed, Feb 19 2020, Matthew Lundin wrote:
- org-hide-emphasis-markers => t
- org-hide-macro-markers => t
[...]
I have a few concerns about this. I believe that markup syntax,
as a
rule, should be visible. Most markdown editors do not hide
markup by
default. I realize that there are some
Bastien writes:
> - org-fontify-done-headline => t
>
> This is useful to visualize done headlines and can be easily turned
> off, while not being easily discovered for Org newcomers.
I find this a bit visually distracting, but that's likely because I've
used Org mode in the "old school" way
Hi Bastien - comments in-line below
Bastien writes:
> Hi Tim,
>
> Tim Cross writes:
>
>> 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 > old habits, but once done the new
Hello,
Bastien writes:
> Well, let's agree to disagree on this one.
>
> org-tempo and C-c C- fill two different use cases: the first one for
> fast block insertion while typing, the second one for e.g. when the
> region is selected.
I don't understand. C-c C-, combination is as fast as Org
Hi Marco,
Marco Wahl writes:
>> Can you propose a patch against the maint branch for the fixes above?
>
> Sure. See the attachments.
Thanks...
> From 49b00d2cf7ca4b8484e0a9679b39b62873ee30b6 Mon Sep 17 00:00:00 2001
> From: Marco Wahl
> Date: Wed, 19 Feb 2020 13:48:01 +0100
> Subject:
Hi!
>>> - org-loop-over-headlines-in-active-region => t
>>
>> I vote for => 'start-level. Loop over headlines with same level as the
>> first.
>
> Yes, good suggestion.
Let's see what others say.
>>> - org-special-ctrl-k => t
>>>
>>> The default value for the sister option org-special-ctrl-a
Hi Tim,
Tim Cross writes:
> 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 old habits, but once done the new version works fine.
Point taken. But as I said, I think both approaches
Am Mittwoch, 19. Februar 2020, 12:30:59 CET schrieb Nicolas Goaziou:
> Hello,
>
> Bastien writes:
> > - Add org-tempo to org-modules
> >
> > Last but not least: we had long discussions about this one in the
> > past. Expansion of the " > the beginning of the line has been turned off. I
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 writes:
> Hello,
>
> Bastien writes:
>
>> - Add org-tempo to org-modules
>>
>> Last but not least: we had long discussions about this one
Hi Nicolas,
Nicolas Goaziou writes:
> 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).
Well, let's agree to disagree on this one.
org-tempo and C-c C- fill two
Hi Marco,
Marco Wahl writes:
>> - org-loop-over-headlines-in-active-region => t
>
> I vote for => 'start-level. Loop over headlines with same level as the
> first.
Yes, good suggestion.
>> - org-special-ctrl-k => t
>>
>> The default value for the sister option org-special-ctrl-a is set to
Hello,
Bastien writes:
> - Add org-tempo to org-modules
>
> Last but not least: we had long discussions about this one in the
> past. Expansion of the " the beginning of the line has been turned off. I have IRL met with
> Org users* who just thought the feature was broken/deleted,
Bastien writes:
> while Org 9.4 is on its way, I am considering changing a few default
> settings (10 options in total). I have created a survey here:
>
> https://framadate.org/Ufc42EVxS2jO1Ajz
>
> Can you take a few minutes and express your opinion there?
Ok. I'll go there in a minute.
>
Hi Samuel,
thanks for your feedback.
Samuel Wales writes:
> On 2/19/20, Bastien wrote:
>> - org-refile-use-cache => t
>>
>> This is a speed boost when refiling entries: if org-refile-targets
>> is big, caching refile targets help refiling faster.
>
> i predict this will generate bug
On 2/19/20, Bastien wrote:
> - org-refile-use-cache => t
>
> This is a speed boost when refiling entries: if org-refile-targets
> is big, caching refile targets help refiling faster.
i predict this will generate bug reports.
in particular pay close attention to restricted refile and whether
Hi all,
while Org 9.4 is on its way, I am considering changing a few default
settings (10 options in total). I have created a survey here:
https://framadate.org/Ufc42EVxS2jO1Ajz
Can you take a few minutes and express your opinion there?
Here is the list of options and a line of justification
42 matches
Mail list logo
