[O] Bug: Incorrect/incomplete documentation for org-timestamp-change

2019-05-05 Thread Tim Landscheidt
I wanted to (and did) change a number of timestamps by a constant. So I found (and successfully used) org-timestamp-change which starts with (master): | […] | (defun org-timestamp-change (n what updown suppress-tmp-delay) | "Change the date in the time stamp at point. | The date will be

[O] bug#35453: 26.1; Poor performance of vertical-motion in large org buffer

2019-05-05 Thread Eli Zaretskii
> From: Ihor Radchenko > Cc: 35...@debbugs.gnu.org > Date: Sun, 05 May 2019 09:05:46 +0800 > > > Of course, if someone comes up with ideas how to speed up > > vertical-motion without changing what Org does with overlays and/or > > how overlays are implemented, such ideas will be most

Re: [O] Parens matching off in babel code block

2019-05-05 Thread Marco Wahl
"Fraga, Eric" writes: > On Thursday, 2 May 2019 at 21:11, Lawrence Bottorff wrote: >> Well, at least there is a sane explanation. Ironically, I was also about to >> complain about all my loose ">"s getting flagged. So they are related! >> Would there be a way to make an exception for < and >

[O] bug#34977: org-edit-src-code undesirable behaviour

2019-05-05 Thread Nicolas Goaziou
Hello, pinkanon pinkanon writes: > There are two things that work undesirably for me when using > org-edit-src-code: > (1) With a selected region, the point in the edit buffer will be one line > below the bottom of the selection. > (2) After closing the edit buffer, if it was modified, the

[O] bug#35122: 27.0.50; item nubmers are not maintained when shifting items in org plain lists

2019-05-05 Thread Nicolas Goaziou
Hello, Li Feng writes: > 0. clean start emacs with "emacs -q" > 1. create an org-mode file > 2. enter a few plain list items > 3. use M-S-up/down to move them > 4. observe that the numbers are wrong This is expected. M-S-up/down moves lines around /without taking context into consideration/.

[O] bug#34891: 25.2; ORG-PUBLISH-FIND-DATE should not use Creation/Publish date (#+DATE:) in file as a modification timestamp.

2019-05-05 Thread Nicolas Goaziou
Hello, David Trudgett writes: > Reproduce: > > In an Org mode file, add a #+DATE tag as follows: > > #+DATE: First published: 1 February 2014 > > Then initiate a project publish, which publishes (by default) only > changed files. A date such as the above will not be parsed, so > ox-publish.el

[O] bug#35419: [Proposal] Buffer Lenses and the Case of Org-Mode (also, Jupyter)

2019-05-05 Thread Ihor Radchenko
Dear Dmitrii, > Indirect buffers give the answer to the issue of sharing some textual data > between several buffer. Note that indirect buffers always share *all* the contents with the master buffer. As a result, it may not be easy to make things like flyspell work on code blocks in org-mode, if