Akira Kyle writes:
> From e9b8b782dbf956c855e2e3cdec5b9e8aa47d47c1 Mon Sep 17 00:00:00 2001
> From: Akira Kyle
> Date: Mon, 27 Feb 2023 12:12:32 -0700
> Subject: [PATCH] org-html-link: Fix relative links with :html-link-use-abs-url
Applied, onto main, adding TINYCHANGE cookie to the commit mess
Sébastien Miquel writes:
> Subject: [PATCH] test-org-src.el: Work around `current-column' bug in older
> emacs
>
> * testing/lisp/test-org-src.el (test-org-src/indented-blocks): Work
> around `current-column' not working in the presence of display strings
> in older emacs.
Applied, onto main. T
and...@fedeli.eu writes:
>#+PROPERTY: Effort_ALL 0 0:10 0:30 1:00 2:00 3:00 4:00 5:00 6:00 7:00
>
>#+COLUMNS: %30ITEM(Task) %30Effort(Estimated Effort){est+} %CLOCKSUM
>...
>Originally produces
>image.png
>That shows that days and months are wrongly counted the same
Thanks!
Co
Dear All,
Including "%b" in the org agenda prefix formats (org-agenda-prefix-format)
allows to display entries' outline paths, which is super useful to get
project-oriented agenda views/todo-list.
Consider a project 'Foobar Report'. In the agenda view/todo-list, it would look
like the followi
On 08/07/2023 16:31, Ihor Radchenko wrote:
- it is what we use ourselves in WORG sources.
Max Nikulin writes:
I have not found it in the worg repository. There are enough @@html:@@
with a handful of @@latex:@@.
Yeah, not in WORG.
https://orgmode.org/quickstart.html#text-comments
It makes
On Wed, 5 Jul 2023 at 23:45, Ihor Radchenko wrote:
> Thanks for the report!
> May you increase your org-element--cache-diagnostics-ring-size 10x and
> try to record the backtrace again?
> I can see that org-data boundaries are incorrect (not at point-max), but
> cannot track down when exactly the
Hi.
Preserved old behavior for `org-element-timestamp-interpreter'
function for :range-type set to `nil'. The new function
The new function takes into account :range-type value when interpreting
ranges and throws error when :range-type set for `active'/`inactive'
types.
>From aa21a84fa38324f455
* aa
** a
** b
** c
is there a command to move entry at point to below c, or to above a?
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com
Hi!
Are you looking for =org-shiftmetadown= and sibling functions? I think
they are bound to SHIFT-META-ArrowDown, and so on, by default.
Cheers,
Dominik
Samuel Wales writes:
> * aa
> ** a
> ** b
> ** c
>
> is there a command to move entry at point to below c, or to above a?
no, i want to move in a single command, not drag.
as if
m-x org-move-this-entry-to-top-same-level
m-x org-move-to-bottom-same-level
On 7/10/23, Dominik Schrempf wrote:
> Hi!
>
> Are you looking for =org-shiftmetadown= and sibling functions? I think
> they are bound to SHIFT-META-ArrowDown, and
I added `org-summary-todo' example function, that are advertized in
`org-after-todo-statistics-hook', to my init file (with
lexical-binding: t) and got a compilation warning:
Warning (bytecomp): Unused lexical variable `org-log-states'
since this variable is undefined. The command:
git log -
On 11/07/2023 06:11, Evgenii Klimov wrote:
I added `org-summary-todo' example function, that are advertized in
`org-after-todo-statistics-hook', to my init file (with
lexical-binding: t) and got a compilation warning:
Warning (bytecomp): Unused lexical variable `org-log-states'
May it be a
Hi,
To reproduce the bug:
1. create test.org:
──✀──
#+begin_src python :session "*Python 3*" :async t
1
#+end_src
# Local Variables:
# python-shell-buffer-name: "Python 3"
# End:
──✀──
2. emacs -Q -L --eval "(require 'ob-python)"
13 matches
Mail list logo
