[O] No syntax highlight in ledger source block

I cannot make it show syntax highlighting in the org-mode ledger block. It is just shown with plain text. But if I bring it to the edit buffer, it displays the syntax properly. Can anyone help me to trace this problem?

Re: [O] Problem with bash arrays from list-valued org-babel :var assignments?

Hello, Keith Amidon writes: > With current org-mode, when I try to execute the following org-babel > block: > > #+begin_src bash :var lst='(1 2 3 4 5 6 7) > printf "%s\n" "${lst[*]}" > #+end_src > > > I get result and the following error in the minibuffer: > >Wrong type argument: listp, 1 F

Re: [O] 6 failing tests on master branch

On Fri, Jun 9, 2017 at 4:05 PM Nicolas Goaziou wrote: > Hello, > > Kaushal Modi writes: > > > Here's a patch rebased off maint (as it's just test and manual change > with > > edits to a backward compatible Tramp syntax). > > LGTM. > > Thank you. > Thanks, pushed to maint, merged to master. --

Re: [O] 6 failing tests on master branch

Hello, Kaushal Modi writes: > Here's a patch rebased off maint (as it's just test and manual change with > edits to a backward compatible Tramp syntax). LGTM. Thank you. Regards, -- Nicolas Goaziou0x80A93738

Re: [O] make test is failing? [ob-fortran stuff]

I see. Thanks. Yours, Christian Kaushal Modi writes: > Turns out the Fortran compiler binary gfortran is part of GCC. Those > fortran tests fail for GCC 4.4.7 but not when using GCC 6.1.0. > > On Tue, Feb 23, 2016 at 3:59 AM Christian Moe wrote: > >> >> I always fail the Fortran tests too, on

Re: [O] 6 failing tests on master branch

On Fri, Jun 9, 2017 at 12:27 PM Nicolas Goaziou wrote: > AFAIU, the function doesn't need to change, but the manual needs to be > updated since, in (info "(org) External links") there is: > > /myself@some.where:papers/last.pdfsame as above > > which is no longer a valid syntax. > He

Re: [O] make test is failing? [ob-fortran stuff]

> "Kaushal" == Kaushal Modi writes: Kaushal> Turns out the Fortran compiler binary gfortran is part of Kaushal> GCC. Those fortran tests fail for GCC 4.4.7 but not when Kaushal> using GCC 6.1.0. All tests pass for me and I'm using gcc-4.7 Best wishes, Colin. -- -- Colin Baxte

Re: [O] Allow #+SETUPFILE to point to an URL for the org file

I have attached the updated patch, rebased to master. On Sun, May 28, 2017 at 3:36 AM Nicolas Goaziou wrote: > This is a good idea. We could even display a read-only buffer with the > contents of the document, using new `org-file-contents'. > > Anyway, this can be done in a different patch. >

Re: [O] 6 failing tests on master branch

Hello, Kaushal Modi writes: > Does org-export-file-uri need to change? Because now > > (org-export-file-uri "/ssh:myself@some.where:papers/last.pdf") > > returns > > "file://ssh:myself@some.where:papers/last.pdf" AFAIU, the function doesn't need to change, but the manual needs to be updated sin

Re: [O] 6 failing tests on master branch

On Fri, Jun 9, 2017 at 12:02 PM Michael Albinus wrote: > Kaushal Modi writes: > > The stronger Tramp file name syntax requires now a method. Something > like "/ssh:myself@some.where:papers/last.pdf". This is backward > compatible with Emacs 25, 24, etc pp. > Thanks for the quick reply! @Nichol

Re: [O] 6 failing tests on master branch

Kaushal Modi writes: > This seems to be related to a tramp file notation change on emacs > master. I don't use tramp, but I heard about it on emacs-devel. Indeed. > Here is a test expression: > > (find-file-name-handler "/myself@some.where:papers/last.pdf" > 'file-remote-p) > > On emacs 25.

Re: [O] 6 failing tests on master branch

On Fri, Jun 9, 2017 at 10:26 AM Kaushal Modi wrote: > This one should be easy to debug since >> >> (org-export-file-uri "/myself@some.where:papers/last.pdf") >> >> is easy to reproduce. Could you investigate where the spurious "/" comes >> from? >> > > Will do. > This seems to be related to a

Re: [O] make test is failing? [ob-fortran stuff]

Turns out the Fortran compiler binary gfortran is part of GCC. Those fortran tests fail for GCC 4.4.7 but not when using GCC 6.1.0. On Tue, Feb 23, 2016 at 3:59 AM Christian Moe wrote: > > I always fail the Fortran tests too, on Mac OS X 10.6.8, though > supposedly there's a Fortran interpreter

Re: [O] newbye questions [the nnir-article-group issue]

>Fran?ois Patte writes: > >> Le 05/06/2017 ? 12:07, Eric Abrahamsen a ?crit : >>> Fran?ois Patte writes: >>> Le 05/06/2017 ? 01:33, Eric Abrahamsen a ?crit : > Fran?ois Patte writes: > >> Bonjour, >> >> Ijust discovered org-mode for emacs and I want to explore the

Re: [O] 6 failing tests on master branch

On Thu, Jun 8, 2017 at 5:10 PM Nicolas Goaziou wrote: > > I remember reading that someone else too saw the fortran errors.. Is it > > because I don't have fortran on my system? > > No, I don't think so. OTOH, I have no idea about where this comes from. > Did little digging, TIL that the gfortran

Re: [O] Problem with bash arrays from list-valued org-babel :var assignments?

On 09/06/17 05:56, Keith Amidon wrote: With current org-mode, when I try to execute the following org-babel block: #+begin_src bash :var lst='(1 2 3 4 5 6 7) printf "%s\n" "${lst[*]}" #+end_src I get result and the following error in the minibuffer: Wrong type argument: listp, 1 This, on

[O] Problem with bash arrays from list-valued org-babel :var assignments?

With current org-mode, when I try to execute the following org-babel block: #+begin_src bash :var lst='(1 2 3 4 5 6 7) printf "%s\n" "${lst[*]}" #+end_src I get result and the following error in the minibuffer: Wrong type argument: listp, 1 This, on the other hand works fine: #+begin_src em