Even if this did work for plain lists it won't work for headlines
because headlines have an arbitrary number of stars and thus it is not
possible for the grammar to know what is a sub-headline vs "the next
headline". For a similar reason I'm fairly sure that the sublist
approach will not work due t
Here is an attempt to clarify my own confusion around the nested
structures in org. In short: each node in the headline tree and the
plain list tree can be parse using the EBNF, the nesting level cannot,
which means that certain useful operations such as folding, require
additional rules beyond the
The image is a bit off center no?
On Mon, Oct 26, 2020 at 1:27 PM TEC wrote:
>
>
> Eric S Fraga writes:
>
> > On Monday, 26 Oct 2020 at 14:54, Daniele Nicolodi wrote:
> >> - (minor) I would add a background to the example in the home
> >> page to
> >> make it stand out more as an example org-mod
I started writing down Org's grammar as an EBNF (with Racket's #lang
brag) on Saturday. There is indeed a layer of Org grammar that can be
implemented via EBNF, but it is fairly minimal. You can identify
headlines, but you can't identify nesting level; the arbitrary nesting
depth means that you hav
> which Ruby org-mode parser does Github use?
I'm pretty sure that github uses https://github.com/wallyqs/org-ruby.
It is ... not compliant, shall we say. I have making some fixes to the
footnote parsing section on my todo list, but I don't expect to get to
it any time in the near future.
Tom
Hi Greg,
Great question. This came out a bit longer than I anticipated since I
wrote up a couple of relevant workflows. Sync between org source
blocks and tangled code is something that I think needs improvement. I
have covered the difference in semantics between tangled code and
babel evaluated c
A vote for A from me. I think that using the light background for the
section above the fold fits better with the color themes of the other
pages and will make the transition less jarring. Best!
Tom
On Thu, Sep 24, 2020 at 9:20 AM TEC wrote:
>
>
> An update.
>
> 1. We have a volunteer for a Japan
ere (though I guess you never know). Thank you
for tracking this down, and now I know how to add ert tests for things
like this in the future! Best,
Tom
On Tue, Sep 15, 2020 at 12:21 AM Kyle Meyer wrote:
>
> Tom Gillespie writes:
>
> > Hi,
> >The 9.4 release has a bug whe
Hi,
The 9.4 release has a bug where it will only tangle the first noweb
reference on a line.
This is also present at 9c31cba002a1ba93053aebea1f778be87f61ba06. It happens in
emacs-27 and emacs-28. The reproduction is below. Best!
Tom
The expected content of oops-3.el should be 1 2 1, but is inst
Hi Vladimir,
I have encountered similar issues with wanting to have a racket
#lang line included in a tangled block while also allowing org to know
exactly which #lang it is working with. I haven't found a good
solution. One issue with embedding the shebang when editing a buffer
is that it is ve
Hi Matt,
Looking good here. Thanks!
Tom
On Wed, Sep 9, 2020 at 12:06 PM Matt Huszagh wrote:
>
> Tom Gillespie writes:
>
> > [...] I have a number of use
> > cases that I can imagine would benefit greatly from being able to
> > define a :header-args: :header (lamb
Great, thank you. Also handy to see the "right" way to traverse up the
tree. Best!
Tom
On Sun, Sep 6, 2020 at 9:52 PM Bastien wrote:
>
> Thanks Tom for the feedback.
>
> >> - org-babel-exp-process-buffer
> > Yes
> >> - org-babel-ref-resolve
> > Probably not?
> >> - org-babel-expand-noweb-referenc
Hi Timothy,
Based on the available relationships Org mode is almost certainly
a https://schema.org/SoftwareApplication that is a
https://schema.org/softwareAddOn of https://emacs.org as well is in
https://schema.org/applicationSuite https://emacs.org. There are a
number of other properties that
Hi Bastien,
My initial reaction was to say yes to all of these in the name of
consistency, but there are nuances for org-babel-ref-resolve and
org-babel-expand-noweb-references that are different than for
org-babel-exp-process-buffer. If I have a block that nowebbs in
another block, and at some
getting this in! Best,
Tom
On Sat, Sep 5, 2020 at 8:45 PM Kyle Meyer wrote:
>
> Tom Gillespie writes:
>
> > Hi Kyle,
> > Following up in this thread having investigated the impact of coderefs.
> > My conclusion is that coderefs need to be stripped out before they are
>
o the second example). Best!
Tom
On Sat, Sep 5, 2020 at 10:00 PM Bastien wrote:
>
> Thanks for weighing in into this discussion.
>
> Tom Gillespie writes:
>
> > I have a number of use
> > cases that I can imagine would benefit greatly from being able to
> >
Hi,
One comment on this patch right now is that =errors= should probably
be changed to =error= for consistency with the slime nomenclature and
with the fact that all the rest of the options for the :results header
are singular nouns.
I also wanted to chime in here with a note that this seems to f
I think making the behavior of default arguments consistent with
regular arguments is probably a good thing. I have a number of use
cases that I can imagine would benefit greatly from being able to
define a :header-args: :header (lambda () "yay!") property as a
closure (and actually I assumed that
Hi Gabriel,
This seems like it is probably a bug given that everything else
about archive headings
is disabled. In the meantime, depending on how many blocks you are
dealing with you
could hack around this by using the following header argument.
#+header: :tangle (unless-archived "/ssh:host:/pat
included a patch against maint that reuses the let block
from org-babel-execute-src-block to accomplish this.
Best!
Tom
From dfb8eee9901a0fe4bd933911386f69863785a15b Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Fri, 4 Sep 2020 20:35:03 -0700
Subject: [PATCH] lisp/ob-core.el: org-babel-check
,
Tom
On Tue, Sep 1, 2020 at 11:07 AM Tom Gillespie wrote:
>
> Hi Timothy,
> Thank you for all your work on this! A couple of suggestions. When
> the dimensions of the browser window become too narrow the links in
> the header move to the hamburger menu. This seems like it is
Hi Timothy,
Thank you for all your work on this! A couple of suggestions. When
the dimensions of the browser window become too narrow the links in
the header move to the hamburger menu. This seems like it is quite bad
for discoverability. Is there a way that the other sections could be
concaten
required.
* Use the code
:PROPERTIES:
:header-args:python: :prologue "<>"
:END:
#+name: python-helper
#+begin_src python
asdf = lambda : 'result'
#+end_src
#+begin_src python :noweb yes
return asdf()
#+end_src
On Fri, Aug 7, 2020 at 9:20 PM Tom Gillespie wrote:
>
>
Hah, this is what I get for not reading carefully enough. I wonder if
it is possible to stick <> in the prologue and have it
expand.
On Fri, Aug 7, 2020 at 9:18 PM Tom Gillespie wrote:
>
> I don't see a direct answer to the original question in the thread, so
> here is an ex
I don't see a direct answer to the original question in the thread, so
here is an example of how I do it taken from
https://raw.githubusercontent.com/SciCrunch/sparc-curation/master/docs/developer-guide.org.
You can ctrl-f for racket-graph-helper to see the relevant blocks. A
reduced version is bel
get the expanded version of the body passed to
org-confirm-babel-evaluate asap with as few disturbances to the rest
of the code base as possible. Best!
Tom
On Tue, Jul 21, 2020 at 9:20 PM Kyle Meyer wrote:
>
> Tom Gillespie writes:
>
> > On Sun, Jul 19, 2020 at 2:13 PM Ky
Hi Kyle,
Thank you for the feedback. In short if modifying (nth 1 info) in place won't
cause a problem then I think it is the way to go. Details below. Best,
Tom
On Sun, Jul 19, 2020 at 2:13 PM Kyle Meyer wrote:
>
> Tom Gillespie writes:
>
> > This is a patch to imp
Hi George,
I took a glance at your additions, nothing jumps out as being problematic. I
have been using wallyqs ob-racket (https://github.com/wallyqs/ob-racket) for
about 4 years because it has support for specifying the #lang in the header,
and I seem to recall that there were some other feature
!
Tom
From 6d069f9532f44ee9fbc1a0ebdaadcc2eb807f8ec Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Mon, 13 Jul 2020 12:04:18 -0700
Subject: [PATCH] lisp/ob-core.el: pass expanded body to
org-confirm-babel-evaluate
* lisp/ob-core.el (org-babel-get-body-to-eval): New function extracted
from org
Hi André,
C-c C-v C-t is the default tangle binding, C-c C-c will execute
the block (and resolve any noweb references if the :noweb header is
set) but will not tangle it.
Two references are
https://orgmode.org/manual/Extracting-Source-Code.html and
https://orgmode.org/manual/Evaluating-Code-Blo
(path) (browse-url (concat "https:" path
("mailto" :follow
(lambda (path) (browse-url (concat "mailto:"; path
("news" :follow
(lambda (path) (browse-url (concat "news:"; path
Hi all,
Sorry to be late to this thread (and for a wall of text), but as a
heavy user of ob-shell I wanted to chime in. First a disclosure, I
would be very unhappy if option 1 were selected, it would require me
to make a whole bunch of changes and try to find an option to revert
to the current
s
use case, but I guess that can wait. Thus, definitely ok to ignore
this patch. Best!
Tom
On Sun, Feb 16, 2020 at 8:16 PM Kyle Meyer wrote:
>
> Hi Tom,
>
> Tom Gillespie writes:
>
> > Hi all,
> > After hours of frustration ending in a realization that I should re
work is needed. Thanks!
Tom
From 362a45ff172af3f49050964aa8534d11374934ca Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Sun, 16 Feb 2020 19:21:16 -0800
Subject: [PATCH] org-src: Add option to restore window configuration after
edit
* lisp/org-src.el: Add an option to restore the previous
Great thanks!
On Thu, Jan 9, 2020 at 8:50 AM Nicolas Goaziou wrote:
> I removed this since you have signed FSF papers.
Got it, I'll leave it out in the future and add a note in
org-contribute.org in case someone
else missed the implication of that paragraph.
Hi,
This is a tiny change to the manual to account for the change from org
-> ol in the org-man example. There may be other references in the
manual that have similar issues but I did not check.
Tom
From b2b8088f958379552f5c9dc228dcda56b7e6f738 Mon Sep 17 00:00:00 2001
From: Tom Gillespie
D
From 8c36ffa82c138057a03c813aa0c7616f04744a72 Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Wed, 11 Dec 2019 17:57:47 -0800
Subject: org.el: Fix verbatim block fontification to end blocks on headlines
* lisp/org.el (org-fontify-meta-lines-and-blocks-1): Enhance regex
for finding the end of blocks (i.e., `b
Adam Porter writes:
> May I recommend using the rx macro for regexps? They are much easier
> for humans to parse, which helps reduce errors like the ones mentioned
> here. And they are about to gain some very useful new features
> in Emacs 27.
Yep. I'll switch the regex in over to use rx.
An
Thank you very much for the feedback. I will make the additional fixes
against maint along with the changes for clarity and send them along
tomorrow. Additional replies in line. Best,
Tom
On Thu, Dec 12, 2019 at 12:40 AM Nicolas Goaziou wrote:
>
> Hello,
>
> Tom Gillespie writes
blocks are not. There is nothing to match, is there?
[1] Bug: headlines escape blocks:
https://lists.gnu.org/archive/html/emacs-orgmode/2019-12/msg00133.html
From 531eac23e22b5b8b16f2747bbd5c1bd43fcbe43b Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Wed, 11 Dec 2019 17:57:47 -0800
Subject:
at 3:12 AM Nicolas Goaziou wrote:
>
> Hello,
>
> Tom Gillespie writes:
>
> > * Description
> > Headlines are not ignored inside of blocks when the headline is not
> > indented.
> >
> > * Affected versions
> > 9.1.9, 9.3
> >
> > *
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
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
--
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
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
--
201 - 243 of 243 matches
Mail list logo
