Re: [O] org-src--contents-for-write-back : preserve original major-mode, and avoid mixing tabs and spaces in org-mode buffers

On Sat, Apr 22, 2017 at 1:41 AM, Nicolas Goaziou wrote: > > > The bug is in the `org-src--contents-for-write-back' function. It > > uses a temp buffer. The temp buffer's major-mode is left to be > > the default, which is fundamental-mode, which knows nothing about > > how

Re: [O] ANN: org-sticky-header

On Wed, 19 Apr 2017, Adam Porter wrote: This should now be fixed. Thanks! I have encountered a bug when trying to export a subtree containing an inlinetask just after the headline/metadata and a src block further down. Here is an ECM: --8<---cut

Re: [O] RFC: Extensible Dependencies 'N' Actions

Gergely Polonkai writes: > • Some finders have missing documentation (although their names are pretty > straightforward) Yup, working on that. > • Why the “new language”, why can’t it be lisp, or at least more lispish? Initially, I made it similar to org-depend.el, but as parsing became

[O] set org-attach-directory location per buffer

Hi! i was wondering if one could use perhaps local variables in separate org files to define the location of the attachment folder per file so that for each folder the attachment will be stored in a separate directory thx Z

[O] function-finding-location?

today i saw this in the DOCU (file+function "path/to/file" function-finding-location) A function to find the right location in the file. i assume you dont just use "function-finding-location" but rather a specific function. are there examples for such functions? best Z

Re: [O] org-src--contents-for-write-back : preserve original major-mode, and avoid mixing tabs and spaces in org-mode buffers

Hello, Brent Goodrick writes: > I found a bug in org-mode where emacs-lisp code that is in a > already-indented source block in an org-mode buffer is improperly > indented when editing it via C-c '. Take the following contrived > example emacs-lisp source code: > > 1. Here is

Re: [O] Bug: Canceling a TODO state change does not revert the heading [9.0.5 (9.0.5-elpa @ /home/laurence/.emacs.d/elpa/org-20170210/)]

Hello, Laurence Rochfort writes: >> I disagree. You may want to cancel the message because this change >> doesn't require one, but, yet, want the todo state change. > > I see, that makes sense. > > I notice that supplying an empty message with C-c C-k results in no

Re: [O] Bug: export does not ignore #+INCLUDE if archived or tagged :noexport: Package: Org mode version 9.0.5 (9.0.5-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20170210/)

Hello, Rasmus writes: > Stefan Kredler writes: > >> when archiving sections or exclude them from export I would expect >> them being exempt from being evaluated during export. >> The section archived or marked as ~:no export:~ is still evaluated and there >>