> Please, keep ";; Package-Requires: " version in org.el consistent with
> such statement (Should it be updated for the bugfix branch as well?).
Unfortunately it is not clear that this is the right thing to do because
nearly every feature of org may work on old versions. Should we put
users
on Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Thu, 28 Jul 2022 23:33:22 -0700
Subject: [PATCH] ol-man: Set window point not buffer point and wait before
search
* lisp/ol-man.el (org-man-open): Set window point not buffer point and
wait before search. When passed man:path::SEARCH `org-man-o
. Instead I use sleep-for a shorter time and
process-live-p which gives better results. I think I got the commit
message formats right this time. Best!
Tom
From 2db2ce6d83b27fcf6366183cbd8b5fa79fcbc4a7 Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Thu, 28 Jul 2022 23:33:22 -0700
Subject: [PATCH] ol
Here's a patch to fix the follow behavior for ol-man links so
that the ::SEARCH functionality will actually work. Best!
Tom
From 2c3e3b994fd7b47a6e91d147d2b1f08cd97a1908 Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Thu, 28 Jul 2022 23:33:22 -0700
Subject: [PATCH] * lisp/ol-man.el (org-man
> GNU packages should not steer people towards running nonfree software.
> As a consequence, they should not suggest people donate using payment services
> that _require_ the donor to run a nonfree program.
A slight variant of Ihor's question.
While GNU packages should not steer people toward
f the ob lang impls that can differ wildly in their semantics.
Best!
Tom
thread drafted, will try to get back to it).
Nesting markup inside code or verbatim seems more difficult because
they are intentionally terminal. I am also unfamiliar with texinfo so
will be of no help with the examples, but I do look forward to them.
Best!
Tom
ample
blocks will also lead to confusion because now there are two different ways
to specify what lang a block is. To me the answer should be to just use source
blocks if you need highlighting, example blocks should not highlight at all in
order to make the distinction clear.
Best,
Tom
I can report that with the current changes in the tree
I see some nice performance improvements in files
where I have large numbers of blocks where I modify
a subset of them (beyond a single case where C-u
C-c C-v C-t works) and then retangle the whole file.
Best,
Tom
ature that is being added to
org for 9.6, though one that will be on by default. The evil-search
module doesn't seem to support _any_ of the isearch hooks needed
but while looking into this I think I know generally where it might be
possible to add them.
Thanks!
Tom
> Off topic: Did you report the issue to evil devs?
Not yet. Needed to understand what is going on.
> alternative workaround could be setting org-fold-core-style to
> 'overlays.
Yes! This fixes the issue, and is consistent with my observations
in the other thread (I will respond with more
Confirming fixed. Many thanks!
Tom
stays closed.
Might restoring the invisible overlay text property restore
the old behavior? Is there a reason it was removed?
Best,
Tom
One of the commits between
ffdc508429c58716272743c0e0650bb721fd906a (good) and
67275f4664ce00b5263c75398d78816e7dc2ffa6 (bad)
a change was introduced that broke folding for markdown
blocks. I'm not sure of the exact commit because folding
is completely broken for all the commits in between.
> Can you confirm that you are using the latest version of Org?
I was running a version from back in december due to the evil
search issues I was having. Updating to the latest version
resolves indeed resolves the org-persist issue.
Thanks!
Tom
it will be small?
I think for option 1 to work safely there would need
to be a way to periodically gc remote files, maybe
when another file on that remote was accessed so
an existing tramp connection would be used?
Thoughts?
Tom
inside
folded headings. I had a quick look at the changes but couldn't figure
out why these changes might cause the issue. Best,
Tom
e
org-agenda-skip-additional-timestamps-same-entry is valuable. I rarely want
an entry to display twice on the same day.
Tom Davey
--
Tom Davey
t...@tomdavey.com
New York NY USA
-Original Message-
From: Emacs-orgmode On
Behalf Of Tim Cross
Sent: Tuesday, March 22, 2022 5:10 PM
To: Ihor Radchenk
what changed.
Perhaps the new variable you propose,
org-agenda-skip-timestamps-in-properties-drawer, should default to nil to
preserve the historical behavior?
--
Tom Davey
t...@tomdavey.com
New York NY USA
-Original Message-
From: Emacs-orgmode On
Behalf Of Ignacio Casso
Sent: Monday, Marc
es drawer as follows:
:PROPERTIES:
:Created: <2022-03-06 Sun 22:42>
:END:
Now, in 9.5.2, literally hundreds of entries that formerly appeared on the
built-in Agenda views cannot be easily found.
Regards to all,
Tom
PS The variable 'org-agenda-skip-additional-timestamps-same-entry se
The backward compatibility requirements for org mean that it won't be
possible to replace the existing implementation
for quite a while. That said, I imagine that having optional transient
dispatchers for users on newer versions of emacs would be appreciated.
Best,
Tom
I do not think we can add -shell-escape by default because it
is an arbitrary code execution vector. It might be good to add
a setting in org that would do the right thing without requiring
a user to understand the arcana of latex cli options though.
Best,
Tom
ing removing support for that syntax altogether is
inviting disaster.
Best,
Tom
> character, or the end of line.
Best,
Tom
, that seems like it would require some deeper
tampering/advising of functions. Best,
Tom
https://github.com/SciCrunch/sparc-curation/blame/master/docs/queries.org#L1704-L1707
#+begin_src elisp :results none :exports none
(ow-babel-eval "neru-simplified")
#+end_src
The implementation I use i
. The simplest fix right now would be to prepend your coderef
with the python comment symbols # |hello| so that at the very least it
won't break your tangled files. I would like to see this implemented,
so let's see what Nicolas has to say. Best!
Tom
of the syntax or the implementation. I
think that most of them are trying to ask whether we want to
clearly delineate pure surface syntax from semantics to make the
document easier to understand.
More replies in line.
Best!
Tom
> As for your other comments, you seem to be suggesting a num
Hi Timothy,
I have attached a patch with some modifications and a bunch of
comments (as footnotes). More replies in line. Thank you for all your
work on this!
Tom
> Marking this as depreciated would have no effect on Org’s current behaviour,
> but we could:
>
> Mark as depreci
/emacs-orgmode/2021-04/msg00031.html
Best,
Tom
cases.
Enough for now. Best!
Tom
ot; and of course the only markup
that makes sense for "all backends" is org itself!
Best,
Tom
elisp{(+ 1 2)}@@word!
#+end_src
Which would render to
#+begin_src org
I want a number in this number3word!
#+end_src
Thoughts?
Best!
Tom
--- rambling below -
> This idea reminds me a bit of Scribble/Racket where every document is
> just inverted code, which m
Hi Timothy,
Replies in line. Some things might seem a bit out of order
because I responded from bottom to top. Best,
Tom
> from heading to bed, so to quote Pascal "I have only made this letter
> longer because I have not had the time to make it shorter".
Likewise, and I've
nto understanding what the
unintended consequences would be, so I wouldn't say
that it is irresponsible, I would say instead that it lacks
sufficient rigor and depth to be seriously considered. If you
can add those to this proposal (e.g. in the form of a patch)
then I suspect it would get a much warmer reception.
Best,
Tom
Hi Timothy,
Replies in line. Best!
Tom
On Thu, Dec 2, 2021 at 1:32 AM Timothy wrote:
>
> Hi All (& Nicolas in particular again),
>
> With my recent efforts to write a parser based on
> <https://orgmode.org/worg/dev/org-syntax.html>, I’ve developed a few thoug
exporters how to interpret \emph{hello}world, but trying for
to have any sane behavior for something like
why *hello*world oh no a wild askterisk*
is not worth it.
Best,
Tom
for markdown, but at least it would be a start.
Best,
Tom
Hi Łukasz,
One workaround that is fairly reliable is to prefix the names
of the blocks to be nowebbed with an &. So #+name: block-name
becomes #+name: Then you reference it as
<<>> and the heredoc syntax is broken. Best,
Tom
Hi Timothy,
Thanks for putting this together. Comments in line. Best!
Tom
For reference here is the tokenizer pattern I use in laundry at the moment.
There are a number of issues with it ...
https://github.com/tgbugs/laundry/blob/5a396bef98d9a3cd9ee929f21cd47612dd6cb1ac/laundry/lex-abbrev.rkt
and discovery. I'm happy to keep
using the multi-word term Org syntax, but I have found a practical need to
distinguish the surface syntax from the Emacs major mode to reduce
confusing for technical users. Best,
Tom
PS Another brainstormed name: Orgsyn?
be called org flavored markdown by the existing conventions
in the markdown community. Best,
Tom
des that could leave
files readable to the world.
Best,
Tom
of the behavior along with some gnarly test
cases to ensure that everything works as expected.
Best!
Tom
Ihor Radchenko writes:
> Tom Ed White writes:
>
>> I was able to fix the problem for the time being by changing the
>> arguments to:
>>
>> (defun org-gnus-open (path _)
>>
>> The keystroke I use is C-c C-o, which runs org-open-at-point which is i
Thanks for the pointer! The actual point of contact seems to be
https://github.com/milisims/tree-sitter-org. Good to find another
group that is working on this. Best,
Tom
o deal with nested parsers in tree sitter. I have some ideas about
how it might be done, but nothing concrete (see the linked issue
for more on that).
Best,
Tom
ld set it to the regexp provided in the
original patch? Not sure how much of the implementation in the patch
is dependent on that particular regexp, but a general solution that
could even be set per org file might be a very useful new feature.
Best!
Tom
Some thoughts.
> Maybe you are right and Tom was actually assuming \begin{equation*}, not
> #+begin_export latex.
Correct. My bad on that one.
> Just as Timothy, I believe that \begin{equation*} is unnecessary verbose
> when \[ works *mostly* in a similar way.
\begin{equation*} i
Ihor Radchenko writes:
> Tom Ed White writes:
>
>> Following gnus links in org fails with the message:
>>
>> funcall: Wrong number of arguments: ((t) (path _) "Follow the Gnus
>> message or folder link specified by PATH." (if (string-match
>> &qu
a feature request to org-latex-preview yes?
Best!
Tom
text. I'm not sure there will ultimately
be much we can do about it, but it is worth investigating.
Best,
Tom
is narrowly skirting the syntax to
allow that all to remain a single paragraph, but stick in a newline
anywhere and boom, no more paragraph, no more equation.
I guess one thing I'm missing/not understanding is when/why people
want to use \[ \] instead of full #+begin_export latex block?
Best,
Tom
t I think.
That said, reducing the number of forms as Eric suggests would
be a happy medium.
Best!
Tom
be given to something as important for security
as tangle mode without very careful consideration. Emacs lisp closures
have clear semantics in Org and the number syntax is clear. If users
are concerned about the verbosity of (identity #o0600) they could go
with the sorter (or #o0600). Best,
Tom
Following gnus links in org fails with the message:
funcall: Wrong number of arguments: ((t) (path _) "Follow the Gnus
message or folder link specified by PATH." (if (string-match
"\\`\\([^#]+\\)\\(#\\(.*\\)\\)?" path) nil (error "Error in Gnus link
%S" path)) (let ((group
peeks 1 char ahead for the space, and then starts
parsing again starting with the space. This is because tags MUST be
preceded by a space, so if you incorrectly gobble the space after the
stars then that space cannot be used as the start for tags. Best,
Tom
Bumping this patch for 9.5.
On Fri, Jul 30, 2021 at 8:59 PM Tom Gillespie wrote:
>
> Hi,
>This patch restores the addition of class="org-svg" to svg images
> during html export. Best!
> Tom
re
any definitive conclusions are drawn.
The complexity of the generalized keyword syntax can be seen here
https://github.com/tgbugs/laundry/blob/5a396bef98d9a3cd9ee929f21cd47612dd6cb1ac/laundry/lex-abbrev.rkt#L107-L249
Best,
Tom
but they would
have to be "shadow objects" or something like that?
Best,
Tom
Hi Marco,
You make sense. What you propose to substitute is easier to understand and
concise:
When FULL is non-nil but not t, skip planning information,
properties, clocking lines and logbook drawers.
Thank you!
--
Tom Davey
t...@tomdavey.com
New York NY USA
-Original
all the developers of Org-mode.
--
Tom Davey
t...@tomdavey.com
New York NY USA
. Maybe I misunderstood the original
question, because there is no way that a citation or footnote could be
exported from there, so I think in your conception text that follows
the format of the citations or footnotes isn't actually a citation or
footnote unless it exports as such.
Best,
Tom
is cite: allowed without the square brackets? Either way, org
element just parses the value to a string and it is up to any
consuming application to parse the node property further. Best!
Tom
On Thu, Sep 9, 2021 at 11:45 AM Bruce D'Arcus wrote:
>
> Just bumping this.
>
> Another question
be a mistake to use up
equation/eq and table/tbl or figure/fig prefixes for references that
are internal to org, because it implicitly limits/collides with the
#+link: keyword.
Best,
Tom
Hi Sébastien,
I think you are probably looking for org-sync which implements
exactly this functionality. You would need to write a new backend for
your particular ticketing system, but github, bit bucket, and redmine
backends already exist and can serve as an example. Best,
Tom
https
rt because it
will touch on what ob-lang implementations are able to overwrite
and/or must provide in order to actually function. At the moment there
are practically no constraints.
Lots of work to do here, so grateful for a report on the variability
in the behavior of the existing system.
Best!
Tom
to mitigate the kind of issues Maxim noticed. Best!
Tom
threads and repos. Best!
Tom
python https://github.com/novoid/Memacs
python https://github.com/karlicoss/orgparse
python https://github.com/bjonnh/PyOrgMode
racket https://github.com/tgbugs/laundry/tree/next
racket https://github.com/jeapostrophe/org-mode
racket https://github.com/antoineB/org-mode
See
Hi,
This patch restores the addition of class="org-svg" to svg images
during html export. Best!
Tom
From 4363eec0913ccd0d05ecf3d6346208c62d3597f8 Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Fri, 30 Jul 2021 20:53:07 -0700
Subject: [PATCH] lisp/ox-html.el: Restore org-svg clas
, but changing the docs would be a good first step.
Best!
Tom
Pinging on this to see if anyone can test it so that it can be merged.
Tom
On Wed, Jun 16, 2021 at 4:29 PM Tom Gillespie wrote:
>
> Hi,
>This is a patch that fixes tangling behavior when a block has been
> ingested into the library of babel and then modified. Best!
> Tom
specification for correct behavior. Until we have that spec
we could encourage users to create extensions that implement those
features.
Best,
Tom
PS The other next thing that I am working on might be another way out
for this particular feature request. Namely, it is simplifying and
extending org keyword
a good name for
it, but the objective seems to be something like :tangle-copy-to that
accepts a function returning zero or more paths, or a list of multiple
paths (I don't recall how/whether any of the babel args deal with
accepting multiple values).
Best,
Tom
> That said, I think keeping 2000 lines of source code inside an
> org src block is neither a standard use case nor a reasonable idea.
I would say that it certainly is a standard use case for people who
want to keep everything in a single file (e.g. to simplify
reproducibility and avoid the mess
Hi,
This is a patch that fixes tangling behavior when a block has been
ingested into the library of babel and then modified. Best!
Tom
From 22d0689257f977d09b013a143e899f788b45a039 Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Mon, 14 Jun 2021 19:18:28 -0700
Subject: [PATCH] ob-core
Hi John,
Are you perhaps missing the :extend t directive in the font spec? Best,
Tom
>
Hi Jakob,
Thank you for getting in touch. I had been meaning to after
someone pointed me to your repo in a reddit thread, but you beat me to
it. Replies in line. Best!
Tom
PS ccing this back to the list for the record.
On Tue, Jun 1, 2021 at 1:56 AM Jakob Schöttl wrote:
>
> Hi Tom,
Hi Ihor,
Yes, happy to put my test cases into the org element cases and
visa versa. My long term plan is to come up with a set of test cases
that are unambiguous and potentially ambiguous so that we can
determine the expected behavior in those cases, so this is a great
first step. Best,
Tom
can use racket-mode to parse arbitrary org files, though
you may hit an error and will definitely encounter an
incomplete/incorrect parse since it is still a work in progress. Best,
Tom
that the
tags pattern at the end of the line always parses as tags and doesn't
switch just because the title is empty. Happy to elaborate. Best,
Tom
https://github.com/tgbugs/laundry/blob/next/laundry/heading.rkt
https://github.com/tgbugs/laundry/blob/971cf35683cd60156868c12b070c2dd9e19d8d06/laundry
running, but it likely should not be on by
default.
For a fairly extensive discussion of code execution in org see this
thread from Nov 2020.
https://orgmode.org/list/robi94$ma$1...@ciao.gmane.io/#t
Best,
Tom
> In the end I've set as to nil as a local variable
If you want something a bit more secure you could use a function that
checks the block name ("some-block" in this example). Best!
Tom
(lambda (_lang _body)
(not
(string= "some-block"
(plist-get (cad
A quick fix is to percent encode the troublesome characters, but the
underlying issue is in org-link-any-re which is defined in
org-link-make-regexps which is what org uses to find the next link.
Some improvements might be possible for some of the edge cases there,
but a complete solution for bare
Hi Bastien,
Here's a patch to make it official. :)
Tom
From 3a61289e8fa4442f6d340138dcb67b950e980212 Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Thu, 6 May 2021 23:52:21 -0700
Subject: [PATCH] lisp/ob-calc.el: Add Tom Gillespie as the maintainer
* lisp/ob-calc.el: Add Tom Gillespie
they are done. Best!
Tom
, it is due to the fact that ob-calc makes
stateful modifications to calc. If you want a stateless (idempotent?)
ob-calc block you would need to do something like this as well, and
then you would need an option to discard the additional values instead
of retruning them as I do here. Best!
Tom
diff --git
a specialized result type if it
were implemented. Best,
Tom
On Wed, May 5, 2021 at 8:33 AM wrote:
>
>
> Example
>
> (require 'ob-calc)
> (org-babel-do-load-languages
> 'org-babel-load-languages
> '( (calc . t) )
>
> calc.org
>
> # To e
transporting overlays into the original buffer
has been implemented). Best!
Tom
Hi Greg,
I just checked and it induces a syntax error, which I did not know,
but turns out to be quite useful because it means that an untangled or
incorrectly tangled file will fail to run beyond that point. Best!
Tom
On Sun, May 2, 2021 at 9:11 PM Greg Minshall wrote:
>
> Tom, that is
have headers set via
property drawers separate from regular blocks seems important.
Especially because inline blocks can accidentally inherit header-args
that are incompatible (e.g. :results list). I don't think these
patches depend on that though, so probably better to deal with that
separately.
Best,
Tom
> I see. I imagine the expected behaviour of such a function would be to
> toggle org-inline-src-prettify-results and redisplay?
Yeah, see org-toggle-link-display for inspiration I think.
;;;###autoload
(defun org-toggle-link-display ()
"Toggle the literal or descriptive display of links."
Hi Timothy,
It seems to work more or less as expected. A few comments below. Best,
Tom
1. I think there needs to be a function to toggle
org-inline-src-prettify-results as there is e.g. for hyperlinks. I was
quite confused by the prettified results.
2. I'm also not sure that this approach
Hi Nicolas,
Sorry, I did not mean to imply that such things were not possible
currently. I was writing in the context of how to specify the current
behavior formally. As you point out they absolutely are possible. More
replies in line. Best,
Tom
> This is inaccurate.
>
> The
for this purpose. Having a string escaped
equivalent would be nice, but because it requires more than just a
simple copy/paste into the buffer, it seems like it probably needs
separate notation. Best,
Tom
blob/master/docs/release.org#build-release.
I found this solution while fighting with the font-locking behavior in
shell blocks. Best!
Tom
lists may come back to haunt us here).
Setting org-adapt-indentation to nil by default would be a major step
toward resolving these issues and frankly I couldn't ask for more.
Best!
Tom
PS I have included some notes on the worg/dev/org-syntax.org
file that I wrote while working on the formal grammar
it might can be useful for debug, if someone
is tangling to a large number of files then the filenames/paths are
going to flood messages, so I would leave it out of this patch, and
possibly submit it as another patch for a separate discussion.
Best!
Tom
de effects.
Best!
Tom
0. https://github.com/tgbugs/laundry/blob/next/laundry/parser.rkt note
the upcoming path change (which I will note in the original thread when
it happens).
PS I'm planning to reply to the main thread as well. My short take is
finding a dedicated and responsive maintainer that can
Hi Greg,
seq cannot be used because it is not available in older versions
of emacs that org still supports. When support for those older
versions is dropped then seq could be used. Best,
Tom
then no modes were set). Best!
Tom
On Sun, Apr 18, 2021 at 12:23 AM Sébastien Miquel
wrote:
>
> Hi,
>
> The attached patch modifies the ~org-babel-tangle~ function to avoid a
> quadratic behavior in the number of blocks tangled to a single file.
>
> Tangling an org buffer with 200
101 - 200 of 525 matches
Mail list logo
