Re: virtual org-mode meetup tomorrow 11am EST

2020-03-29 Thread Adam Porter
Ihor Radchenko writes: > FYI: > I have recently stumbled upon a FOSS service for video conferencing: > https://meet.jit.si/ (recommended in Tor blog > https://blog.torproject.org/remote-work-personal-safety) > > Might be another option for future meetings. Yes, that's what was used for

Re: Automatic formatting of the table as you type

2020-03-29 Thread ndame
> I suggest being very careful with this.  While it's a very nice feature, > it's bound to be slow with large tables.  And it is very frustrating for > users when typing becomes laggy. The feature could be an optional minor mode first and then later made default if it proves to work well in every

Re: Automatic formatting of the table as you type

2020-03-29 Thread Adam Porter
ndame writes: > As for org-at-table-p being slow storing the start and end position of > the table could be a solution, so if point is between them then there > is no need to check org-at-table-p again. > > org-table-align seemed fast enough for me when I tried the posted > code, but if it's

Re: Bug: Latex-Export does not respect custom latex section hierarchy [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.3/lisp/org/)]

2020-03-29 Thread Nicolas Goaziou
Hello, Lukas Juhrich writes: > Following the manual[1], I wanted to extend `org-latex-classes` to > support `paragraph` as a fourth level instead of enumerating. > However, everything after the third entry in an `org-latex-classes` > entry is ignored. See `org-export-headline-levels' Regards,

Re: :tangle header argument not picked up in #+PROPERTY line or :PROPERTIES: block

2020-03-29 Thread Joost Kremers
On Sun, Mar 29 2020, Berry, Charles via General discussions about Org-mode. wrote: What we really need is an ECM rather than snippets of code. Yes, my apologies. It seems that having more than one `header-arg` line doesn't work properly. The following works: ``` * Header 1 :PROPERTIES:

Re: :tangle header argument not picked up in #+PROPERTY line or :PROPERTIES: block

2020-03-29 Thread Berry, Charles
> On Mar 28, 2020, at 3:00 PM, Joost Kremers wrote: > > Hi list, > > I'm having trouble tangling an Org file. Basically, if I put a =:tangle= > header argument in a =#+PROPERTY= line at the top of the file or in a > =:PROPERTIES:= block under a header, it is not picked up and the code

Re: :tangle header argument not picked up in #+PROPERTY line or :PROPERTIES: block

2020-03-29 Thread Joost Kremers
On Sun, Mar 29 2020, Berry, Charles via General discussions about Org-mode. wrote: On Mar 28, 2020, at 3:00 PM, Joost Kremers wrote: Is this expected behaviour? Am I doing something wrong? IIUC what you did, then yes and yes. This is the accepted idiom: #+PROPERTY: header-args :tangle

Re: :tangle header argument not picked up in #+PROPERTY line or :PROPERTIES: block

2020-03-29 Thread Joost Kremers
On Mon, Mar 30 2020, Joost Kremers wrote: Looks like a bug, right? And while I'm at it, this doesn't work as expected either: ``` #+PROPERTY: header-args :dir /home/joost/tmp/dlpy/ * Header 1 :PROPERTIES: :header-args:python: :tangle out1.py :header-args:python: :session py1 :results

Re: :tangle header argument not picked up in #+PROPERTY line or :PROPERTIES: block

2020-03-29 Thread Ken Mankoff
Header args overwrite. Change python to python+ to append header args. Please excuse brevity. Sent from tiny pocket computer with non-haptic feedback keyboard. On Sun, Mar 29, 2020, 15:42 Joost Kremers wrote: > > On Mon, Mar 30 2020, Joost Kremers wrote: > > Looks like a bug, right? > > And

Re: :tangle header argument not picked up in #+PROPERTY line or :PROPERTIES: block

2020-03-29 Thread Berry, Charles
> On Mar 29, 2020, at 1:13 PM, Joost Kremers wrote: > > > On Sun, Mar 29 2020, Berry, Charles via General discussions about Org-mode. > wrote: >>> On Mar 28, 2020, at 3:00 PM, Joost Kremers wrote: >>> Is this expected behaviour? Am I doing something wrong? >> >> IIUC what you did, then

Re: Org-babel-lilypond always renders full pages

2020-03-29 Thread Jonathan Gregory
Hi On 29 Mar 2020, Oliver Heck wrote: > Hi, > > I am trying to use org-babel-lilypond and basically got it running. > But somehow I always get full lilypond pages back instead of a small > snippet. > This is what I have in my org-file: > > #+NAME: Lilypond > #+BEGIN_SRC lilypond :file test.png

Re: Org-babel-lilypond always renders full pages

2020-03-29 Thread Oliver Heck
Hi Jonathan, that works fine. Thank you! Can I set this as default header somewhere in the org file or will I have to include it to every snippet (I will have a lot of them). Oliver On 30.03.20 01:58, Jonathan Gregory wrote: Hi On 29 Mar 2020, Oliver Heck wrote: Hi, I am trying to use

Org-babel-lilypond always renders full pages

2020-03-29 Thread Oliver Heck
Hi, I am trying to use org-babel-lilypond and basically got it running. But somehow I always get full lilypond pages back instead of a small snippet. This is what I have in my org-file: #+NAME: Lilypond #+BEGIN_SRC lilypond :file test.png \relative c'' { c d e f } #+END_SRC I read through

Re: Org-babel-lilypond always renders full pages

2020-03-29 Thread stardiviner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 You might want to try this: #+begin_src emacs-lisp (add-to-list 'org-babel-default-header-args:lilypond '((:prologue . "\paper{ indent=0\mm line-width=120\mm oddFooterMarkup=##f oddHeaderMarkup=##f bookTitleMarkup = ##f

Re: Org-babel-lilypond always renders full pages

2020-03-29 Thread Oliver Heck
This throws an error: org-babel-exp process emacs-lisp at position 1... org-babel-exp process lilypond at position 480... sort: Wrong type argument: stringp, (:prologue . "paper{ indent=0mm line-width=120mm oddFooterMarkup=##f oddHeaderMarkup=##f bookTitleMarkup = ##f

Bug: Latex-Export does not respect custom latex section hierarchy [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.3/lisp/org/)]

2020-03-29 Thread Lukas Juhrich
Following the manual[1], I wanted to extend `org-latex-classes` to support `paragraph` as a fourth level instead of enumerating. However, everything after the third entry in an `org-latex-classes` entry is ignored. [1] https://orgmode.org/worg/org-tutorials/org-latex-export.html#org09a8ac4