[O] drawer handling
If a drawer is associated with and below a table entry is it necessary to hide the drawer's visibility in order to go below the drawer in the original org file and edit entries below that drawer? I'm using org version 8.29 and just using tab doesn't get me below a drawer. --
[O] bug#34323: reproducibility: absolute file names in ox-odt.elc
It's due to the eval-when-compile sections in org-odt-schema-dir-list and org-odt-styles-dir-list. These don't make sense to me. All they do is add the build directory. There is a comment "see make install", but I cannot see what this refers to. No similar variable initializes itself in this way AFAIK. If those sections are removed, does anything stop working?
Re: [O] [PATCH 1/3] org-habit: Add org-habit-scheduled-past-days
Hello, John Lee writes: > OK I guess in fact I'm 1. supposed to attach the patches (?) You can also thread them. > The new thing here since Nicolas reviewed this last year (apart from > applying changes in response to review feedback) is "greying out" > habits that you just did, by applying face 'org-agenda-done when > a habit is scheduled for the future. I applied them in master. Thank you. Could you provide an entry for ORG-NEWS file, too? Regards, -- Nicolas Goaziou
[O] bug#34323: reproducibility: absolute file names in ox-odt.elc
Hello, Glenn Morris writes: > 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 > "/home/nico/work/emacs-26/etc/schema/" and > "/home/nico/work/emacs-26/etc/styles/". > This means the generated elc file is non-reproducible (ie, the contents > change depending on the build directory). > > (Like https://debbugs.gnu.org/34321, issued spotted in > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/emacs.html > ) I'm Cc'ing the author of ox-odt.el as he might have more insight. Regards, -- Nicolas Goaziou
Re: [O] Org mode 9.2 breaks org-edit-special on INCLUDE statement with :only-contents t
Hello, Joon Ro writes: > After upgrading to org 9.2, I found that C-c ' (org-edit-special) does not > work on an INCLUDE statement if it has :only-contents t. > > That is, I can normally visit the subtree with CUSTOM_ID theory in paper.org > if I press C-c ' on the following: > > #+INCLUDE: "./paper.org::#theory" > > but pressing C-c ' on the following gives me this error: "org-open-file: No > match for custom ID: theory" :only-contents t" > > #+INCLUDE: "./paper.org::#theory" :only-contents t > > Looks like parsing the statement was not working -- it seems it is > capturing stuff after ". Fixed. Thank you. Regards, -- Nicolas Goaziou
[O] Org mode 9.2 breaks org-edit-special on INCLUDE statement with :only-contents t
Hi, After upgrading to org 9.2, I found that C-c ' (org-edit-special) does not work on an INCLUDE statement if it has :only-contents t. That is, I can normally visit the subtree with CUSTOM_ID theory in paper.org if I press C-c ' on the following: #+INCLUDE: "./paper.org::#theory" but pressing C-c ' on the following gives me this error: "org-open-file: No match for custom ID: theory" :only-contents t" #+INCLUDE: "./paper.org::#theory" :only-contents t Looks like parsing the statement was not working -- it seems it is capturing stuff after ". Best Regards, Joon
[O] Pushing commits to the Work Git repository
Hi, Is there any policy for pushing commits to the Worg Git repository? I fixed the GitHub paths in file org-outside-org.org, as per the patch attached to this message and would like to contribute it. Best, Rafael >From 1458b431c347fdf53ce84eecc2e2503385e93984 Mon Sep 17 00:00:00 2001 From: Rafael Laboissiere Date: Wed, 6 Feb 2019 16:33:36 +0100 Subject: [PATCH] Transfer maintainership of outshine, outorg, and navi-mode --- org-tutorials/org-outside-org.org | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/org-tutorials/org-outside-org.org b/org-tutorials/org-outside-org.org index 8fe2ae92..b8bc5606 100644 --- a/org-tutorials/org-outside-org.org +++ b/org-tutorials/org-outside-org.org @@ -134,8 +134,8 @@ To sum it up in one sentence: Download =outshine.el= (or clone the github-repo) and copy it to a location where Emacs can find it: -| https://github.com/tj64/outshine | -| git clone g...@github.com:tj64/outshine.git | +| https://github.com/alphapapa/outshine | +| git clone g...@github.com:alphapapa/outshine.git | Use this in your '.emacs' to get started: @@ -323,8 +323,8 @@ works too). You can download the file (or clone the github-repo) here: -| https://github.com/tj64/outorg | -| git clone g...@github.com:tj64/outorg.git | +| https://github.com/alphapapa/outorg | +| git clone g...@github.com:alphapapa/outorg.git | /outorg/ requires Org-mode too, thus should be loaded after Org-mode. Insert @@ -597,10 +597,10 @@ offering a vast amount of possible 'views' at the original-buffer. Download (or clone the github-repos of) the three required libraries -| `navi-mode.el' | https://github.com/tj64/navi | -|| git clone g...@github.com:tj64/navi.git | -| `outshine.el' | https://github.com/tj64/outshine | -| `outorg.el'| https://github.com/tj64/outorg | +| `navi-mode.el' | https://github.com/alphapapa/navi | +|| git clone g...@github.com:alphapapa/navi.git | +| `outshine.el' | https://github.com/alphapapa/outshine | +| `outorg.el'| https://github.com/alphapapa/outorg | and put them in a place where Emacs can find them (on the Emacs 'load-path'). Follow the installation instructions in =outshine.el= and =outorg.el=. -- 2.19.2
