Re: [O] Bug: org-clock-total-time is calculated from midnight in UTC (not in current time zone) [9.1.4 (9.1.4-13-g84cb63-elpa @ /home/yantar92/.emacs.d/elpa/org-20171218/)]

in friendly jest: On 12/21/17, Ihor Radchenko wrote: > intended recipient, you are hereby notified that any use, dissemination, > distribution, or copying of this message, or any attachment, is strictly > prohibited. If you have received this email in error,

Re: [O] Bug: shiftmeta[left|right] on multi line items [9.1.2 (release_9.1.2-40-g6ca906 @ /usr/local/share/emacs/27.0.50/lisp/org/)]

Hello, Nathan Aclander writes: > Now I'm curious, do you have an example list where this would be > obviously confusing and ambiguous? * Headline 1 ** Sub-headline - Plain list - Sub-list - Sub-item [X] If the point is at [X],

Re: [O] Bug: org-clock-total-time is calculated from midnight in UTC (not in current time zone) [9.1.4 (9.1.4-13-g84cb63-elpa @ /home/yantar92/.emacs.d/elpa/org-20171218/)]

Hello, Allen Li writes: > On Thu, Dec 21, 2017 at 5:55 PM, Ihor Radchenko > wrote: >> >> org-clock-in in org-clock.el calculates org-clock-total-time via calling >> (org-clock-sum-current-item (org-clock-get-sum-start)). >> However,

Re: [O] Bug: Editing src blocks: user-error: Cannot modify an area being edited in a dedicated buffer [9.1.4 (9.1.4-2-g118753-elpaplus @ /home/paul/.emacs.d/elpa/org-plus-contrib-20171211/)]

@Paul Do you have similar config? I use it to enable flycheck in editing temp src buffer. (defadvice org-edit-src-code (around set-buffer-file-name activate compile)   (let ((file-name (buffer-file-name)))     ad-do-it     (setq buffer-file-name file-name))) On 12/22/2017

Re: [O] Bug: List does not fold correctly with inline tasks in the middle [9.1.4 (9.1.4-13-g84cb63-elpa @ /home/yantar92/.emacs.d/elpa/org-20171218/)]

I am dumb... Forgot to load 'org-inlinetask 'Ihor Radchenko' writes: > 1. Create the following same org file: > * Test > - blah > - a > - b > - c > *** List folding stops here > :PROPERTIES: > :ID:

[O] Bug: List does not fold correctly with inline tasks in the middle [9.1.4 (9.1.4-13-g84cb63-elpa @ /home/yantar92/.emacs.d/elpa/org-20171218/)]

1. Create the following same org file: * Test - blah - a - b - c *** List folding stops here :PROPERTIES: :ID: 27eb85b6-114f-437f-9424-b28d400f6aa9 :END: *** END - everything here and below folds on tab at =**...END= - f 2. Try

Re: [O] Bug: org-clock-total-time is calculated from midnight in UTC (not in current time zone) [9.1.4 (9.1.4-13-g84cb63-elpa @ /home/yantar92/.emacs.d/elpa/org-20171218/)]

On Thu, Dec 21, 2017 at 5:55 PM, Ihor Radchenko wrote: > > org-clock-in in org-clock.el calculates org-clock-total-time via calling > (org-clock-sum-current-item (org-clock-get-sum-start)). > However, org-clock-get-sum-start returns the time in UTC, which is not

[O] Bug: org-clock-total-time is calculated from midnight in UTC (not in current time zone) [9.1.4 (9.1.4-13-g84cb63-elpa @ /home/yantar92/.emacs.d/elpa/org-20171218/)]

This email may contain confidential and/or proprietary information that is exempt from disclosure under applicable law and is intended for receipt and use solely by the addressee(s) named above. If you are not the intended recipient, you are notified that any use, dissemination, distribution,

Re: [O] Bug: Editing src blocks: user-error: Cannot modify an area being edited in a dedicated buffer [9.1.4 (9.1.4-2-g118753-elpaplus @ /home/paul/.emacs.d/elpa/org-plus-contrib-20171211/)]

Turns out that the issue was caused by trying to disable a flycheck checker using the org edit src hook On Mon, Dec 18, 2017, 6:30 AM Nicolas Goaziou wrote: > Hello, > > Paul Davis writes: > > > Using ~C-c '~ to edit a src block works as

Re: [O] Bug: Tangling python code results in mixed tabs and spaces, incomaptible with python3 [9.1.4 (9.1.4-dist @ /home/ehere/emacs-scripts/org-9.1.4/lisp/)]

Hello, Edmund Christian Herenz writes: > The following python code uses only whitespaces for the different > indentdation levels: > > a_list = ['elem1', > 'elem2', > 'elem3'] > > for elem in a_list: > print(elem) > for char in elem: >

[O] Bug: Tangling python code results in mixed tabs and spaces, incomaptible with python3 [9.1.4 (9.1.4-dist @ /home/ehere/emacs-scripts/org-9.1.4/lisp/)]

The following python code uses only whitespaces for the different indentdation levels: a_list = ['elem1', 'elem2', 'elem3'] for elem in a_list: print(elem) for char in elem: print char I enter this code into a SRC block with #+BEGIN_SRC python :tangle

Re: [O] [BUG] Re: header argument :noweb-ref seems can't be resolved

problem solved, Thanks very much. @Nicolas and @Berry. [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner Twitter: @numbchild Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 Blog: http://stardiviner.github.io/ On Wed, Dec 20,

Re: [O] [BUG] Re: header argument :noweb-ref seems can't be resolved

Hello, "Berry, Charles" writes: > Looks pretty clean. I've not had time to try it out, however. Thank you. OK. I applied it on master. Since there was some differences with maint, I didn't backport it there, though. Instead, I bound `org-babel-current-sourced-block-location'

Re: [O] [BUG] Re: header argument :noweb-ref seems can't be resolved

> On Dec 19, 2017, at 11:00 AM, Nicolas Goaziou wrote: > > Since :noweb-ref is the only property that absolutely needs to be > retrieved from definition, another option would be to write a specific > function for that. > > It implies some duplicated efforts with

Re: [O] [BUG] Re: header argument :noweb-ref seems can't be resolved

Hello, "Berry, Charles" writes: > I guess I was unclear. There are two ways to fix this. > > 1) let bind org-babel-current-src-block-location in > org-babel-expand-noweb-references in the loop that scans for > noweb-ref'ed src blocks. This fixes the bug, but contradicts the >

Re: [O] [BUG] Re: header argument :noweb-ref seems can't be resolved

> On Dec 18, 2017, at 11:31 PM, stardiviner wrote: > > Confirmed. I don't know how to fix this problem, so maybe report to Org-mode > ML is the better way. (I changed the message title by prepend [BUG]) I guess I was unclear. There are two ways to fix this. 1) let bind

[O] [BUG] Re: header argument :noweb-ref seems can't be resolved

Confirmed. I don't know how to fix this problem, so maybe report to Org-mode ML is the better way. (I changed the message title by prepend [BUG]) On 12/19/2017 12:59 PM, Berry, Charles wrote: On Dec 18, 2017, at 9:28 AM, numbch...@gmail.com wrote: Hope someone can help here. OK. I think

Re: [O] Bug: Editing src blocks: user-error: Cannot modify an area being edited in a dedicated buffer [9.1.4 (9.1.4-2-g118753-elpaplus @ /home/paul/.emacs.d/elpa/org-plus-contrib-20171211/)]

Hello, Paul Davis writes: > Using ~C-c '~ to edit a src block works as expected, but if I make > changes and use ~C-c '~ again, I get the error ~Cannot modify an area > being edited in a dedicated buffer~ I need more information. Where do you make changes? In the

[O] Bug: Editing src blocks: user-error: Cannot modify an area being edited in a dedicated buffer [9.1.4 (9.1.4-2-g118753-elpaplus @ /home/paul/.emacs.d/elpa/org-plus-contrib-20171211/)]

Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list.

[O] bug#24791: bug#24791: org-todo-yesterday behaves like plain org-todo (incorrect timestamp)

Hi, interestingly, it hasn't happend to me for a long time now – I assumed that it had already been fixed. I tried again just now and I can no longer reproduce it with Org 9.0.9. / Emacs 27.0.50. Cheers, Jan Am 04.12.2017 um 20:59 schrieb Nicolas Goaziou: > Hello, > > Allen Li

[O] bug#28072: Org Mode Drawer Folds Unexpectedly

Hello Nicolas, Thanks you so much for trying to reproduce my observation. I see the discrepancy that you have uncovered... It seems that to reproduce the problem, the drawer must be inside the body of a headlined section. So, simply adding a headline above the drawer should allow you to reproduce

[O] bug#29722: issues with some function declarations

Glenn Morris writes: > Thanks. I think that will have introduced a compilation warning: > > In end of data: > org-duration.el:448:1:Warning: the function 'org-trim' is not known to > be defined. Indeed! Also fixed. Thank you. Regards,

[O] bug#29722: issues with some function declarations

Thanks. I think that will have introduced a compilation warning: In end of data: org-duration.el:448:1:Warning: the function 'org-trim' is not known to be defined.

[O] bug#29722: issues with some function declarations

Hello, Glenn Morris writes: > Package: org-mode > Severity: minor > > "make check-declare" reports the following issues: > > org/org-compat.el:40:Warning (check-declare): said 'org-table-end' was defined > in unknown file: Malformed declaration > org/org-footnote.el:48:Warning

[O] bug#29722: issues with some function declarations

Package: org-mode Severity: minor "make check-declare" reports the following issues: org/org-compat.el:40:Warning (check-declare): said 'org-table-end' was defined in unknown file: Malformed declaration org/org-footnote.el:48:Warning (check-declare): said 'org-fill-paragraph' was defined

[O] bug#29694: Quoting of consts in org-agenda-custom-commands-local-options

Hello, Glenn Morris writes: > Package: org-mode > > In code like > > (defcustom ... > :type '(const some-constant)) > > it's a mistake to write 'some-constant. > > So I'm guessing that various instances of quoted consts in > org-agenda-custom-commands-local-options are a

[O] bug#29698: missing/empty custom groups

Hello, Glenn Morris writes: > Package: org-mode > Severity: minor > > ox-publish.el defines an "org-publish" group, but nothing uses it. > > org-pcomplete.el defines an "org-complete" group, but nothing uses it. > > org-structure-template-alist uses an "org-completion" group, but

[O] bug#29695: Mistakes in custom :types

Hello, Glenn Morris writes: > Package: org-mode > > The following user options have :types that do not match their defaults: > > org-babel-stan-cmdstan-directory > org-latex-default-packages-alist > org-odt-with-latex > > As a result, customizing them displays "mismatch". Fixed.

[O] bug#29698: missing/empty custom groups

Package: org-mode Severity: minor ox-publish.el defines an "org-publish" group, but nothing uses it. org-pcomplete.el defines an "org-complete" group, but nothing uses it. org-structure-template-alist uses an "org-completion" group, but nothing defines it.

[O] bug#29695: Mistakes in custom :types

Package: org-mode The following user options have :types that do not match their defaults: org-babel-stan-cmdstan-directory org-latex-default-packages-alist org-odt-with-latex As a result, customizing them displays "mismatch".

[O] bug#29694: Quoting of consts in org-agenda-custom-commands-local-options

Package: org-mode In code like (defcustom ... :type '(const some-constant)) it's a mistake to write 'some-constant. So I'm guessing that various instances of quoted consts in org-agenda-custom-commands-local-options are a mistake. Eg (const :tag "scheduled" 'scheduled) etc

Re: [O] Bug: subtree archiving when Archive is not final headline yields bad visibility [8.2.10 (release_8.2.10 @ /usr/share/emacs/25.2+gg1+12/lisp/org/)]

Allen Li writes: > Archiving DOES move point, it's just a question of where it moves > point to. It should not be moving point to the archived heading. > Examples (^ is point): > > * Foo > ** A > ** ^B > ** C > ** Archive :ARCHIVE:... > > Archiving to a

Re: [O] Bug: subtree archiving when Archive is not final headline yields bad visibility [8.2.10 (release_8.2.10 @ /usr/share/emacs/25.2+gg1+12/lisp/org/)]

On Mon, Dec 11, 2017 at 6:10 AM, Nicolas Goaziou wrote: > Hello, > > Allen Li writes: > >> On Wed, Dec 6, 2017 at 12:19 PM, Allen Li wrote: >>> (Can reproduce with Org 9.1.3, submitting with emacs -Q) >>> >>> Using a

Re: [O] Bug: subtree archiving when Archive is not final headline yields bad visibility [8.2.10 (release_8.2.10 @ /usr/share/emacs/25.2+gg1+12/lisp/org/)]

Hello, Allen Li writes: > On Wed, Dec 6, 2017 at 12:19 PM, Allen Li wrote: >> (Can reproduce with Org 9.1.3, submitting with emacs -Q) >> >> Using a file tmp.org: >> >> * Foo >> ** Archive :ARCHIVE: >> *** Test >> :PROPERTIES:

Re: [O] Bug: Inline src block results no longer exported

Hello, "Berry, Charles" writes: > This commit > > --- > commit 5f5d82ed516b7b385a9258271becbfa247e94af3 > Author: Nicolas Goaziou > Date: Tue Nov 21 22:25:17 2017 +0100 > > Remove second pass for macro expansion > --- > > breaks the

Re: [O] bug report: + is not escaped in org-link-escape

Nicolas Goaziou twisted the bytes to say: Nicolas> Hello, Nicolas> dmg writes: >> org-link-escape only replaces space, [, ], and % >> >> but search in google/gmail is replacing + also. >> >> The simplest solution is to add 43 to org-link-escape-chars: >> >>

[O] Bug: Inline src block results no longer exported

This commit --- commit 5f5d82ed516b7b385a9258271becbfa247e94af3 Author: Nicolas Goaziou Date: Tue Nov 21 22:25:17 2017 +0100 Remove second pass for macro expansion --- breaks the processing of inline src block results wrapped as {{{results(=my result=)}}}.

Re: [O] BUG: TODO statistics in parent heading prevent evaluation of TODOs with TRIGGER property

I should probably add that this will require org-depend.el to be loaded. On 10 December 2017 at 17:50, Adrian Bradd wrote: > Hello, > > ECM: > > * Top-Heading with process indicator [/] > > ** TODO Here I invoke org-todo to DONE > :PROPERTIES: > :TRIGGER:

Re: [O] BUG: TODO statistics in parent heading prevent evaluation of TODOs with TRIGGER property

Hello, ECM: * Top-Heading with process indicator [/] ** TODO Here I invoke org-todo to DONE :PROPERTIES: :TRIGGER: 2021-12-03-target(TODO) :END: ** This should be changed to TODO :PROPERTIES: :ID: 2021-12-03-target :END: If you run org-todo on the "Here I invoke org-todo to DONE" headline

Re: [O] bug report: + is not escaped in org-link-escape

Hello, dmg writes: > org-link-escape only replaces space, [, ], and % > > but search in google/gmail is replacing + also. > > The simplest solution is to add 43 to org-link-escape-chars: > >org-link-escape-chars is a variable defined in ‘org.el’. >Its value is

Re: [O] BUG: TODO statistics in parent heading prevent evaluation of TODOs with TRIGGER property

Hello, Adrian Bradd writes: > Please see the patch attached. > > When completing a TODO with a TRIGGER property that has statistics in the > parent headline the trigger would not evaluate because the :position > property in `change-plist' may now refer to the line above

[O] BUG: TODO statistics in parent heading prevent evaluation of TODOs with TRIGGER property

Hi, Please see the patch attached. When completing a TODO with a TRIGGER property that has statistics in the parent headline the trigger would not evaluate because the :position property in `change-plist' may now refer to the line above the original TODO. I have used a marker to avoid the issue

Re: [O] Bug: shiftmeta[left|right] on multi line items [9.1.2 (release_9.1.2-40-g6ca906 @ /usr/local/share/emacs/27.0.50/lisp/org/)]

Nicolas Goaziou writes: > This is confusing because it is ambiguous. The same point could > correspond to a table, multiple lists, and multiple headings, all > reclaiming S-M-left binding. I think I agree with your point that having the S-M-left bindings overloaded by

Re: [O] Bug: shiftmeta[left|right] on multi line items [9.1.2 (release_9.1.2-40-g6ca906 @ /usr/local/share/emacs/27.0.50/lisp/org/)]

Hello, Nathan Aclander writes: > Using ^ as point like you did, what I am expecting to happen is: > > Case 1: > > * Heading > > - foo > - ^bar > second bar line > > M-S-left/right moves > > - bar > second bar line > > left and right. > > Case 2: > > - foo >

Re: [O] Bug: shiftmeta[left|right] on multi line items [9.1.2 (release_9.1.2-40-g6ca906 @ /usr/local/share/emacs/27.0.50/lisp/org/)]

Allen Li writes: > I think what Nicolas is saying is this (^ is point): > > * ^Heading > > M-S-left/right works here. > > * Heading > ^content text > > M-S-left/right does not work here. Let’s assume that it does work > here to be consistent with the feature/bug you

Re: [O] Bug: shiftmeta[left|right] on multi line items [9.1.2 (release_9.1.2-40-g6ca906 @ /usr/local/share/emacs/27.0.50/lisp/org/)]

On Sat, Dec 9, 2017 at 4:41 PM, Nathan Aclander wrote: > > Nicolas Goaziou writes: > >> I don't qualify this as a bug. These commands explicitly work when point >> is at the beginning of an item. Indeed, the sub-item may be arbitrarily >> large,

Re: [O] Bug: shiftmeta[left|right] on multi line items [9.1.2 (release_9.1.2-40-g6ca906 @ /usr/local/share/emacs/27.0.50/lisp/org/)]

Nicolas Goaziou writes: > I don't qualify this as a bug. These commands explicitly work when point > is at the beginning of an item. Indeed, the sub-item may be arbitrarily > large, contain tables... it would be confusing to move the whole > sub-list when its structure

[O] bug#11700: 24.1.50; Bad interaction between BiDi and org-tables

Hello, Eli Zaretskii writes: > Can one of you please provide a short Lisp snippet that generates a > 2x2 Org table and inserts it in a buffer, which I could use as the > basis for the test? That would get me off the ground quicker, since > I'm a very infrequent user of Org

[O] bug#11700: 24.1.50; Bad interaction between BiDi and org-tables

> From: Nicolas Goaziou > Cc: dov.grobg...@gmail.com, 11...@debbugs.gnu.org > Date: Mon, 04 Dec 2017 22:02:00 +0100 > > Eli Zaretskii writes: > > > Such tests can only be run interactively, because bidi reordering is a > > display-time feature in Emacs.

[O] bug#24791: bug#24791: org-todo-yesterday behaves like plain org-todo (incorrect timestamp)

On Mon, Dec 4, 2017 at 11:59 AM, Nicolas Goaziou wrote: > Hello, > > Allen Li writes: > >> On Fri, Dec 1, 2017 at 1:53 PM, Nicolas Goaziou >> wrote: >>> Hello, >>> >>> Jan Böhm writes: >>>

Re: [O] Bug: subtree archiving when Archive is not final headline yields bad visibility [8.2.10 (release_8.2.10 @ /usr/share/emacs/25.2+gg1+12/lisp/org/)]

On Wed, Dec 6, 2017 at 12:19 PM, Allen Li wrote: > (Can reproduce with Org 9.1.3, submitting with emacs -Q) > > Using a file tmp.org: > > * Foo > ** Archive :ARCHIVE: > *** Test > :PROPERTIES: > :ARCHIVE_TIME: 2017-12-06 Wed 12:13 > :END: >

[O] bug report: + is not escaped in org-link-escape

hi everybody, I am running 9.0.10. org-link-escape only replaces space, [, ], and % but search in google/gmail is replacing + also. The simplest solution is to add 43 to org-link-escape-chars: org-link-escape-chars is a variable defined in ‘org.el’. Its value is (32 91 93 37) This

Re: [O] Bug: org-files-list duplicate files [9.1.3 (9.1.3-29-g037db0-elpa @ ~/.emacs.d/elpa/org-20171204/)]

Hello, Renato Ferreira writes: > Investigating an issue I was having with (org-resolve-clocks) that i would > need to resolve the same clock twice, i believe i stumbled upon the > following bug on (org-files-list) (used by (org-resolve-clocks)): > > It gets a list from

[O] bug#28263: bug#28263: bug#28263: 24.5; Org: `C-c LETTER' keys

On Wed, Dec 6, 2017 at 7:23 AM, Drew Adams wrote: > [paraphrased] Org should not suggest user reserved key bindings I agree with you in general. However, when I first started using Emacs for Org mode years ago, I found the documentation very helpful. Furthermore, I did

[O] Bug: subtree archiving when Archive is not final headline yields bad visibility [8.2.10 (release_8.2.10 @ /usr/share/emacs/25.2+gg1+12/lisp/org/)]

(Can reproduce with Org 9.1.3, submitting with emacs -Q) Using a file tmp.org: * Foo ** Archive :ARCHIVE: *** Test :PROPERTIES: :ARCHIVE_TIME: 2017-12-06 Wed 12:13 :END: ** Bar This appears like so with default visibility: * Foo ** Archive :ARCHIVE:...

[O] bug#28263: bug#28263: 24.5; Org: `C-c LETTER' keys

> Could you summarize how you think the situation could be improved in > one or two sentences? > > I think what you are trying to say is, Org mode should make global > key bindings for some commands. No. I'm saying that Org should not suggest that users bind keys that are reserved for use by

[O] bug#28263: bug#28263: 24.5; Org: `C-c LETTER' keys

On Tue, Dec 5, 2017 at 7:15 AM, Drew Adams wrote: > > That's even worse, IMHO. And hardly "as neutral as possible". > > > > Just one opinion. Could you summarize how you think the situation could be improved in one or two sentences? I think what you are trying to say

[O] bug#28263: bug#28263: 24.5; Org: `C-c LETTER' keys

[O] Bug: org-files-list duplicate files [9.1.3 (9.1.3-29-g037db0-elpa @ ~/.emacs.d/elpa/org-20171204/)]

Hello, Investigating an issue I was having with (org-resolve-clocks) that i would need to resolve the same clock twice, i believe i stumbled upon the following bug on (org-files-list) (used by (org-resolve-clocks)): It gets a list from (org-agenda-files) and pushes the open org buffers found

[O] bug#28263: 24.5; Org: `C-c LETTER' keys

> >> Org's manual suggests to bind `org-agenda' to `C-c a', > >> but doesn't bind it by default. > > > > I'm not even sure that's a great idea. I think not. > > > > I suppose it's "legit", as the user, not the Org code, > > would be making the binding. But in my libraries I > > provide binding

[O] bug#27711: bug#27711: 25.2; org-feed gets old news as new from some feeds

Thank you very much for the fix. ;) I can't test it right now, but I will do so in the future. Have a nice day! ;) 2017-12-04T22:22:13+0100 Nicolas Goaziou wrote: > Hello, > > > Fixed. Thank you. > > Regards,

[O] bug#28263: 24.5; Org: `C-c LETTER' keys

Hello, Drew Adams writes: >> > Dunno whether there are actual bindings in Org that correspond to these >> > occurrences in the source code of `C-c' followed by a letter. Might be >> > worth checking. (Bindings of `C-c' followed by a letter are reserved >> > for users.)

[O] bug#28263: 24.5; Org: `C-c LETTER' keys

> > Dunno whether there are actual bindings in Org that correspond to these > > occurrences in the source code of `C-c' followed by a letter. Might be > > worth checking. (Bindings of `C-c' followed by a letter are reserved > > for users.) Possibly these are just vestigial doc indications,

[O] bug#7980: Org links does not allow () - at least http links can contain that

Hello, Lennart Borgman writes: > In `org-make-link-regexps' the characters "()" are excluded in > `org-plain-link-re'. Is not that wrong at least for http links? This is not accurate, but usually Org plain links are used when jolting down notes, as in the following

[O] bug#14910: org-mode `org-open-at-point' doesn't follow id links

Hello, Bastien writes: > Hi Oleh, > > Oleh writes: > >> As the subject says. > > This bug is fixed in upstream Org. You can either install Org > separately or wait for the next stable version to be merged in > Emacs. I'm closing this bug, per the last

[O] bug#28263: 24.5; Org: `C-c LETTER' keys

Hello, Drew Adams writes: > Dunno whether there are actual bindings in Org that correspond to these > occurrences in the source code of `C-c' followed by a letter. Might be > worth checking. (Bindings of `C-c' followed by a letter are reserved > for users.) Possibly

[O] bug#24814: Doc Typo in org-insert-heading

Hello, Benjamin Wiese writes: > The documentation of the function org-insert-heading contains a typo on > line 21 ('ways' instead of 'way'). This documentation can be viewed by > typing: C-h f org-insert-heading. Apparently, the docstring no longer contains the

[O] bug#27711: 25.2; org-feed gets old news as new from some feeds

Hello, Adonay Felipe Nogueira writes: > This was tested with `emacs -Q`. > > 1. In the Lisp Interaction buffer, evaluate: > > (require 'org-feed) > (setq org-feed-alist '(("Blog de Bradley Kuhn" > "http://ebb.org/bkuhn/rss.xml; >

[O] bug#11700: 24.1.50; Bad interaction between BiDi and org-tables

Eli Zaretskii writes: > Such tests can only be run interactively, because bidi reordering is a > display-time feature in Emacs. Is that OK with you? That's better than no test at all in my book, so I'm fine with it, yes. I can use isolation characters instead (if anyone cares to

[O] bug#11700: 24.1.50; Bad interaction between BiDi and org-tables

> Date: Mon, 04 Dec 2017 22:43:12 +0200 > From: Eli Zaretskii > Cc: m...@nicolasgoaziou.fr, 11...@debbugs.gnu.org > > Yes, Emacs implements Unicode 9.0, including the UBA with isolates. Actually, the current development sources and the upcoming Emacs 26.1 already support Unicode

[O] bug#11700: 24.1.50; Bad interaction between BiDi and org-tables

> From: Nicolas Goaziou > Cc: Dov Grobgeld , 11...@debbugs.gnu.org > Date: Mon, 04 Dec 2017 21:27:53 +0100 > > I'd rather preserve structure of Org documents outside of Emacs. So, > `:align-to' is not an option. > > IIUC, I need to replace the

[O] bug#11700: 24.1.50; Bad interaction between BiDi and org-tables

> From: Dov Grobgeld > Date: Mon, 4 Dec 2017 21:35:40 +0100 > Cc: Eli Zaretskii , 11...@debbugs.gnu.org > > The correct Unicode≥6.3 way to do this would be with the unicode isolation > characters. I.e. you would wrap > each of the columns with column

[O] bug#11700: 24.1.50; Bad interaction between BiDi and org-tables

The correct Unicode≥6.3 way to do this would be with the unicode isolation characters. I.e. you would wrap each of the columns with column contents. Does emacs honor these? Should be easy to test. Regards, Dov On Mon, Dec 4, 2017 at 9:27 PM, Nicolas Goaziou wrote: >

[O] bug#28072: Org Mode Drawer Folds Unexpectedly

Hello, Mitch Norcross writes: > * ISSUE: Org Mode Drawer Folds Unexpectedly > > ** Issue Description > > - Org Mode Drawers fold (unexpected) when user attempts to unfold a plain > list item within the drawer after having folded it. > > ** Steps To Reproduce the

[O] bug#11700: 24.1.50; Bad interaction between BiDi and org-tables

Hello, Eli Zaretskii writes: >> Date: Wed, 13 Jun 2012 22:26:35 +0300 >> From: Dov Grobgeld >> >> Imagine you have a buffer with the following logical contents (using the >> convention that capitals are RTL characters). >> >> | abcdef | abc | >> | ABCDEF

[O] bug#24791: bug#24791: org-todo-yesterday behaves like plain org-todo (incorrect timestamp)

Hello, Allen Li writes: > On Fri, Dec 1, 2017 at 1:53 PM, Nicolas Goaziou > wrote: >> Hello, >> >> Jan Böhm writes: >> >>> Symptoms: both org-todo-yesterday and org-agenda-todo-yesterday behave >>> just like normally

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

On 04-Dec-2017, Nicolas Goaziou wrote: > Any 9.X version certainly contains the fix. Using this version of ‘org-mode’: Org mode version 9.1.2 (9.1.2-dist @ /usr/share/emacs/25.2/site-lisp/elpa/org-9.0.9/) I confirm that the display of the report is much better: | Headline

[O] bug#29329: 27.0.50; Missing requirement in org-gnus.el

Hello, Glenn Morris writes: > Speaking for the version in Emacs, apart from org-gnus the warnings are: > > In end of data: > org-irc.el:255:1:Warning: the following functions are not known to be defined: > erc-save-buffer-in-logs, erc-logging-enabled Fixed. Thank you.

[O] bug#29329: 27.0.50; Missing requirement in org-gnus.el

Speaking for the version in Emacs, apart from org-gnus the warnings are: In end of data: org-irc.el:255:1:Warning: the following functions are not known to be defined: erc-save-buffer-in-logs, erc-logging-enabled (I haven't looked at the code.)

Re: [O] Bug in emphasis fontification

On Sat, Dec 2, 2017 at 5:30 PM Nicolas Goaziou wrote: > Hopefully fixed. Thank you. > Yes, I confirm the fix. Thank you! -- Kaushal Modi

Re: [O] Bug: org-attach-directory should be safe [9.1.3 (9.1.3-10-gadfbfd-elpaplus @ /home/ionasal/.emacs.d/elpa/org-plus-contrib-20171127/)]

Hello, Allen Li writes: > org-attach-directory should be safe to set as a file local or > directory local string. > > This allows the user to set a directory local attachment directory for > all Org files in a directory tree recursively. > > I do not believe there are

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

Hello, Ben Finney writes: > On 04-Dec-2017, Nicolas Goaziou wrote: >> Ben Finney writes: >> > How can we test the change, to know whether this bug is resolved? >> >> You can test the latest ELPA release, scheduled for today > > Please

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

On 04-Dec-2017, Nicolas Goaziou wrote: > Ben Finney writes: > > How can we test the change, to know whether this bug is resolved? > > You can test the latest ELPA release, scheduled for today Please state the exact version string, so that we can compare to see whether

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

Hello, Ben Finney writes: > On 22-Aug-2016, Nicolas Goaziou wrote: >> The display for clock reports has been changed some months ago in >> development version. > > Which version contains this change? > >> I think this bug can be closed. > > How can we test the change,

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

On 22-Aug-2016, Nicolas Goaziou wrote: > The display for clock reports has been changed some months ago in > development version. Which version contains this change? > I think this bug can be closed. How can we test the change, to know whether this bug is resolved? -- \ “Instead of

[O] Bug: org-attach-directory should be safe [9.1.3 (9.1.3-10-gadfbfd-elpaplus @ /home/ionasal/.emacs.d/elpa/org-plus-contrib-20171127/)]

org-attach-directory should be safe to set as a file local or directory local string. This allows the user to set a directory local attachment directory for all Org files in a directory tree recursively. I do not believe there are any security issues to enable arbitrary Org files to set

[O] bug#20090: improperly closed

Boruch Baum writes: > Bug report 20090 was perfunctorily closed today: > 1] without the person who performed the action consulting with the bug > reporter; You're free to re-open the bug or create another one if you disagree. For the record, I don't consider this to be a

[O] bug#20090: improperly closed

Bug report 20090 was perfunctorily closed today: 1] without the person who performed the action consulting with the bug reporter; 2] without any discussion for over 2.5 years; 3] with a reason given that demonstrates that the person who performed the action didn't give the action much of any

[O] bug#20090: 24.4: linking to a position within an info node

Closing the bug report.

[O] bug#20090: 24.4: linking to a position within an info node

Hello, Boruch Baum writes: > On 03/12/2015 03:50 PM, Juri Linkov wrote: >>> When the org mode manual discusses creating links, it gives an example >>> of linking to an info node (the self-referencing example is >>> `info:org#External' links). The manual continues, at node

[O] bug#4068: 23.1; M-x org-cdlatex-mode: cdlatex not found

Hello, David Reitter writes: > Selecting M-x org-cdlatex-mode brings up the error message shown below. > This command is also available via a menu, so it should really work > out-of-the-box. As specified in the manual, you need to install cdlatex from

[O] bug#7528: 24.0.50; (org) Visibility Cycling

Hello, "Drew Adams" writes: > The node says: > > `C-c C-k' (`show-branches') > Expose all the headings of the subtree, CONTENT view for just one > subtree. > > But both `C-c C-k' and `show-branches' seem to be undefined in Org mode. > > The doc does

[O] bug#21818: 24.5; org-set-tags-to indentation problems when called programmatically

Nicolas Goaziou writes: > Nicolas Goaziou writes: > >> After a quick glance, I think you are right: invisible characters are >> not treated the same way in both cases. I'll investigate deeper soon. > > Fixed in d5767ad. Closing this bug report,

[O] bug#18877: 25.0.50; org-mode fontification error

Hello, Davor Rotim writes: > GNU Emacs 25.0.50.1 (i686-pc-linux-gnu, GTK+ Version 3.14.4) of 2014-10-26 > > emacs -Q, then (setq org-src-fontify-natively t) and try visiting an org > file with source code blocks, the message "org-mode fontification error" > will appear

[O] bug#28999: 25.3.50; org export : exclude-tags not working with org-export-filter-options-functions

Hello, Kyle Meyer writes: > Michel Damiens writes: > >> Adding : >> >> (defun my-org-export-change-options (plist backend) >> (cond >> ((equal backend 'html) >>(plist-put plist :exclude-tags "NOHTML") >>(plist-put plist

[O] bug#27068: 25.2; org-odt-export-to-odt error when filename contains Chinese chars

Hello, "steven.y...@china-hicloud.com" writes: > When execute `org-odt-export-to-odt` command, if the org filename > contains Chinese, and under Windows 7 OS default encoding GBK. An error > occurs that the zipped obt file's name is not correct. I think we > can

[O] bug#22635: 25.1.50; wrong-type-argument when using org-beamer-select-environment

Hello, Kyle Meyer writes: > Derek Feichtinger writes: > >> When executing C-c C-b (org-beamer-select-environment) in an org beamer >> using the current emacs head (git hash ae928ae), I reproducibly get >> the following >> error and backtrace,

[O] bug#26765: 25.2; org-babel: Inserting list of cons cells fails

Hello, Lucas Groenendaal writes: > Please describe exactly what actions triggered the bug, and > the precise symptoms of the bug. If you can, give a recipe > starting from 'emacs -Q': > > First off, I found a fix for this problem. I wasn't sure how to best > submit

[O] bug#29329: 27.0.50; Missing requirement in org-gnus.el

Hello, Glenn Morris writes: > In org-gnus-store-link: > org-gnus.el:121:49:Warning: reference to free variable ‘gnus-newsgroup-name’ > org-gnus.el:127:42:Warning: reference to free variable ‘gnus-summary-buffer’ > > In org-gnus-follow-link: > org-gnus.el:203:9:Warning: reference

Re: [O] Bug in emphasis fontification

Hello, Kaushal Modi writes: > I believe that the recent fontification rules still need tweaking. > > Here's a MWE: > > = > *bold* > = > > Here's a more detailed version: > > = > *bold* > ^ above does not work > *bold* this works at the time of typing. > But

<    9   10   11   12   13   14   15   16   17   18   >