It's been a while since my question on this mailing list about block
boundaries [1]. For my private code I came up with the function below
to both get and test on all sorts of block boundaries. Like this:
(and-let* ((element (or element (org-element-at-point)))
;; returns nil if p
e007831a35b5d Mon Sep 17 00:00:00 2001
From: Jens Schmidt
Date: Sat, 26 Apr 2025 21:33:46 +0200
Subject: [PATCH] Improve support for weekday-less timestamps
* lisp/org.el (org-ts-regexp1, org-timestamp-formats): Doc fixes.
(org-timestamp-change): Test for presence of optional groups befo
Suppose my cwd is at the top-level of the Org Git repo.
- How would I byte-compile a single Org source? Any make target
available for that?
I use this to byte-compile "org.el" after changes:
~/work/emacs-master/src/emacs --batch -L lisp --eval '(byte-compile-file
"lisp/org.el")'
but
[ Readding tomás since this thread got more high-level again ... ]
On 2025-04-20 13:27, Ihor Radchenko wrote:
> Looks reasonable.
Thanks. More or less by chance I let Org's ERT tests run with
`org-timestamp-formats' set to `("%Y-%m-%d" . "%Y-%m-%d %H:%M")'.
(I do not intend to do anything like
Bump ...
On 2025-03-21 22:42, Jens Schmidt wrote:
> [Moving to emacs-orgmode - I hope it is OK to keep tomás on CC.]
>
> Hi Ihor,
>
> the following statement of yours on emacs-devel caught my eye:
>
> On 2025-03-03 19:31, Ihor Radchenko wrote:
>
>> FYI, weekd
[Moving to emacs-orgmode - I hope it is OK to keep tomás on CC.]
Hi Ihor,
the following statement of yours on emacs-devel caught my eye:
On 2025-03-03 19:31, Ihor Radchenko wrote:
> FYI, weekday is optional. It also adapts to the language settings.
What exactly do you mean by "optional" here?
On 2025-01-18 12:38, Ihor Radchenko wrote:
> Ship Mints writes:
>
>> Yes, could do, and nothing needed by org-mode or markdown-mode. Could also
>> test for buffer-file-name nil. Or test both. Let's recommend that simpler
>> approach and I will rescind my markdown PR in favor of this simpler
>> s
Minor copy-and-paste issue: The language code for "See figure" is
still on "et", not "de".
Plus minor consistency issues: The ordering of the language codes
"de" => "et" is not always consistent. If that bothers you ...
On 2024-10-05 17:13, Philip Kaludercic wrote:
>
> Hi, I have noticed that
Open the following Org mode document in a "make vanilla" Emacs:
- snip -
* foo =bar= baz
* FOO BAR BAZ
[[*foo =bar= baz][Link Title]]
- snip -
For me that document renders like this:
---
The following sequence of commands:
make vanilla
M-x org-mode RET
M-x erase-buffer RET SPC
M-: (setq org-adapt-indentation 'headline-data)
M-x org-indent-line RET
results in:
Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
org-indent-line()
funcall-
On 2023-11-27 21:30, Ihor Radchenko wrote:
> Fixed, on main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=6d7c7917a
Which is currently my HEAD, and there are still edge cases that do not
seem to be handled well.
Start off from "make vanilla" and the following buffer
--
Triggered by a recent question here on `org-in-src-block-p' and a
current need: Is there a function already available that returns
the *inner* boundaries of an arbitrary block element?
For the element corresponding to the block below:
#+begin_verse
^A foo
bar
baz^B
#+end_verse
that function
* Reproducer
Save the following files:
- /tmp/test.org -
#+begin_src bash
foo
bar
baz
#+end_src
- /tmp/test.org -
- /tmp/test.el -
(transient-ma
Is there any kind of support (also by non-core extensions) for tables
in Org that are entirely organized along buffer columns? Some magic
(= clever heuristics) that recognizes the following as a table with
four columns, the first three left-aligned, the last right-aligned:
<6>
On 2023-09-03 08:53, Ihor Radchenko wrote:
> Jens Schmidt writes:
>
>> Implemented in the next version of the patch, please check.
>>
>
> Applied, onto main.
Thanks!
On 2023-09-02 09:10, Ihor Radchenko wrote:
> Jens Schmidt writes:
>> - Even if we made "&" mandatory, it would not really solve the quoting
>> problem, since the parser is rather hacky and other quoting and
>> context issues would still be there.
>
>
On 2023-09-02 09:10, Ihor Radchenko wrote:
> Jens Schmidt writes:
>> This all calls for a proper parser, based on peg or bovine or whatever.
>> Hopefully that parser would still keep backward compatibility, but
>> that's probably wishful thinking.
>
> Backward c
On 2023-08-27 09:43, Ihor Radchenko wrote:
> Samuel Loury writes:
>
>> IMHO, "-tag&-todo=TODO" is totally ok. I even imagine we could say that
>> & and | are forbidden to say anything else than AND and OR and people
>> would be ok with that.
>
> Actually, explicit & or | might be an easier way
On 2023-08-31 10:08, Ihor Radchenko wrote:
> Jens Schmidt writes:
>
>>> Implemented in the next version of the patch, please check.
>>
>> Gentle ping ...
>
> I was waiting for your comment on
> https://list.orgmode.org/orgmode/874jklhqw2.fsf@localhost/
Ah,
On 2023-08-26 14:54, Jens Schmidt wrote:
> On 2023-08-26 14:22, Ihor Radchenko wrote:
>> Looks good to me.
>
> Implemented in the next version of the patch, please check.
Gentle ping ...
On 2023-08-26 14:22, Ihor Radchenko wrote:
> Jens Schmidt writes:
>> #+begin_example
>> boss\-prio="C"
>> boss\:prio="C"
>> boss\\prio="C"
>> #+end_example
>
> Looks good to me.
Implemented in the next version of the patch,
On 2023-08-26 14:00, Ihor Radchenko wrote:
> Jens Schmidt writes:
>> On 2023-08-26 12:16, Ihor Radchenko wrote:
>>> This actually feels rather cubersome.
>>
>> [...] I can
>> provide a simpler example in the manual, but that's probably not
>>
On 2023-08-26 12:16, Ihor Radchenko wrote:
> Jens Schmidt writes:
>> #+begin_example
>> -+-long-and-twisted-property-name-="foo"
>> +\-long\=and\\twisted\:property\.name\*="foo"
>> #+end_example
>
> This actually feels rather cubersome.
On 2023-08-24 10:52, Jens Schmidt wrote:
> On 2023-08-24 09:32, Ihor Radchenko wrote:
>> I prefer (B). And we will need to allow escaping of the "\" itself. Like
>> \\.
>
> OK. Since backslash is not used yet in the rest of the regexp, (B)
> should
On 2023-08-24 14:24, Ihor Radchenko wrote:
> Jens Schmidt writes:
>
>> Would you mind if I added a test that explicitly and with some nice
>> error message tests for that condition? I.e. if some unwary user
>> strips off trailing whitespace in test-org.el, that t
On 2023-08-24 13:41, Ihor Radchenko wrote:
> Jens Schmidt writes:
>
>> Seems the insert-heading-issue is still struggling, this time during
>> a "make check" @ d5ee33fed8dd80d3f9f9811d86a73827fde80780 using Emacs 29:
>> ...
>>FAILED 998/1094 t
Seems the insert-heading-issue is still struggling, this time during
a "make check" @ d5ee33fed8dd80d3f9f9811d86a73827fde80780 using Emacs 29:
Test test-org/insert-heading condition:
(ert-test-failed
((should
(equal "* 1\n** 1.1\n** 1.2\n*\n* 2"
(org-test-with-temp-te
On 2023-08-24 13:18, Ihor Radchenko wrote:
> Jens Schmidt writes:
>
>> Compiling /home/jschmidt/work/org-mode/lisp/org-element-ast.el...
>>
>> In org-element--properties-mapc:
>> org-element-ast.el:628:25:Warning: ‘not’ called with 3 args, but requires 1
>&g
Compiling /home/jschmidt/work/org-mode/lisp/org-cycle.el...
Compiling /home/jschmidt/work/org-mode/lisp/org-datetree.el...
Compiling /home/jschmidt/work/org-mode/lisp/org-duration.el...
Compiling /home/jschmidt/work/org-mode/lisp/org-element-ast.el...
In org-element--properties-mapc:
org-element-a
On 2023-08-24 09:32, Ihor Radchenko wrote:
> Jens Schmidt writes:
>> Some obvious choice would be a simpler single backslash
>>
>> (B) "\-" => "-"
>
> I prefer (B). And we will need to allow escaping of the "\" itself. Like
&g
On 2023-08-23 16:00, Jens Schmidt wrote:
> Given the property name syntax in
>
> https://orgmode.org/worg/org-syntax.html#Node_Properties
>
> the subre in `org-make-tags-matcher' to match property names
> should then look similar to
>
> &quo
> On 2023-08-23 12:31, Ihor Radchenko wrote:
>
>> Jens, we got an edge case with "-", after all.
>>
>> What is happening here is that the new parser
>> (https://orgmode.org/list/9132e58f-d89e-f7df-bbe4-43d53a236...@vodafonemail.de)
>> treats the above match string as
>>
>> property "tag-TODO" not
On 2023-08-23 12:31, Ihor Radchenko wrote:
> Jens, we got an edge case with "-", after all.
>
> What is happening here is that the new parser
> (https://orgmode.org/list/9132e58f-d89e-f7df-bbe4-43d53a236...@vodafonemail.de)
> treats the above match string as
>
> property "tag-TODO" not equal "T
Thanks for the detailed report!
On 2023-08-23 09:57, Samuel Loury wrote:
> The following tags query used to implicitly behave as a AND
> "-tag-TODO=\"TODO\"".
> Before commit f689eb44f175fbbdc4e8ef0ad6f5201b10863438, this showed only
> "nothing", as expected.
That was my short-sighted attempt
On 2023-08-11 23:48, Ihor Radchenko wrote:
- If you run into this issue, the real pain is to understand what's
going on, since org-ctags might get loaded in surprising ways. So
probably we should make that easier.
The quick fix is unsetting `help-enable-completion-autoload'.
Unfort
On 2023-08-11 19:01, Nick Dokos wrote:
Sure, but we should not reject Jens' proposal just because of this
argument. We can use the suggestions to improve org-ctags itself, after
it is explicitly loaded.
Absolutely.
My disagreement was only with the part that I quoted, in particular
the "Prob
On 2023-08-08 10:48, Ihor Radchenko wrote:
The situation is a bit more complex.
To make it even more complex, here a different point of view. Sorry,
I don't have any earlier mails ready I could reply to ...
* TL;DR
Probably the problem is not the side-effects done by loading
=org-ctags=, b
Sorry, just followed that recent side-effect-thread to the root
https://list.orgmode.org/orgmode/87o7omg4ie@alphaville.usersys.redhat.com/
and found that everything already got documented. It was that thread
that triggered my bug report as an example of a particular nasty side
effect.
make EMACS=../emacs-master/src/emacs vanilla
Create a new Org-mode buffer with the following contents:
--
<>
[[test][test link]]
--
Position point on the link then type C-c C-o: Point jumps to the l
ume
that "gv" means "getter value" and be done with it.
Updated patch attached.From 6e98356dfaf3466288398ff4ecee7fd147c32a20 Mon Sep 17 00:00:00 2001
From: Jens Schmidt
Date: Sun, 6 Aug 2023 16:38:04 +0200
Subject: [PATCH] org-make-tags-matcher: Add starred property operators, fix
quotin
On 2023-08-06 11:19, Jens Schmidt wrote:
I
will also add tests for matching property names having minuses and then
we can see how it goes.
Went well. With a property name regexp
"\\(?5:[[:alnum:]_-]+\\)"
and the following Org file
-
On 2023-08-06 09:55, Ihor Radchenko wrote:
But from here it gets more intersting:
- The code uses subre "-" in property names to (supposedly) allow
for inclusion of minus characters in property names, which (probably)
could be confused with term negation.
Not probably. It is know
it is added to Emacs) rely upon peg.el for parsing.
Given the fact that we have to discuss issues like those above, I
heartily agree.
> https://yhetil.org/emacs-devel/875yvtbbn3@ericabrahamsen.net/
Arthouse thread: Interesting plot, surprising sidelines, not everything
comprehensible, (un
On 2023-07-31 08:45, Ihor Radchenko wrote:
If you are up to a job of adding this to `org-make-tags-matcher' and
not breaking things, you can try.
Depends a bit on the required collateral changes: Updating ORG-NEWS and
doc/org-guide.org should be no problem. Doing a naive grep-based search
I
The following was initially meant as bug report until I understood that
it's actually some sort of feature ...
Consider the following todo list:
todos.org
* TODO relax
* TODO do this
:PROPERTIES:
:patchday: 202302
:END:
* TODO do that
:PROPERTIES:
:pat
look right now?
From 74d5c1f5caf4ce425eb888340c2115276b4ddf8a Mon Sep 17 00:00:00 2001
From: Jens Schmidt
Date: Sun, 30 Jul 2023 17:51:27 +0200
Subject: [PATCH] ol-gnus.el: Fix issue when storing links from Gnus article
buffers
* lisp/ol-gnus.el (org-gnus-store-link): Switch to
`gnus-summary
In the context of some ol-gnus bug I created a minimal Gnus setup. Ihor
wanted to have a look at it, so here it is.
To use:
- create an empty directory /foo/bar/baz and say
unzip -qd /foo/bar/baz gnus-minimal-test.zip
- if you want to use the nnselect backend based on notmuch (haven't
t
On 2023-07-26 18:04, Ihor Radchenko wrote:
This is not a proper email address and name. Should I use Jens
Schmidt ?
Sorry, forgot to maintain that yet in my org-mode clone. Will do.
May you please add TINYCHANGE cookie to commit message. I do not see
you having a copyright status in our
On 2023-07-25 01:08, Ypo wrote:
Why did you try that variable instead of
"org-pretty-entities-include-sub-superscripts"?
To be honest: Because I haven't read your mail properly and because I
didn't know about "pretty entities". I just noticed the subscripting
done on such_file_names in Org H
On 2023-07-24 21:12, Ypo wrote:
I wanted it, because I usually use (_) to divide words when naming
my_files, and that looks ugly in Orgmode.
I had that problem myself recently. Do `org-use-sub-superscripts' and
its companion `org-export-with-sub-superscripts' help in your case?
See also .
Uh, I had technical issues and did not get all mails as I expected.
Cobbling things together in one big reply now, with references and
quotes hopelessly broken ... hope you can sort it out.
Anyway, thanks to Eric for chiming in.
> Ideally, it would be nice to have tests, though I have no clue ho
On 2023-07-23 12:26, Max Nikulin wrote:
Is nnselect a real NNTP group or is it some instance existing solely
in user's configuration?
Like nnvirtual and nnir, nnselect exists only in user's configuration,
yes. All these three backends are "wrapper backends" that keep track of
the original me
On 2023-07-22 15:48, Ihor Radchenko wrote:
I am not familiar with Gnus, but looking at the code, may it be that
a Gnus article is open when Gnus summary buffer is not?
Theoretically yes, if you actively and malignantly kill the summary
buffer, for example. In practice and through Gnus key b
Tags: patch
`org-store-link' has a number of related issues when storing links from
article buffers related to nnvirtual, nnselect, or nnir groups. I
describe them here in prose without providing a full repro case, which
would be somewhat difficult to set up. Just let me know if you think
you n
On 2023-07-18 10:13, Ihor Radchenko wrote:
No, it is space. In particular, it is `org--align-tags-here' + some bug
in Emacs that screws up column computation.
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64696
FWIW the third test yields
■ Warning (emacs): Test #3:: ’word’ is hidden apply
On 2023-07-19 09:10, Ihor Radchenko wrote:
I see no good way to address this quickly, so I re-added stickiness to
the opening emphasis marker, as you suggested.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=724135dda
Follow-ups:
1. https://debbugs.gnu.org/cgi/bugreport.cgi?b
[Resent with correct identity to make this visible on the list as well -
sorry for the hassle.]
On 2023-07-18 10:13, Ihor Radchenko wrote:
Confirmed.
Thanks for caring about this so quickly ...
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64696
... and for the discussion with Eli & co.
[emacs-29]$ ./src/emacs -Q -L ~jschmidt/work/org-mode/lisp/
(org-version nil t)
"Org mode version 9.7-pre (release_9.6.7-562-g5b6268 @
/home/jschmidt/work/org-mode/lisp/)"
(setq org-hide-emphasis-markers t)
t
;; assume test.org being absent in cwd
C-x 4 f ;; find-file-other-window
t
On 2023-06-09 09:34, Ihor Radchenko wrote:
Emacs master tracks the latest stable Org release.
OK, so I cobbled up Org main with branch emacs-29.
./src/emacs -Q
M-x org-version
Org mode version 9.7-pre (release_9.6.6-408-g9082fa @ ...)
(setq org-adapt-indentation 'headline-data)
Paste the
Forget about that one, it is already fixed in master. I had the wrong load path
and used actually 9.5.5 and not org-mode cloned from master, as intended.
60 matches
Mail list logo
