[O] electric-pair, autopair, smartparens, etc in org-mode

Hi eveyrone, I'm just wondering what tools other people use to manage paired parentheses and other markers in org. I'm revisiting my long-ago decision to turn all pairing tools off in org, but every tool I try is pretty frustrating out of the box: - smartparens steals a large number of really

Re: [O] Bug: ox-odt.el should support text:start-value [9.1.14 (9.1.14-7-g01c419-elpaplus @ …/org-plus-contrib-20181015/)]

Hello, "Mark A. Hershberger" writes: > Nicolas Goaziou writes: > >> Could you provide a patch using git format-patch, with a proper commit >> message? > > Attached. Also see > . Applied. Thank you. >>

Re: [O] Why is ":CLOCK => hh:mm" allowed as a clock entry?

Hello, Marcin Borkowski writes: > I am studying the `org-clock-sum' function (I need to parse an Org file > and extract clocking data), and I noticed that ":CLOCK => hh:mm" is > allowed as a clock entry. The Org syntax at >

Re: [O] Bug: ox-beamer add label when option 'allowframebreaks' setted in org-beamer-frame-default-options [9.1.14 (9.1.14-7-g01c419-elpaplus @ .emacs.d/elpa/org-plus-contrib-20181015/)]

Hello, Héctor Enríquez Ramón writes: > Latex beamer not allow 'label=' when 'allowframebreaks' setted in frame. > > In file ox-beamer.el function org-beamer--format-frame search > 'allowframebreaks' option inside beamer-opt but not inside variable > org-beamer-frame-default-options. Then insert

[O] Org source block header argument :var does not support space separated string

Org source block header argument :var does not support quoted string with space separator like bellowing example: For example encrypt text -- ~<<< [TEXT]~ #+NAME: base64 encrypt text #+begin_src sh base64 <<< "stardiviner " #+end_src #+RESULTS: base64 encrypt text :

Re: [O] How to make agenda generation faster

Hello, Adam Porter writes: > Yes, because this is the fastest way to search for matching entries in a > buffer, when it's possible to use a regexp search. You would still do regexp searches, but not at the time of queries. > That would be ideal. The problem I foresee is that, when a buffer's

[O] (no subject)

Org source block header argument :var does not support quoted string with space separator like bellowing example: For example encrypt text -- ~<<< [TEXT]~ #+NAME: base64 encrypt text #+begin_src sh base64 <<< "stardiviner " #+end_src #+RESULTS: base64 encrypt text :

Re: [O] Org source block header argument :var does not support space separated string

Hello, stardiviner writes: > Org source block header argument :var does not support quoted string with > space separator like bellowing example: > > For example > > encrypt text -- ~<<< [TEXT]~ > > #+NAME: base64 encrypt text > #+begin_src sh > > base64 <<< "stardiviner " #+end_src > >

[O] Styling header stats for collapsed trees

Hello, there is a feature of Orgzly that I like: when a headline containing sub-haedlines is folded, the leading star (bullet in Orgzly interface) changes to signal that subheadings are hidden below. I've tried to see if org allows to easily achieve something similar, but the face of the