[O] patch to keep the level in refile

Hi, This allows to specify via a variable whether org-refile should keep the level of the item when refiling. At the moment, org-refile automatically creates a sub-item at the next level. This causes problems, when the level has semantic meaning beyond defining the hierarchy (e.g., level 3 always

Re: [O] patch to keep the level in refile

Hello, Sebastian Fischmeister writes: > This allows to specify via a variable whether org-refile should keep the > level of the item when refiling. At the moment, org-refile automatically > creates a sub-item at the next level. This causes problems, when the > level has

Re: [O] problems with export and :cache

Hello, Aaron Ecay writes: > If this means “can it ever work?” then I think the answer is “yes it > can”. But I think the current implementation is broken and likely to > remain so for the foreseeable future. The issues are: > > 1. :cache only works for code which is a

[O] [PATCH] org-babel-execute-src-block-region

Hello, I find it useful to be able to execute only a region of a source code block, so I've implemented a new function for that. I've tested it with MATLAB and Python, but it should work for any mode, since it calls org-babel-execute-src-block. Thanks, Carlos From

Re: [O] Filtering properties in agenda view

Thanks for your answer! Unfortunately, it does not work for me as described in the manual. For example I have an entry with the Property "Test" * TODO test SCHEDULED: <2015-11-01 Sun> :PROPERTIES: :CATEGORY: Test :END: C-c am Match: Category=Test I get a buffer that is empty except for the

Re: [O] Filtering properties in agenda view

On Sun, Nov 1, 2015 at 4:04 PM, Georg Otto wrote: > Thanks for your answer! Unfortunately, it does not work for me as > described in the manual. > > For example I have an entry with the Property "Test" > > * TODO test > SCHEDULED: <2015-11-01 Sun> > :PROPERTIES: > :CATEGORY:

Re: [O] patch to keep the level in refile

>> This causes problems, when the level has semantic meaning beyond >> defining the hierarchy (e.g., level 3 always indicates a task while >> levels 2 and 1 are project headings). > > Why don't you simply refile into the parent, then? Because there might not be a lvl 2 heading, but still lvl 3

[O] sh - script: how to control the output.

In the normal shell, I can do: echo '\d wos.wos_papers_by_subject_mv' | psql -h localhost -p 63334 book_citation | grep '[+|]' and get the output: Column | Type | Modifiers --+-+--- id | integer | subject | citext | articles | bigint | When I try this

[O] Org Babel resolution of `:var` value reference inconsistent

Sometime since Org version 8.3beta and now, the way Org Babel resolves the value of the `:var` header argument when assigned to a reference has changed. Previously, the following would work when exporting: --8<---cut here---start->8--- * test #+BEGIN_SRC R

Re: [O] Babel: How to call code in one org file into another org file

On Saturday, 31 Oct 2015 at 16:51, Lawrence Bottorff wrote: > I guess I'm saying that the whole `org-babel-lob-ingest` into > `org-babel-library-of-babel` exercise should make code ready and available. But it does. There are two levels here: the babel codes and the results of the codes. If your