e actual heading (after the asterisks).
Am Do., 17. Aug. 2023 um 13:30 Uhr schrieb Ihor Radchenko <
yanta...@posteo.net>:
> Michael Dauer writes:
>
> > I probably mis-interpreted the code. Because then I would also fail for
> > normal headings. Just thinking about the symptoms
tasks including the END line
as a branch. Then org-cut-special would do something useful on them, i.e.
cutting the inlinetask includinging its contents and the END line.
Am Do., 17. Aug. 2023 um 10:42 Uhr schrieb Michael Dauer <
mick.da...@gmail.com>:
> I looked directly into the code and I thi
should take the element at point.
Am Mi., 16. Aug. 2023 um 18:02 Uhr schrieb Ihor Radchenko <
yanta...@posteo.net>:
> Michael Dauer writes:
>
> > No. Here also * h2 gets killed by org-cut-special.
>
> You may need to pull the latest main.
>
> > What is REPRO_ARGS?
No. Here also * h2 gets killed by org-cut-special.
What is REPRO_ARGS? org-onlinetask.el is included org repo anyway?
Ihor Radchenko schrieb am Mi., 16. Aug. 2023, 14:11:
> Michael Dauer writes:
>
> > Put the point on the second line - the inlinetask "ilt".
>
>
Put the point on the second line - the inlinetask "ilt".
Am Mi., 16. Aug. 2023 um 13:47 Uhr schrieb Ihor Radchenko <
yanta...@posteo.net>:
> Michael Dauer writes:
>
> >>>>
> > * h1
> > *** ilt
> > *** END
> >
>>>
* h1
*** ilt
*** END
** h11
* h2
<<<
org-cut-special somewhere on the send line kills all but the first line.
Org mode version 9.7-pre (release_9.6.7-594-gf03b83
I don't think that this bug existed in the previous versions.
Maybe it helps to share you other fix there?
Am Mi., 9. Aug. 2023 um 11:14 Uhr schrieb Michael Dauer <
mick.da...@gmail.com>:
> I don't know how to get swiper activated in a "clean" manner from there.
> In my operational set-up everything is based on straight.
>
hr schrieb Ihor Radchenko <
yanta...@posteo.net>:
> Michael Dauer writes:
>
> > The issue is still easy to reproduce:
> >>>>
> > * h1
> > a
> > * h2
> > b
> > * h3
> > b
> > * h4
> > c
> > <<&
e, but h2 works again.
(org-fold-core--clear-isearch-overlays) still fixes the buffer.
Am Fr., 4. Aug. 2023 um 16:11 Uhr schrieb William Denton :
> On 4 August 2023, Michael Dauer wrote:
>
> > I'm on main (Org mode version 9.7-pre (release_9.6.7-594-gf03b83), and
> it's
>
I'm on main (Org mode version 9.7-pre (release_9.6.7-594-gf03b83), and it's
not fixed. Am I missing something?
Am Do., 1. Juni 2023 um 13:33 Uhr schrieb Ihor Radchenko <
yanta...@posteo.net>:
> Michael Dauer writes:
>
> > I think I found a way to cons
Sorry, my mistake. >>>org-protocol://store-link?url=foo&title=bar<<< works.
Am Di., 1. Aug. 2023 um 15:38 Uhr schrieb Michael Dauer <
mick.da...@gmail.com>:
> Just look at the first examples, which are 1-to-1 copied from org-protocol
> code/documentation.
>
Just look at the first examples, which are 1-to-1 copied from org-protocol
code/documentation.
org-protocol://store-link?url=foo&title=bar
is not working. And this is exactly what store-link is for.
Am Di., 1. Aug. 2023 um 14:01 Uhr schrieb Ihor Radchenko <
yanta...@posteo.net>:
>
Org mode version 9.7-pre (release_9.6.4-327-gf81ba4
org-protocol://store-link?url=http:%2F%2Flocalhost%2Findex.html&title=The%20title
stores http://localhost/index.html
org-protocol://store-link?url=val&key2=val2
stores val
org-protocol://store-link?url=val?key2=val2
stores val?key2
org-protoco
I think I found a way to consistently reproduce the issue:
>>>
* h1
a
* h2
b
* h3
b
* h4
c
<<<
Collapse all. All is fine at this time.
At pos-min call (query-replace) bbb -> zzz: Already when asking whether to
replace it cannot expand. h2 and h3 are expansion is broken.
(org-fold-co
hild instead of
a child.
Not important for me, just strangely non-intuitive.
Ihor Radchenko schrieb am Do., 11. Mai 2023, 12:11:
> Michael Dauer writes:
>
> > Example
> > * h1
> > <>** h11
> >
> > brings:
> > * h1
> > *** <>
> >
Example
* h1
<>** h11
brings:
* h1
*** <>
** h11
expected:
* h1
** h11
*** <>
Org mode version 9.7-pre (release_9.6.4-327-gf81ba4
Just another check on my side for any appearance of "org-fold-": Nothing in
my code, only org related packages use it.
$ grep -r -l org-fold- .
./org/.git/index
./org/doc/org-manual.org
./org/etc/ORG-NEWS
./org/lisp/ob-core.el
./org/lisp/ob-exp.el
./org/lisp/ob-lilypond.el
./org/lisp/ob-ref.el
./o
What could be called. It's not org-fold-core-style.
Can I be just a data corruption of the text properties? I've no idea what
they are exactly, and what other parts use them. Maybe a conflicting key,
or failed optimization, or side effect on the regions they apply to. I just
want to give ideas fro
t;…")
(setq org-modern-hide-stars nil) ; somehow fixes indentation of body
And I think that I can only do it after loading org-mode.
Am Sa., 6. Mai 2023 um 09:36 Uhr schrieb Ihor Radchenko :
> Michael Dauer writes:
>
> > This sibling branch works:
> > Text content at posi
org-fold-outline
Am Sa., 6. Mai 2023 um 09:18 Uhr schrieb Michael Dauer :
> Got another observation:
> Text content at position 30248:
>
>
> There is an overlay here:
> From 30248 to 30442
> evaporatet
> invisibleorg-fold-outline
> is
Got another observation:
Text content at position 30248:
There is an overlay here:
From 30248 to 30442
evaporatet
invisibleorg-fold-outline
isearch-open-invisible delete-overlay
org-invisibleorg-fold-outline
priority 5
There are text proper
would have to wait until it happens again.
Am Fr., 5. Mai 2023 um 19:43 Uhr schrieb Ihor Radchenko :
> Michael Dauer writes:
>
> > Based on my analyses it's not the cycle functions, but must come from
> > broken text attributes. Even (org-fold-core-region (point-min)
> (po
Maybe I missed a known bug when doing the research. But all the other
reports describe different and reproducible behaviour.
Sometimes (often) I cannot unfold a subtree. It then affects only one or
more subtrees while others in the same buffer or even the same branch still
work. The only fix then
Yes, but the missing headings are within the narrowed subtree.
Am Mi., 11. Jan. 2023 um 12:22 Uhr schrieb Ihor Radchenko <
yanta...@posteo.net>:
> Michael Dauer writes:
>
> > But within (org-with-wide-buffer) the collapsed branches should be
> visible.
>
> You
But within (org-with-wide-buffer) the collapsed branches should be visible.
Ihor Radchenko schrieb am Mi., 11. Jän. 2023, 11:02:
> Michael Dauer writes:
>
> > I would expect both output rows to be identical. But it seems
> > that (org-with-wide-buffer) has no effect on
I see a potential bug here: (org-element-parse-buffer) with VISIBLE-ONLY
does not include regions made visible with (org-with-wide-buffer).
Test (Have h2.2.1 collapsed before running it.):
>>>
* h1
** h2
*** h2.1
*** h2.2
#+begin_src elisp
(org-with-wide-buffer
(org-narrow-to-subtree)
(goto-char
Agree. How do you run such feature polls?
Ihor Radchenko schrieb am Di., 27. Dez. 2022, 17:20:
> Michael Dauer writes:
>
> > I'm aware of this theoretical conflict. But I see the risk as very low
> > compared to the value of not having to make a lot of customizat
t expansion. Or any other escape sequence to bring
the conflict probability to 0.001.
Am Di., 27. Dez. 2022 um 16:51 Uhr schrieb Ihor Radchenko <
yanta...@posteo.net>:
> Michael Dauer writes:
>
> > I mean something like:
> > * Heading
> > [[http:abc{{{input-file}}}]
erful especially for
action links and deep links into other applications.
Am Di., 27. Dez. 2022 um 16:30 Uhr schrieb Ihor Radchenko <
yanta...@posteo.net>:
> Michael Dauer writes:
>
> > I do not understand why links are excluded from macro expansion. I would
> > see it as ver
Hi,
I do not understand why links are excluded from macro expansion. I would
see it as very valuable to have macros for links too.
The change would be as simple as inserting
(eq type 'link)
into org-macro-replace-all.
May I recommend this patch.
Thanks,
Michael
It's this fixed? How can I track myself?
Ihor Radchenko schrieb am Mo., 17. Okt. 2022, 15:11:
> Michael Dauer writes:
>
> > Org mode version 9.5.5 (9.5.5-geeae6e
> >
> > #+CALL: test1()
> >
> > #+RESULTS:
> > : 1
> >
> > #+CALL:
Org mode version 9.5.5 (9.5.5-geeae6e
#+CALL: test1()
#+RESULTS:
: 1
#+CALL: test2()
Fails with: Format specifier doesn’t match argument type
* Test
#+name: test1
#+begin_src elisp
1
#+end_src
#+NAME: test2
#+begin_src elisp
(org-sbe "test1")
#+end_src
(org-up-element) does not jump up when cursor is on inlinetask.
From within the inlinetask it jumps to the inlinetask heading, but from
there not higher in the hierarchy.
Org mode version 9.5.5 (9.5.5-geeae6e
org-version reports the same version, but now the same code (posted before)
works. So it's fixed.
But shouldn't org-version report 9.5.5 instead of 9.5?
Ihor Radchenko schrieb am Fr., 30. Sep. 2022, 10:22:
> Michael Dauer writes:
>
> > This is the latest commit on ma
hr schrieb Ihor Radchenko <
yanta...@gmail.com>:
> Michael Dauer writes:
>
> > There seems to be an issue with export of inlinetasks, at least with
> > customizing it. Org mode version 9.5 (9.5-gced2b3
>
> Can you try the latest bugfix or main branch instead?
>
> -
There seems to be an issue with export of inlinetasks, at least with
customizing it. Org mode version 9.5 (9.5-gced2b3
Please see the POC below:
* heading 1
** heading 1.1
* heading 2
*** TODO inline task
*** END
* heading 3
** heading 3.1
* Direct is fine
#+begin_src elisp
There is a (require 'org-inlinetask), and I use inlinetasks a lot.
Am Do., 29. Sept. 2022 um 13:18 Uhr schrieb Ihor Radchenko <
yanta...@gmail.com>:
> Michael Dauer writes:
>
> > Inlinetasks are always interpreted to be of type heading. This causes
> > multiple issu
Inlinetasks are always interpreted to be of type heading. This causes
multiple issues e.g with export.
I think that I could track it to the function org-element--current-element,
where the check for headings is before the one for inlinetasks, while
inlinetask is just a sub-type of heading.
Hence
This e.g. affects pressing TAB on an inlinetask in the agenda view.
Org mode version 9.5 (9.5-gced2b3
Sorry, please ignore. The problem was in front of the screen.
Am Di., 15. Feb. 2022 um 14:16 Uhr schrieb Sébastien Miquel <
sebastien.miq...@posteo.eu>:
> Hi,
>
> Michael Dauer writes:
> > When I export a subtree I normally want to produce a document for the
> > topic
Org mode version 9.5.2 (9.5.2-ge7ea95
When I export a subtree I normally want to produce a document for the topic
of the subtree. So I would expect that the contents of the subtree would be
exported with the heading as title (and maybe file name) and the children
promoted to level 1.
What I recei
uzzy-link the relevant function, at least
for my use case?
But there it looks like it is searching through all elements including
inlinetasks, which is in org-element-all-elements:
(append pseudo-types '(target) org-element-all-elements)
Am Sa., 4. Dez. 2021 um 04:18 Uhr schrieb I
:
> Michael Dauer writes:
>
> > Before (require 'org-inlinetask) all is fine. But after executing
> (require
> > 'org-inlinetask) the following happens:
> > 1. With point on/in t1 (org-store-link) stores *h2.
> > 2. The manually created link below h1 wor
Is there a setting that excludes inline-tasks from internal links?
I actually want to link to inline-tasks. BUT:
emacs -Q
>>>
* h1
[[*t1][t1]]
* h2
*** TODO t1
*** END
(require 'org-inlinetask)
<<<
Before (require 'org-inlinetask) all is fine. But after executing (require
t;
yanta...@gmail.com>:
> Michael Dauer writes:
>
> > Hi,
> >
> > Was something wrong with my previous report or is nobody interested in
> > inline tasks?
>
> Your report is fine, but please note the following
> (https://orgmode.org/worg/org-mailing-lis
Hi,
Was something wrong with my previous report or is nobody interested in
inline tasks?
Inline tasks are a great feature of org-mode, very useful to include tasks
in all sorts of documents without interfering with the document structure.
I resend my report with now hopefully all information to
Hi,
I resend my report with now hopefully all information to reproduce it
quickly.
Inline tasks are a great feature of org-mode, very useful to include tasks
in all sorts of documents without interfering with the document structure.
0. emacs -Q
1. Insert the below snippet into scratch buffer.
>>
uot; targets
:@CB:
x
*** END
** heading 4
x
(org-mode)
(require 'org-inlinetask)
<<<
Am Mo., 20. Sept. 2021 um 10:21 Uhr schrieb Ihor Radchenko <
yanta...@gmail.com>:
> Michael Dauer writes:
>
> > What I get after the first org-c
following subtree is more complex.
it stays after the 2nd and 3rd cycle. Cycles 4 to 6 are OK, then the
problem comes again.
Am Mo., 20. Sept. 2021 um 07:01 Uhr schrieb Ihor Radchenko <
yanta...@gmail.com>:
> Michael Dauer writes:
>
> > Stating collapsed, pressing TAB on the headi
Sorry, I forgot:
Org mode version 9.4.6 (9.4.6-gcf30f7
Am Sa., 18. Sept. 2021 um 10:27 Uhr schrieb Michael Dauer <
mick.da...@gmail.com>:
> Hi,
>
> Inline tasks are a great feature of org-mode, very useful to include tasks
> in all sorts of documents without interfering
Hi,
Inline tasks are a great feature of org-mode, very useful to include tasks
in all sorts of documents without interfering with the document structure.
But it seems that there are multiple issues with multiple org commands and
inline tasks (visibility, navigation, selection).
For that reason I
Hi,
If I did not miss it there is no way to specify arguments as optional for a
macro definition.
I've the following:
(defun ct-action-plan (&optional up recently-done)
...
(push '("action_plan" . "(eval (ct-action-plan $1 $2))")
org-export-global-macros)
The arguments of the function are specif
Hi,
I have a lot of global macros defined in org-export-global-macros. Wherever
they are used in my org files org-lint reports them as undefined.
It seems that org-lint just checks against org-macro-templates (collected
with (org-macro-initialize-templates)) and a few default macros.
I'm going t
Hi Tim,
indent-tabs-mode was exactly what I was looking for.
Thank you,
Michael
Am Di., 25. Mai 2021 um 04:39 Uhr schrieb Tim Cross :
>
> Michael Dauer writes:
>
> > Hi,
> >
> > #+begin_src elisp :results output
> > (aaa
> > bbb (
> > #x09#x09#x
hrieb Nicolas Goaziou <
m...@nicolasgoaziou.fr>:
> Hello,
>
> Michael Dauer writes:
>
> >>>>
>
> [...]
>
> >>>>
>
> I think we are mis-communicating. I saw the document you're re-posting.
> My question, however, is about the speci
ormal text
TODO l3
---
SCHEDULED: <2021-06-08>
normal text
* TODO l4
normal text
<<<
Am Di., 15. Juni 2021 um 08:07 Uhr schrieb Nicolas Goaziou <
m...@nicolasgoaziou.fr>:
> Hello,
>
> Michael Dauer writes:
>
> > I would understand that the ex
;
m...@nicolasgoaziou.fr>:
> Hello,
>
> Michael Dauer writes:
>
> > There seems to be a bug in Org mode version 9.4.6 (9.4.6-gcf30f7:
> > EXPORT_OPTIONS (at least p for with-planning) is only respected if there
> is
> > no planning date placed above the properties drawe
Hi,
There seems to be a bug in Org mode version 9.4.6 (9.4.6-gcf30f7:
EXPORT_OPTIONS (at least p for with-planning) is only respected if there is
no planning date placed above the properties drawer.
>>>
* TODO export options
:PROPERTIES:
:EXPORT_OPTIONS: p:nil
:END:
SCHEDULED: <2021-06-08 Di.>
**
.
Thanks,
Michael
Am Di., 25. Mai 2021 um 20:32 Uhr schrieb Michael Dauer <
mick.da...@gmail.com>:
> Sorry, maybe I did not test thoroughly enough. I'll do, and come back if
> still necessary. thx
>
> Nicolas Goaziou schrieb am Di., 25. Mai 2021,
> 17:51:
>
>> Mi
Sorry, maybe I did not test thoroughly enough. I'll do, and come back if
still necessary. thx
Nicolas Goaziou schrieb am Di., 25. Mai 2021,
17:51:
> Michael Dauer writes:
>
> > How do you do this with a #+macro keyword with arguments?
>
> As before, with "(eval ...&
How do you do this with a #+macro keyword with arguments?
The old implementation checked the string for a "(eval" prefix.
Nicolas Goaziou schrieb am Di., 25. Mai 2021,
11:14:
> Hello,
>
> Michael Dauer writes:
>
> > at least not compatible with before.
>
at least not compatible with before.
Probably caused by commit 8abdbbee395f284f2262a89187d662eaf40080b1.
originally correct macro ("macroA" . "(eval
do-something-dynamically-at-macro-expansion)")
How should this be achieved now? (functionp "any-string") is nil
Hi,
#+begin_src elisp :results output
(aaa
bbb (
#x09#x09#x09ccc))
ccc
#+end_src
looks like this in the editor
(aaa
bbb (
ccc))
ccc
Line 1-3 were indented automatically by pressing Tab. In line 4 I inserted
6 spaces manually. This is what I would expect to find in line 3
I would like to have just the task headings on the same level,
not also the END marks.
Bastien schrieb am Sa., 15. Mai 2021, 11:02:
> Hi Michael,
>
> Michael Dauer writes:
>
> > Wouldn't it be the much better approach to change inline tasks so
> > that the END line
Hi,
org-agenda-entry-text-cleanup-hook is not called when agenda is produced.
Org mode version 9.3.6 (release_9.3.6-471-g9e385d
Prove:
(defun ct-clean-agenda-entry ()
(message "XXX1"))
(add-hook 'org-agenda-entry-text-cleanup-hook 'ct-clean-agenda-entry)
But there is no output while agen
Hi,
Wouldn't it be the much better approach to change inline tasks so that the
END line is one level below the "begin" line?
I did not think it through. But IMO it would make IT more compatible with
normal org behavior, and also more visually appealing.
With the END notation it would still be un
66 matches
Mail list logo
