[O] bug#34323: reproducibility: absolute file names in ox-odt.elc

2019-02-04 Thread Glenn Morris
Package: emacs,org-mode Version: 26.1.91 Severity: minor The compiled file ox-odt.elc contains strings that refer to the absolute location of the build directory, through org-odt-schema-dir-list and org-odt-styles-dir-list. For example, in the Emacs 26.1.91 pretest tarfile, it contains

Re: [O] org-today broken

2019-02-04 Thread Samuel Wales
On 1/31/19, Kyle Meyer wrote: > Thanks for the report. I introduced this and a handful of other related > incompatibilities with my port of Emacs's c75f505de. I've reverted the > problematic spots. thank you.

Re: [O] (9.2) Noweb blocks not expanded in Python blocks.

2019-02-04 Thread John Kitchin
The problem may be the name is only two characters long. Try Ahh instead. That works for me. John --- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin

Re: [O] Bug: org-copy-subtree: Invalid function: org-preserve-local-variables

2019-02-04 Thread Abdo Haji-Ali
Updating to the latest org-mode (9.2.1) seems to solve this issue. On Sun, Feb 3, 2019 at 4:40 PM Abdo Haji-Ali wrote: > I just updated emacs to 27.0.50 and I am seeing the exact same error. > I think org-preserve-local-variables is in org-macs which is part of > org-mode source code. > > On

Re: [O] [RFC] Org Num library

2019-02-04 Thread Marco Wahl
Hello stardiviner, >>> Just one idea came to my mind. What about adding an option to restart >>> the numbering at 1 for the first heading in the case when narrowing is >>> in effect? >> >> AFAICT, detecting narrowing changes requires using >> `post-command-hook'. > > Add more things into

[O] (9.2) Noweb syntax not understood in Python blocks

2019-02-04 Thread Emmanuel Charpentier
Seen in `org-mode' version `9.2'. Using `noweb' syntax works OK with `emacs-lisp': ┌ │ #+name: a │ #+begin_src emacs-lisp │ (setq L (append L (list i))) │ #+end_src │ │ #+name: b │ #+begin_src emacs-lisp :noweb yes :exports both │ ;; Lisp version │ (setq L nil) │ (dotimes (i 5) <>)

Re: [O] (9.2) Noweb blocks not expanded in Python blocks : it should be a bug...

2019-02-04 Thread Emmanuel Charpentier
Le lundi 04 février 2019 à 08:11 -0500, John Kitchin a écrit : > The problem may be the name is only two characters long. Try Ahh > instead. That works for me. Indeed. Nice catch ; how did you find this ? Since this doesn't happen with emacs-lisp or Sage, and since nothing in the docs I've read

Re: [O] org-today broken

2019-02-04 Thread Marco Wahl
Hi Kyle, >> Occasionally I like to bend time to see what the agenda would look like >> if another day was current. This can be achieved conveniently when >> solely function "current-time" is the source for the current time. >> >> So I'm all for using the explicit calls to current-time instead of

Re: [O] (9.2) Noweb blocks not expanded in Python blocks : it should be a bug...

2019-02-04 Thread John Kitchin
I doubt it is Python specific, and I don't know why it would work in some places and not others. For me, the two character name does not work in elisp, but 1 or 3 does. I agree that seems buggy. The origin of the problem is here: #+BEGIN_SRC emacs-lisp (list (string-match (org-babel-noweb-wrap)

[O] Commenting in org-mode 9.2.1

2019-02-04 Thread Abdo Haji-Ali
I just updated to the latest org-mode (9.2.1) and noticed that when I press M-; (or call `org-comment-dwim`) inside a `#+BEGIN_SRC emacs-lisp` section, I get the following error message `org-comment-dwim: Wrong number of arguments: (0 . 2), 3` Calling the function outside a source section works

[O] (9.2) Noweb blocks not expanded in Python blocks.

2019-02-04 Thread Emmanuel Charpentier
Seen in `org-mode' version `9.2'. Using `noweb' syntax works OK with `emacs-lisp': ┌ │ #+name: a │ #+begin_src emacs-lisp │ (setq L (append L (list i))) │ #+end_src │ │ #+name: b │ #+begin_src emacs-lisp :noweb yes :exports both │ ;; Lisp version │ (setq L nil) │ (dotimes (i 5) <>)

Re: [O] (9.2) Noweb blocks not expanded in Python blocks : it should be a bug...

2019-02-04 Thread Emmanuel Charpentier
as of today's (20190118) org-plus-contrib, this seems fixed. Quick check : === # Noweb syntax check #+property: header-args:python :session #+property: header-args:sage :session #+name: A #+begin_src sage L.append(i) #+end_src

Re: [O] Commenting in org-mode 9.2.1

2019-02-04 Thread Abdo Haji-Ali
> I cannot reproduce your issue, neither or maint nor on master. Thanks. I was using Emacs 25.2.2. Updating to Emacs 27.0.50 solves this issue. -- Abdo Haji-Ali

[O] Error in Literal Examples manual?

2019-02-04 Thread Lawrence Bottorff
At the bottom of this is a description of adding a `org-store-link` inside of a babel code block edit called with C-c ' , however, it doesn't seem to work with C-c l , although M-x org-store-line does work. Or am I seeing, doing this wrong? Sorry

Re: [O] (9.2) Noweb blocks not expanded in Python blocks : it should be a bug...

2019-02-04 Thread Robert Pluim
John Kitchin writes: > #+RESULTS: > : <<\([^ > : ].+?[^ ]\|[^ > : ]\)>> That regex looks malformed, and will only match strings with 1 or 3 or more characters between << and >>. If someone knows what itʼs supposed to be matching we can fix it. eg it looks like it wants to allow <> Is that

Re: [O] [RFC] Org Num library

2019-02-04 Thread Nicolas Goaziou
Hello, Marco Wahl writes: > If there is interest in that patch, the code could be refined to only > hook into the `post-command-hook' when local numbering of narrowed parts > has been chosen. This is mostly already the case. If local numbering of narrowed parts is inactive, the code executed

[O] Manual available?

2019-02-04 Thread Lawrence Bottorff
Is the latest org-mode manual available as an org file? Is there a github for it somewhere? LB

Re: [O] Error in Literal Examples manual?

2019-02-04 Thread Nicolas Goaziou
Hello, Lawrence Bottorff writes: > At the bottom of this is > a description of adding a `org-store-link` inside of a babel code block > edit called with C-c ' , however, it doesn't seem to work with C-c l , > although M-x org-store-line does

Re: [O] Commenting in org-mode 9.2.1

2019-02-04 Thread Nicolas Goaziou
Hello, Abdo Haji-Ali writes: > I just updated to the latest org-mode (9.2.1) and noticed that when I press > M-; (or call `org-comment-dwim`) inside a `#+BEGIN_SRC emacs-lisp` section, > I get the following error message > `org-comment-dwim: Wrong number of arguments: (0 . 2), 3` > > Calling

Re: [O] (9.2) Noweb blocks not expanded in Python blocks : it should be a bug...

2019-02-04 Thread Nicolas Goaziou
Hello, Robert Pluim writes: > John Kitchin writes: > >> #+RESULTS: >> : <<\([^ >> : ].+?[^ ]\|[^ >> : ]\)>> > > That regex looks malformed, and will only match strings with 1 or 3 or > more characters between << and >>. If someone knows what itʼs supposed > to be matching we can fix it. eg it

Re: [O] Manual available?

2019-02-04 Thread Kaushal Modi
On Mon, Feb 4, 2019 at 11:33 AM Lawrence Bottorff wrote: > Is the latest org-mode manual available as an org file? Is there a github > for it somewhere? > > LB > It's here: https://code.orgmode.org/bzg/org-mode/raw/master/doc/org-manual.org

[O] Possible bug fontifying the terms in numbered description list

2019-02-04 Thread Nick Dokos
Terms in description lists - Term :: definition are given an `org-list-dt' face, but the regex (org.el: l.6307 or thereabouts) does not seem to apply to numbered description lists - in: 1. Term :: definition the Term is given no face at all: is that intentional? Version: Org mode version

Re: [O] meaning for _ (and perhaps ^) temporalily changed

2019-02-04 Thread Rudolf Sykora
Julius Dittmar writes: > Hi Ruda, > > Am 10.12.18 um 11:32 schrieb Rudolf Sykora: >> is there a way to *temporalily* disable the default interpretation >> of _ as a subscript? >> >> I use filenames which include _ , > > how about enclosing those filenames in a pair of = signs to mark the >