Re: Bug: babel python html export error [9.3.6 (9.3.6-25-g685b2c-elpaplus @ /home/johannes/.emacs.d/elpa/26.3/develop/org-plus-contrib-20200330/)]

Okay, thank you Nicolas. I will let you know if I find something out. Best, Johannes Am Sa., 16. Mai 2020 um 19:06 Uhr schrieb Nicolas Goaziou < m...@nicolasgoaziou.fr>: > Hello, > > Johannes Wasmer writes: > > > I have a very simple test.org file with the content: > > > > #+begin_src python > >

Splitting large org file into smaller ones

Hi there, Is there an efficient way to split a large org file into smaller ones? Lets say I have a master file with the following * Notes ** Candidate A - Strong technical background - High H-factor - good funding - More established investigator - Huge startup need $$ ** Candidate B - low

Using est+ with effort estimate range

Hello, according to the manual, there is a special column type for column view ‘est+’ Add low-high estimates. This is explained later: The ‘est+’ summary type requires further explanation. It is used for combining estimates, expressed as low-high ranges. For example, instead of estimating a

Re: Splitting large org file into smaller ones

On 2020-05-30, at 11:51, Marvin M. Doyley wrote: > Hi there, > > Is there an efficient way to split a large org file into smaller ones? I do not know about "efficient", but you might find my org-one-to-many library useful: https://github.com/mbork/org-one-to-many (Note that I don't wven know i

[PATCH] Fix org-narrow-to-subtree smaller than subtree

I noticed that when I narrow to a subtree and then hit org-mark-element, I can’t kill the text because the narrow is actually 1 char smaller. This seemed like an unpleasant workaround, and I think the behavior can be changed without any real negative consequences. >From 61260469a9ad37ad4011cc489dc

Re: [PATCH] Fix org-narrow-to-subtree smaller than subtree

Oh, of course I attached the wrong patch again. Wish mu4e-compose could preview these. >From 5f7cf68f92d3fa82d01646f7f1e12a4d18bad2fb Mon Sep 17 00:00:00 2001 From: nivekuil Date: Sat, 30 May 2020 00:11:19 -0700 Subject: [PATCH] Make narrowed subtree same size as the subtree, not 1 char less

nondeterministic org-test-with-temp-text?

I’m trying to add a test (which should fail at the moment, representing an org-mode bug), but it seems like each ‘should’ form is actually nondeterministic. The first form returns nil on the first eval and t on subsequent evals, its behavior resetting upon any command, and the second form does the

Re: `with` as a list.

Hi Kyle, thank you for writing back, I have a couple of questions in reply. btw. are you on irc.freenode.net?  I'm `mariotomo' there.  and I just joined `#org-mode'.  I don't think that my terminal will ring a bell if I'm mentioned there. On 30/05/2020 01:22, Kyle Meyer wrote: Mario Frasca

Re: Splitting large org file into smaller ones

On Sat, May 30, 2020 at 6:09 AM Marvin M. Doyley wrote: > Is there an efficient way to split a large org file into smaller ones? > > Lets say I have a master file with the following > > * Notes > ** Candidate A > … > ** Candidate B > … > > How do I export the subtree to separate org files, say

Re: `with` as a list.

On 30/05/2020 09:23, Mario Frasca wrote: The code above looks fine to me.  Another option would be to use number-sequence and then filter out the ind value. no, that would break functionality: I need to keep the given order. ah, no, sorry, you are totally right here.  I'll see if using number-

Re: Splitting large org file into smaller ones

On 30 May 2020, Marvin M. Doyley wrote: How do I export the subtree to separate org files, say - Candidate-a.org - Candidate-b.org I'll throw out an uninformed suggestion of a possible direction: archiving subtrees. I guess you'd have to

Re: `with` as a list.

what's new … edited the documentation string to `org-plot/zip-deps-with', removed some redundancies there, removed my ›zip‹ function, in favour of ›cl-mapcar 'cons‹, simplified the double test `stringp', `string=' with `equal'. simplified the unit tests correspondingly. make test: no unexpec

Re: [PATCH] Fix org-narrow-to-subtree smaller than subtree

Hello, Kevin Liu writes: > Right now a narrowed subtree is one char smaller than the actual > subtree. (org-mark-element) on a narrowed subtree will select a > region 1 char out of bounds, for example. There doesn't seem like a > good reason for this to be the case. There is a good reason for

Re: nondeterministic org-test-with-temp-text?

Hello, Kevin Liu writes: > I’m trying to add a test (which should fail at the moment, representing > an org-mode bug), but it seems like each ‘should’ form is actually > nondeterministic. The first form returns nil on the first eval and t on > subsequent evals, its behavior resetting upon any c

Re: Possible fix for :includes header argument in org-babel C source blocks

I don't know if it's been mentioned in the "issue tracker?" thread, but if I could pick just *one* feature off web-based forges, it'd be automated testing with CI… [...] Automated testing has been a massive time-saver everywhere I've seen it used, though I'm not sure I've ever seen it combined

Re: Splitting large org file into smaller ones

Am 30.05.20 um 17:36 schrieb William Denton: > On 30 May 2020, Marvin M. Doyley wrote: > >> How do I export the subtree to separate org files, say >> >> - Candidate-a.org >> - Candidate-b.org > > I'll throw out an uninformed suggestion of a pos

Re: `with` as a list.

Mario Frasca writes: > btw. are you on irc.freenode.net?  I'm `mariotomo' there.  and I just > joined `#org-mode'.  I don't think that my terminal will ring a bell if > I'm mentioned there. No, sorry, I'm not. > On 30/05/2020 01:22, Kyle Meyer wrote: >> Mario Frasca writes: > >> Two meta-comme

Re: `with` as a list.

Mario Frasca writes: > diff --git a/lisp/org-plot.el b/lisp/org-plot.el > index a23195d2a..c44cca991 100644 > --- a/lisp/org-plot.el > +++ b/lisp/org-plot.el > @@ -156,7 +156,8 @@ and dependent variables." > table))) > ;; write table to gnuplot grid datafile format >

Re: [BUG] recently commits on master branch breaks command 'org-babel-demarcate-block'

> On May 29, 2020, at 7:03 PM, stardiviner wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > > When I have a source block (The "|" represents the point): > > #+begin_src sh :eval no > chrome --remote-debugging-port > | > > #+end_src > > Then press =[C-c C-v d]=, it becomes

Re: `with` as a list.

oops .. you mentioned `cl-loop' and I found it interesting, in particular the de-structuring part. so I rewrote the (dolist (col-with …) …) as (cl-loop for (col . with) in … do …). so I could simplify `(car col-with)' and `(cdr col-with)', then I replaced the `do' with a `collect', so I coul

Re: `with` as a list.

On 30/05/2020 15:25, Kyle Meyer wrote: Could you update this header to match the style used by other tests (see, e.g., test-org-num.el)? apparently, I managed to pick precisely the wrong example! ;;; test-org-clock.el --- Tests for org-clock.el

Re: Splitting large org file into smaller ones

Hi Marvin, I replied to a similar question some time ago, here's my answer (with updated links since the files have changed in the meantime): I do something similar in my ox-leanpub-book module [1], which exports each top-level heading to a different file. The general idea is to use =org-map-entr

Re: `with` as a list.

Mario Frasca writes: > On 30/05/2020 15:25, Kyle Meyer wrote: >> Could you update this header to match the style used by other tests >> (see, e.g., test-org-num.el)? > > apparently, I managed to pick precisely the wrong example! > > ;;; test-org-clock.el --- Tests for org-clock.el Ha, I poked aro

Re: Splitting large org file into smaller ones

Hi Marcin, I appreciate this, I will give it a go. Thanks, M > On May 30, 2020, at 9:13 AM, Marcin Borkowski wrote: > > > On 2020-05-30, at 11:51, Marvin M. Doyley wrote: > >> Hi there, >> >> Is there an efficient way to split a large org file into smaller ones? > > I do not know about "e

Re: Splitting large org file into smaller ones

Cool! I will try this too Thanks Cheers, M > On May 30, 2020, at 6:23 PM, Diego Zamboni wrote: > > Hi Marvin, > > I replied to a similar question some time ago, here's my answer (with > updated links since the files have changed in the meantime): > > I do something similar in my ox-leanpub-b

Re: Splitting large org file into smaller ones

Thanks Bill > On May 30, 2020, at 11:36 AM, William Denton wrote: > > On 30 May 2020, Marvin M. Doyley wrote: > >> How do I export the subtree to separate org files, say >> >> - Candidate-a.org >>

using org mode to help with a construction project

I am still a beginner at org mode - I am looking for ideas or information about how I can use org mode to help me manage a construction project. I have a list of contractors (name, phone, email, etc) that I want to contact - and eventually get bids. Right now I would like to keep track of which on

Re: nondeterministic org-test-with-temp-text?

On 30 May 2020 09:09, Nicolas Goaziou wrote: > You cannot call `org-cycle' consecutively without care, because it > checks `last-command' and `this-command'. You need to fake their values > before calling `org-cycle' again. Good to know, thanks. Relatedly, would you be willing to take a look at

Re: [PATCH] Fix org-narrow-to-subtree smaller than subtree

> There is a good reason for this. If you insert text at (point-max), you > break the following headline. > > OTOH `org-mark-element' should pay attention to buffer boundaries. Good point. `org-mark-element` uses (org-element-property); I wonder if it makes sense to have the actual :end propert

[PATCH] Re: [BUG] recently commits on master branch breaks command 'org-babel-demarcate-block'

Berry, Charles writes: >> On May 29, 2020, at 7:03 PM, stardiviner wrote: >> >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> >> When I have a source block (The "|" represents the point): >> >> #+begin_src sh :eval no >> chrome --remote-debugging-port >> | >> >> #+end_src >> >>

[PATCH v2] Re: [BUG] recently commits on master branch breaks command 'org-babel-demarcate-block'

I updated the patch commit message. From b0bdf52a305cb5f9663ee1dc2d08c5de6c7cb602 Mon Sep 17 00:00:00 2001 From: stardiviner Date: Sun, 31 May 2020 10:59:41 +0800 Subject: [PATCH] fix 5f0a9cca3 missing space * lisp/ob-core.el (org-babel-demarcate-block): replace wrong newline with missing space

[Patch] Add support for geiser-scheme-implementation to lisp/ob-scheme.el

Hello, everyone ob-scheme doesn't seem to be respecting geiser-scheme-implementation, which is a buffer-local variable to specify which implementation in particular to use in an org buffer by default. This 2-line patch adds this support. Please, consider adding it. -- Yours sincerely, Vladimir

Re: Failing tests (was: Possible fix for :includes header argument in org-babel C source blocks)

Kévin Le Gouguec writes: > Kyle Meyer writes: > >> The source for that page is in the worg repo: >> https://code.orgmode.org/bzg/worg/src/master/org-contrib/babel/languages/ob-doc-C.org > > Thanks for the pointer, and for applying the patches! > FAILED ob-tangle/jump-to-org FAILED