Max Nikulin writes:
> It seems I completely failed trying to express my idea.
>
> Instead of extending Org grammar (syntax), I suggest to change behavior
> of source blocks during export. In addition to current :results options,
> "ast" may be added. Its effect is that instead of adding text
Juan Manuel Macías writes:
> For my personal use I have written a function which performs Org related
> searches in different places. The list of places is expandable, but so
> far I found them useful: this mailing list, the Org Manual (via org-ql),
> the Git log and the Org Reddit. The idea was
Ihor Radchenko writes:
> The patches look good, but I am unable to apply them onto current main:
Hmm, strange. I've rebased on top of current main, and I'm resending
the resulting patches here. I hope they work better.
From ffd00c1272dd876f64c9ef930d19988b6da5c2a3 Mon Sep 17 00:00:00 2001
Stefan Kangas writes:
> Please find attached three separate documentation patches.
Thanks!
The patches look good, but I am unable to apply them onto current main:
128 git … am --3way -- /tmp/0002-Improve-documentation-of-org-agenda-skip.patch
Applying: Improve documentation of
Tim Landscheidt writes:
>> This looks like the nginx case issue again.
>
>> I've looked at this and there does not seem to be any 'clean' way to fix
>> this which also doesn't have significant processing overhead or a
>> maintenance burden.
>
>> I wonder if it would be worthwhile adding an
Ihor Radchenko writes:
>> +(defvar org-agenda-filters-preset nil
>> + "Preset of filters, which becomes buffer-local in org-agenda buffers.")
>
> Can you detail the value format in the docstring?
> It would also be useful to mention `org-agenda-local-vars'. Otherwise,
> the reader might be
Ypo writes:
> Sorry for my delayed answer. But I don't see it either :/
>
> "The prompt will default to a timer string at
> + point (if any),"
>
> I can't see it well related to the C-u prefix. For example why the "(if
> any)"? It should be unnecessary, since it is the previous explained
>
"Rick Lupton" writes:
> I wonder if you have seen Pollen’s approach to this?
> https://docs.racket-lang.org/pollen/pollen-command-syntax.html
Thanks for the interesting reference!
After skimming through the syntax described in the link, I feel like
most of the features are already present in
Jonas Bernoulli writes:
> * lisp/ob-ref.el (org-babel-ref-resolve): When the result an empty
> list, then treat it as a list, not as the symbol nil.
> * testing/lisp/test-ob.el (test-ob/return-empty-list-from-post-block):
> Add new test.
> * etc/ORG-NEWS (Post-processing code blocks can return
"Fraga, Eric" writes:
> On Wednesday, 5 Oct 2022 at 06:38, reza wrote:
>> But the overlay specification is missing on the second column and I
>> guess this is a bug?
>
> Maybe a bug or more simply a missing feature. On line 552 of
> ox-beamer.el, we add options but there is no equivalent for
No Wayman writes:
> The attached patch is the first step toward integrating DOCT[1]
> syntax into Org mode.
Thanks! This is most welcome.
> It adds property options to org-capture-templates which make it
> easier to run template-specific hooks.
> ...
> Contrast the above with the
Org sample fixed:
BEGIN ORG SAMPLE
...
* Planning
** Planned tasks
- [[#task4][My task 4 header]]
- [[#task5][My task 5 header]]
- [[#task1][My task 1 header]]
- [[#task2][My task 2 header]]
- [[#task7][My task 7 header]]
- [[#task6][My task 6 header]]
- [[#task3][My task 3 header]]
Hi Ihor and all,
I wonder if you have seen Pollen’s approach to this?
https://docs.racket-lang.org/pollen/pollen-command-syntax.html
There are two separate ideas used there which seemed related to this
discussion. I’m not sure if they are useful in the org context.
1. The use of a special
Please find attached three separate documentation patches.
From 269faa44ec18bb63c61ecba4cb232ceb0e46cd10 Mon Sep 17 00:00:00 2001
From: Stefan Kangas
Date: Sun, 2 Oct 2022 21:54:20 +0200
Subject: [PATCH 1/3] Add crossreference to org-stuck-projects docstring
* lisp/org-agenda.el
Tim Cross wrote:
>> at https://orgmode.org/manual/HTML-Export.html, the links
>> for the first five (5) and the last two (2) subsections
>> work, the links for:
>> - "Headlines in HTML export"
>> (https://orgmode.org/manual/Headlines-in-HTML-export.html)
>> - "Links in HTML export"
>>
Here's my patch, including a test and a news entry.
I didn't know where to put the test so I just put it at the beginning.
It should probably be moved.
Jonas Bernoulli (1):
Allow returning empty list from post-processing block
etc/ORG-NEWS| 6 ++
lisp/ob-ref.el | 2
* lisp/ob-ref.el (org-babel-ref-resolve): When the result an empty
list, then treat it as a list, not as the symbol nil.
* testing/lisp/test-ob.el (test-ob/return-empty-list-from-post-block):
Add new test.
* etc/ORG-NEWS (Post-processing code blocks can return an empty list):
Document change in
Sorry for my delayed answer. But I don't see it either :/
"The prompt will default to a timer string at
+ point (if any),"
I can't see it well related to the C-u prefix. For example why the "(if
any)"? It should be unnecessary, since it is the previous explained
general case.
Best regards
Ihor Radchenko writes:
> Ihor Radchenko writes:
>
>>> https://orgmode.org/manual/Handling-Links.html#FOOT28
>>
>> Unless I miss something, this footnote is plain wrong. The timestamps
>> are not removed. At least not when I run M-x org-store-link on a
>> headline with timestamp with emacs -Q.
>
Hi all,
For my personal use I have written a function which performs Org related
searches in different places. The list of places is expandable, but so
far I found them useful: this mailing list, the Org Manual (via org-ql),
the Git log and the Org Reddit. The idea was that everything would be
On Wednesday, 5 Oct 2022 at 06:38, reza wrote:
> But the overlay specification is missing on the second column and I
> guess this is a bug?
Maybe a bug or more simply a missing feature. On line 552 of
ox-beamer.el, we add options but there is no equivalent for adding
actions to the column
Juan Manuel Macías writes:
> Ihor Radchenko writes:
>
>> May we introduce a new standard macro {{{page-break(backend)}}}
>> that will expand to an appropriate
>> @@backend:> ?
>
> The macro seems like a good idea. The only (minor) inconvenience that I
> see, if I have understood it correctly, is
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>> But as you can see @3$17 only gets changed to @3$16 but not to @3$8 as
>> it should be.
> Thanks for reporting, and sorry for the late reply.
> Fixed on main.
>
Sébastien Miquel writes:
> Hi,
>
> Ihor Radchenko writes:
>> Thanks for the clarification!
>> I did not mean to reduce the font size in affiliated keywords.
>> I was referring to replacing the display of affiliated keywords:
>>
>> #+name: A classic
>> #+tag: easy
>>
>> will be displayed by Emacs
Hi Ihor and Liu,
Ihor Radchenko writes:
>> I have signed the FSF
>> copyright assignment paper.
>
> Bastien, could you please confirm the FSF records?
I do confirm, I updated https://orgmode.org/worg/contributors.html
Liu, thanks in advance for contributing to Org!
Best,
--
Bastien
Jonas Bernoulli writes:
>>> In the long run you might want to consider not turning any symbols
>>> into strings, at least not when the "regular" block as well as the
>>> post-processing block both use elisp.
>>
>> This may be tricky. Introducing any kind of special case will make the
>> code
Hi List
I have the following MWE:
* A section
** A Frame
*** A left column
:PROPERTIES:
:BEAMER_COL: 0.48
:END:
*** A right column
:PROPERTIES:
:BEAMER_COL: 0.48
:BEAMER_ACT: <2->
:END:
And I would expect the following tex output:
On Thu, Sep 29, 2022 at 4:19 PM Ihor Radchenko wrote:
> Or you can bisect the config to hunt for less obvious issues using
> https://github.com/Malabarba/elisp-bug-hunter
>
I'm preparing a new machine right now, so I will plug into the emacs
configuration one bit ata time and see when the
28 matches
Mail list logo
