| Yes | Final element of
non-final list item |
| dog | No| Final list item and
not contained in a list item |
--
Tom Alexander
lines.
foo
bar* baz
foo *bar \\
baz \\
lorem \\
ipsum \\
dolar* cat
```
Test document TeX-style LaTeX fragments:
```
$foo
bar
baz
lorem
ipsum
dolar$
```
--
Tom Alexander
Thanks!
--
Tom Alexander
On Tue, Aug 22, 2023, at 4:26 AM, Ihor Radchenko wrote:
> Ihor Radchenko writes:
>
>>> I am seeing dual-ownership of the post-blank in the examples below, but at
>>> the same time if I put a plain-list inside a footnote definition, the
>>
> Same here, I'd be tempted to deny Org citizenship to inline tasks: it
> always felt like a nice hack for a niche use-case, but a hack anyway.
>
> If it modifies Org syntax in surprising ways, this is another argument
> for removing org-inlinetask.el from Org's core. Remember: this is not
> to
I've found a bug where inline source blocks cannot be executed and
org-element cannot find/parse them if they are in #+captions: where
the caption is affiliated with a not-inline source block. Example
below. Best,
Tom
Issue present in:
Org mode version 9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1
> org-element-at-point is not supposed to return objects. So, there is no
> problem here.
Right. My original issue description is wrong for this part. It seems that
org-babel-get-src-block-info returns nil when immediately before the start
of the ala |src_ in #+caption: but will return non-nil in
Hi,
Here's a patch to fix the :tangle header behavior when it is
passed a closure that returns nil. Best,
Tom
From f1e15e0634fffed4648aa11628a14e0a68c3b18d Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Tue, 15 Aug 2023 13:46:08 -0700
Subject: [PATCH] ob-tangle.el: restore :tangle closure
> Any other ideas? I'd be happy to see some brain-storming.
Maybe a #+keyword[options]: that doubles as a dynamic block or
something like that?
#+inline_task[options]: TODO some tiny task
#+inline_task[options]: TODO some small task
DEADLINE: <2023-11-11>
:PROPERTIES:
:SOMETHING: or other
:END:
> Thanks for reporting!
> Fixed, on main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=e340dde63
Thanks for fixing!
--
Tom Alexander
Here is a corrected patch that fixes the fact that closures passed to the
:tangle header were not being evaluated. Details in the commit message.
Best,
Tom
On Tue, Aug 15, 2023 at 6:41 PM Tom Gillespie wrote:
>
> After a bit more investigation don't apply this patch because the
I have tested this again against bugfix, the issue is still present
when the cursor is on the s in #+caption: src_. Best,
Tom
After a bit more investigation don't apply this patch because the change
is insufficient to correct another issue.
Specifically org-babel-tangle-collect-blocks must check for and resolve
any closures that are passed to :tangle _before_ testing (string=
src-tfile "no").
As it stands blocks that
Confirming fixed. Many thanks!
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
stays closed.
Might restoring the invisible overlay text property restore
the old behavior? Is there a reason it was removed?
Best,
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
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
f the ob lang impls that can differ wildly in their semantics.
Best!
Tom
> 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
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
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
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
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
around the missing package metadata field, which would cause
a failure when trying to build on emacs < 26 unless org-i-know-what-i-am-doing
or some such is non-nil. The error message would say something along
the lines of "this version of org {org-version} will run on {emacs-version}"
but it is not supported. If you still want to install it, please run
(setq org-i-know-what-i-am-doing t) and then install the package again"
or something like that.
Best!
Tom
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
> 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
. 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
Hi Bastien,
In short, we need two variables due to the case where
a user wants to set nil for all vars and a function for code.
More replies in line. Best!
Tom
> I see nothing in etc/ORG-NEWS that describes this change: am I missing
> something?
Looks like any mention of the change is m
potential
for disruption and our desire to do a good job on the
design of the new system I think it would make sense
to revert the commit from the release so that we don't
rush in trying to fix something under pressure without
taking the time we need to consider all the angles.
Best!
Tom
Hi Max,
Thank you for the feedback. More replies in lines. Best!
Tom
> I am not sure concerning "exactly".
>
> lisp/ob-core.el:248
> `org-confirm-babel-evaluate' is called with 2 arguments. In your patch
> `org-confirm-babel-evaluate-cell' has a single argument.
Y
Looks like string-replace doesn't support that notation,
so both too aggressive and without sufficient control.
I've switched to replace-regexp-in-string which does
what we want.
Here's the updated patch.
From 12ca29965e867acd64fecaecd14f2f74e90d7e99 Mon Sep 17 00:00:00 2001
From: Tom Gillespie
users.
Best!
Tom
From 54e468b60f17b54d81edafd8ee9e22311e519793 Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Sat, 10 Dec 2022 12:11:17 -0800
Subject: [PATCH] ob-core: add org-confirm-babel-evaluate-cell custom variable
* lisp/ob-core.el (org-confirm-babel-evaluate-cell): Added to control
> Please use :package-version and let the mapping be handled by
> customize-package-emacs-version-alist.
Got it. Here's the updated patch (I think I did it correctly?).
From 47a47aa9453a54a4f5f2e9188e2ad072a77c50cb Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Sat, 10 Dec 2022 12
Hi Ihor,
Here's the updated patch using :safe, and an additional
patch for the news entry to make it easier to apply the
core change to bugfix if needed. Best!
Tom
> I am also wondering if we should include this into bugfix.
I can vouch for the fact that trying to work around this in
Here's the rebased patch. It should apply without issue. Best!
Tom
From 5247d2459800f82434f1bc3aeea136c18af7923c Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Sun, 4 Dec 2022 01:02:35 -0800
Subject: [PATCH] lisp/org-expiry.el: Account for org-time-stamp-formats
refactor
* lisp/org
(old-andf args
(list
(and)
(and 1 2 3)
(equal (symbol-function #'and) old-and
> Tom, does not the following allow to achieve the same without your patch?
It works if I have a closed set of things I want to allow but not if I
want to set it to nil
Hi Ihor,
Chiming in here with a slight variant on what
others have said. Best!
Tom
I don't think this should be handled at the syntactic
layer at all. The empty string block language should
be syntactically valid with any special behavior
needed being handled later.
Linters could treat
By the way, while we're on bugfixes. I just noticed that (format "%S" cell)
is being used to create the fake body for info. This is incorrect because
cell is already a string at this point and this makes the behavior
inconsistent with the rest of org babel as a result. Fix below.
One more correction. The source of the issue is that the two values in the
list need to be different, one for the message and one for the actual test.
Best,
Tom
(list "emacs-lisp" cell
'((:eval . yes)) nil (format "%S" cell)
nil nil)
Hi,
Here is a patch that fixes broken tangling during export. I don't have a
simple reproduction, but was able to run git bisect to find the originating
commit. The commit text explains the issue in detail. Best,
Tom
From 0b4e35453874db0acf046e46c571cdef5f39f59a Mon Sep 17 00:00:00 2001
From
> It's purpose is also different.
> I am generally skeptical about our ability to provide universal way to
> judge if a given sexp is safe or not. It should be left to the user.
I am in complete agreement.
> Will it be clear to users what "cell" means in this context?
I assume the language was originally chosen
with tables in mind, but I think it is clear? The
one issue is that using org-babel-confirm-evaluate
doesn't use the word "cell" in the yes-or-no-p prompt.
> Am I wrong that, roughly
multiple versions of the same package. Many thanks!
Tom
Hi,
Here is a patch that improves the ergonomics and thus hopefully
the security for the recent changes to check evaluation for cells. Full
details in the commit message on the patch. Best!
Tom
From da3a88e2919ec5bac6328d55eb99b3352f25b9b4 Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date
> I don't think there is any safe way to install an updated version of
> org-mode other than
I don't know whether it counts as safe, but since I don't see it
mentioned anywhere else in the thread you can do the following.
(require 'package)
(unless package--initialized
(package-initialize))
Here is an updated patch. Best!
Tom
On Thu, Dec 8, 2022 at 3:42 AM Ihor Radchenko wrote:
>
> Tom Gillespie writes:
>
> > Hi,
> >Here is a patch for org-contrib/lisp/org-expiry.el to account for
> > recent changes to org-time-stamp-formats. Best,
> >
Hi,
Here is a patch for org-contrib/lisp/org-expiry.el to account for
recent changes to org-time-stamp-formats. Best,
Tom
PS is this list still the best place to send org-contrib patches?
From 2408e92a9c5e155b55a374462d1314aabbe50fe0 Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Sun, 4
the builtin version of org.
I'm not going to write anything else at the moment because I've just
spent the last 3+ hours trying to deal with this and am in an
extremely uncharitable mood.
Tom
winter/early spring if I had to guess. Best!
Tom
Without wading too far into this at the moment,
timezones are an extremely tricky problem with
a whole bunch of design considerations. I am
reproducing the heading comment from laundry's
timestamp.rkt in its entirety here. Best!
Tom
https://github.com/tgbugs/laundry/blob/master/laundry/grammar
> I strongly disagree. I'd prefer to allow only internationally recognized
> time zone format. Let's not make life harder for Org file parsers.
So offsets and tz database names but no time zone abbreviations?
That seems reasonable since there isn't a sane way to handle the
timezone with dst vs
h precision or ux considerations
because I don't think anyone using org right now is going to be early or
late to their meeting at [3023-01-16 Thu 12:00] (regardless of the timezone).
But org does tell me that it will be a Thursday! Best,
Tom
> Getting the rules and explanation clear is the issue. It's a mistake
> that a great many people make with scheduling meetings. Those two
> behaviors need different encodings because they behave differently.
This is related to why I suggested splitting timezones and offsets into
two separate
> This is because Org is checking if you have any dangling clocks present.
Seems like a reasonable default.
> See org-clock-auto-clock-resolution
Perfect solution for my case. Thanks!
to disable this so that clocking does not
destroy my emacs buffer state by starting org-agenda?
Thanks!
Tom
In short, you cannot nest code in verbatim or verbatim in code
because they are both terminal (end of the line for nesting).
In fact you can't nest anything inside them by their very nature.
Anything inside of them cannot have special functionality, even
escape codes don't play well in that part
Oh boy. In short, I think we can only hope they come up with
LTC and we already have a syntactic space to say whether
our reference seconds are TAI/UTC/LTC/MTC/JTC etc. And
being the privileged squats that we are if the time system is
left out then it means UTC. The friendly thing to do would be
> So I guess the timestamp format and the code which manages them will
> need the ability to use the full TZ name and not just the abbreviated
> form (and I guess an option to allow the user to select). In fact, we
> probably need a way to select between abbreviated/full dynamically as
> well as
(not to mention what
happens if a delay tries to track across a change in timezones).
Best,
Tom
Small bugfix for emacs 25 compat. Best!
Tom
From f04a44e5cc8143fc6cdbbc92b9d2afb76de4a459 Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Mon, 16 Jan 2023 00:25:47 -0500
Subject: [PATCH] fix compat with emacs 25 due using temporary-file-directory
function
* lisp/ob-core.el: org-babel
> The state of our unloading support is not good enough to use it blindly
I have managed to use unload-feature to reload a new version of org
after the builtin version has been previously loaded, but the dance you
have to do to avoid nasty errors (and segfaults if using native comp!)
is about 100
Hi Ihor,
Thank you for looping me in. Best,
Tom
The way I have implemented this is by maintaining an explicit list of
characters that are safe for pre markup and another for post markup.
It is not possible to use unicode punctuation for this because there
are a variety of punctuation marks
> We might probably generalize to
> PRE = Zs Zl Pc Pd Ps Pi ' "
> POST = Zs Zl Pc Pd Pe Pf . ; : ! ? ' " \ [
If this works I think it is reasonable. We might want to
specify what to do in cases where an org implementation
might not fully support unicode, and might want to do a
review of related
The documentation for line breaks says that PRE is:
> Anything but backspace (`\`).
I suspect this is supposed to say "backslash" (ascii 92) not "backspace" (ascii
8)
Link to the documentation: https://orgmode.org/worg/org-syntax.html#Line_Breaks
Thanks for fixing all the documentation issues I submitted today!
On Sat, Jul 22, 2023, at 2:58 AM, Ihor Radchenko wrote:
> "Tom Alexander" writes:
>
>> The documentation for plain links states that PATHPLAIN is:
>>
>>> A string containing non-whites
The documentation for plain links states that PATHPLAIN is:
> A string containing non-whitespace non-bracket (()[]<>=) characters,
> optionally containing parenthesis-wrapped non-whitespace non-bracket
> substrings up to a depth of two. The string must end with either a
> non-punctation
The documentation for Inline Babel Calls mentions that opening and closing
square brackets must be balanced within BODY but the grammar above it only
defines NAME, ARGUMENTS, HEADER1, and HEADER2.
Link to the documentation:
https://orgmode.org/worg/org-syntax.html#Inline_Babel_Calls
The documentation for Citations when specifying which syntactic elements have
spaces between them references a "KEYCITES" syntactic element that does not
appear anywhere else on the page.
Link to the documentation issue:
https://orgmode.org/worg/org-syntax.html#Citations
-blank 4
:post-affiliated 38 :mode planning :granularity nil :parent #2)
#("alpha\n" 0 6
(:parent #3)))
(paragraph
(:begin 48 :end 53 :contents-begin 48 :contents-end 53 :post-blank 0
:post-affiliated 48 :mode nil :granularity nil :parent #2)
#("beta\n" 0 5
(:parent #3))
```
--
Tom Alexander
On August 11, 2023 5:20:08 AM EDT, Ihor Radchenko wrote:
>"Tom Alexander" writes:
>
>> The org-mode documentation states: "With the exception of list items, blank
>> lines belong to the preceding element with the narrowest possible scope. For
>> exam
. Find the contents of that buffer below.
Thank you for the work on Org mode, which is magnificent and
without peer.
Tom Davey
■ Warning (org-element-cache): org-element--cache: Org parser error in
journal.org::18359990. Res
#2)))
(paragraph
(:begin 68 :end 71 :contents-begin 68 :contents-end 71 :post-blank 0
:post-affiliated 68 :mode nil :granularity nil :parent #1)
#("@@\n" 0 3
(:parent #2)
```
--
Tom Alexander
list items org-element
will report the type as written (which is expected) however on export
they are converted to the type of the first occurring item.
So the now-removed sentence might have referred to the org-element behavior.
Regardless, the change is an improvement. Thanks!
Tom
as needed.
Header arguments need to have a single value, so I think
we should split :labels and :label-format, that way users
can also specify :label-format without having to specify
:labels first (otherwise there is ambiguity about what a single
argument :labels means.
Best,
Tom
> I think that we can take names from the parser internals:
I had a similar thought immediately after I sent my previous email.
> :number-lines
> :preserve-indent
> :retain-labels
> :use-labels
> :label-fmt
I thought that we might be able to combine :retain-labels
and :use-labels, but now
Hi,
Here is a fix for bad init values for org-babel-tangle-lang-exts.
Details in the patch commit message.
Best,
Tom
From 71558cc80181b5d7a1d720785165b358984284e3 Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Fri, 28 Jun 2024 14:08:08 -0700
Subject: [PATCH] initialize org-babel-tangle
org-mode/commit/6bcb99413e18324367fa27f8572955d5a92092ce
Got it. Will keep an eye on this. Thanks!
Tom
information does other org-based blogging software use as labels?
Thanks,
Tom Breton (Tehom)
*** Footnotes
[fn:1] My change consists of
* a patch at http://www.panix.com/~tehom/my-code/gblogger.el.diff
* It sent it to T V Raman, so maybe it will be in the next g-client.
* a new file
On Fri, Mar 19, 2010 at 1:00 PM, Martin Stemplinger mstemplin...@gmx.de wrote:
Hi all,
I currently think if I should buy a new smartphone but of course I need
support for org-mode ☺. Now
there is mobileorg for the iPhone and a port to Android.
I tend to prefer an Android phone but would
Tom Breton (Tehom) te...@panix.com writes:
Any interest in trying this out? I can push it if anyone else wants to
try it out.
I'm interested! Please let me know where I can read some code.
Thanks :)
I pushed it just now; it's on branch stow-design. Here is a little
documentation
(which is stand-alone) or all of
emtest, I can certainly include it. Since you seem to have chosen ert, I
don't know what you want in this regard.
Tom Breton (Tehom)
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies
* Now the doc section of this file contains this item
* Finish writing it (a moment from now) and update.
So I've added to a document while just dealing with notes, and
crucially, I can retract individual notes that become obsolete.
Take care,
Tom Breton (Tehom
one by one) or you have to
do extra work to group them. If they're in file, you can run every
test in a package with `rtest:library'. The other really convenient
way to run a test is rtest:defun-at-point.
If we can, would we loose quality/speed of tests?
Not at all.
Tom Breton (Tehom)
PS
-update-all-dblocks' didn't seem to work in
org-export-preprocess-hook because the working buffer isn't yet in
org-mode when it's called, but works in the new hook.
Tom Breton (Tehom)
*** old-org-exp.el 2008-12-18 18:26:05.0 -0500
--- org-exp.el 2008-12-29 23:10:46.0 -0500
on the y-axis, and column 1 is
plotted on the x-axis. [...]
You might want to accept column names as well as column numbers.
Tom
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http
that
comment aligned with the regexp.
Made `org-set-regexps-and-options' also process
`org-todo-blockage-keywords'.
Changed the behavior of org-todo and org-depend-block-todo as described
above.
Tom Breton (Tehom)
*** org-depend.el 2008-12-18 18:26:05.0 -0500
--- new-org-depend.el
, and
it could also show up in other languages like C.
What would be safer? [...]
Perhaps it would make sense to let the syntax vary by source language.
Like, elisp could have something like ;;((def))\n and C something like
/*((def))*/.
Tom Breton
ids and the links work in org,
however html export gives me the following html snippet:
div id=outline-container-1.1 class=outline-3
Looks like the problem is that it is html-escaped because it's the headline.
I actually think this is the right behavior.
Tom Breton (Tehom
Hi Tom,
I am hesitant to apply this relatively complex patch which
I have not had the time to study closely enough.
I am wondering: Instead of setting a TODO keyword,
would it not be simpler and equally effective to set a
special tag when an entry is blocked?
That is a much better
thing with
the variables that trigger time stamp and note recording.
Right. I had already planned to let the hooks to nil; I will do the
same for the time stamp and note recording variables.
Thanks for the advice. I will code it up and send it.
Tom Breton (Tehom
Hi Tom,
this looks awesome.
Right now I am stabilizing everything to make my final release
for Emacs 23.1, so it may be a week or two before I get to
integrate this.
Understood.
Also, I am interested in the testing environment, and what
you made here may end up to be enough to establish
Hi Tom,
[...]
WIth you patch, we have right now
CHOOSEas the prefix
choseness as the interpretation
org-decision as the name of the module.
My request would be to maybe use `choose' also as the
interpretation symbol, or, alternatively, CHOSENESS
as the prefix.
Yes. I think choose
format you like (or send it it me) and we wil publish it there.
OK, I've add comments, keywords, and some docstrings I forgot to
org-choose.el, and I wrote a standalone doc. Both are attached.
Tom Breton (Tehom)
docs.org-choose.el.diff
Description: Binary data
docs.org-choose-docs.org
On Tue, Feb 10, 2009 at 8:44 AM, Tom Breton (Tehom) wrote:
[...]
OK, I've add comments, keywords, and some docstrings I forgot to
org-choose.el, and I wrote a standalone doc. Both are attached.
This is very intriguing functionality. I tried to follow your and
Casten's
earlier exchanges
couldn't reproduce this. Is this on the same test file as before?
Tom Breton (Tehom)
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Hmm, not sure if I messed up there - so I fixed this bug. Tom,
please check if I did this right.
- Carsten
Hi, Carsten. I just looked at org-6.22b
You caught a problem, but I think it's a different bug. I think there
are these different things:
* What you saw, that it doesn't work
On Tue, Feb 10, 2009 at 2:42 PM, Carsten Dominik wrote:
On Feb 10, 2009, at 9:46 AM, Manish wrote:
On Tue, Feb 10, 2009 at 8:44 AM, Tom Breton (Tehom) wrote:
[...]
OK, I've add comments, keywords, and some docstrings I forgot to
org-choose.el, and I wrote a standalone doc. Both
401 - 500 of 530 matches
Mail list logo
