Michael Heerdegen writes:
>> May you please post detailed steps to recreate the issue starting from
>> emacs -Q? See https://orgmode.org/manual/Feedback.html#Feedback
>
> I really just hit C-c a a M-> f as I said. C-c a is `org-agenda',
> the following "a" means "current week or day" as usual.
Ihor Radchenko writes:
> I am unable to reproduce.
> May you please post detailed steps to recreate the issue starting from
> emacs -Q? See https://orgmode.org/manual/Feedback.html#Feedback
I really just hit C-c a a M-> f as I said. C-c a is `org-agenda',
the following "a" means "current week o
Ihor Radchenko writes:
> That's what I tried myself.
> I do not see any problem.
> Please, do try to follow
> https://orgmode.org/manual/Feedback.html#Feedback and provide detailed
> steps showing how to reproduce the problem you are seeing without your
> personal config.
This will be a lot of w
Given:
1. A tendency of massively marking all items as schedule [1]
2. Some of that items should be done on daily basis (I generate them
with a daily template and the power of org-capture)
3. Life happens and some of them are accumulated, for my last case, that
was 29 entries pending to be proc
Michael Heerdegen writes:
> especially after displaying the agenda when it didn't exist before, when
> I display it (`org-agenda'), switch to it and then move point to the end
> of the agenda buffer, and hit f (`org-agenda-later'), I see an purely
> void window. I don't think I messed with agend
[replying to two messages]
Quoth onf:
On Sat Jan 4, 2025 at 7:37 AM CET, G. Branden Robinson wrote:
At 2025-01-04T01:23:02+0100, onf wrote:
[…]
> My impression of Plan 9's troff is that it's a poorly maintained
> descendant of DWB troff that's used only to format manpages.
It’s not only use
Ihor Radchenko writes:
>> +(ert-deftest ob-tangle/bibtex ()
>> + "Tangle BibTeX into a `.bib' file."
>
> I think that the test is not necessary here.
> We already test `org-babel-tangle-lang-exts' in
> `ob-tangle/collect-blocks', I think.
> Or do I miss something?
I wanted to make sure this beh
Rudolf Adamkovič writes:
> I wanted to make sure this behavior, specifically for BibTeX, will never
> get "lost in translation", say when refactoring. ...
Ok.
Applied, onto main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=405787dfbc
--
Ihor Radchenko // yantar92,
Org mode
---
etc/ORG-NEWS | 7 +++
lisp/ob-tangle.el | 3 ++-
testing/lisp/test-ob-tangle.el | 24
3 files changed, 33 insertions(+), 1 deletion(-)
diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS
index 8f266c560..097550805 100644
--- a/etc/ORG-NEWS
++
Ihor Radchenko writes:
>> When doing:
>> (org-export-to-file 'html "~/new/path/thing.html")
>> and the file option has the path "~/other/path/file.org", the 'ltximg'
>> directory is made in "~/other/path/", which is not intutive, or useful
>> behaviour.
>>
>>
>> (the option 'tex' is set to 'dvisv
Rudolf Adamkovič writes:
> +*** BibTeX is tangled with the standard =.bib= file extension
> +
> +Previously, =bibtex= source blocks located in a file named =NAME.org=
> +were tangled into a file named =NAME.bibtex=. Now, they are tangled
> +into a file named =FILE.bib=, using the standard extens
Ihor Radchenko writes:
> Ihor Radchenko writes:
>
>>> When doing:
>>> (org-export-to-file 'html "~/new/path/thing.html")
>>> and the file option has the path "~/other/path/file.org", the
>>> 'ltximg'
>>> directory is made in "~/other/path/", which is not intutive, or
>>> useful
>>> behaviour.
>>
12 matches
Mail list logo
