Re: [DISCUSSION] Possible inclusion of org-capture.el into Emacs core (was: [ELPA] New package: jami-bot and org-jami-bot)

[[[ To any NSA and FBI agents reading my email: please consider]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] NOTE: Is it absolute;y necessary to cross post to emacs-devel and emacs-orgmode?

Re: [DISCUSSION] Possible inclusion of org-capture.el into Emacs core (was: [ELPA] New package: jami-bot and org-jami-bot)

[[[ To any NSA and FBI agents reading my email: please consider]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > Similar to jami-bot providing a dbus interface for Jami to interact with >

Elisp function to get the upcoming event with the closest scheduled date

I just learned that it is possible to add functions to tab-bar-format, which is the variable that controls the information that is shown in the tab-bar. I want to write a function that gets the upcoming event with the closest scheduled date so that it is shown in the tab-bar. I want to know if

Re: [PATCH] Set Python shell in Org edit buffer

Ihor Radchenko writes: >> I agree that `python-shell-buffer-name' should be set according to the >> :session header, and that Liu's patch fixes a problem in ob-python. >> >> Is there any objection if I go ahead and apply it? > > Because I am still thinking about the idea with global

Re: Month-week and quarter-week datetrees (RFC and package announcement)

Ihor Radchenko writes: >> https://gitlab.com/jackkamm/org-grouped-weektree >> >> I'd appreciate feedback on 2 points: >> >> 1. Are any of these datetree formats worth upstreaming into org-mode >>proper? > > That would make sense. > >> 2. Can we add a public interface for

Re: [PATCH] Set Python shell in Org edit buffer

Ihor Radchenko writes: > python.el is convenient as it allows setting the session buffer name in > advance via buffer-local variable. Then, all the normal python-mode > commands, including `run-python' or `python-shell-send-region' will work > as expected. However, other babel backends like ob-R

Re: [DISCUSSION] org-capture.el vs remember.el (was: [ELPA] New package: jami-bot and org-jami-bot)

If this works (big if since given all this is vapourware), we'll finally have found good use for indirect buffers :-) FWIW, I use indirect buffers constantly through `org-tree-to-indirect-buffer', which is also called from several of my tools like org-ql, org-bookmark-heading, etc. Largely,

Re: Adding functionality to org-latex-classes

That’s what I’m looking at these days :-) Just trying to provide a proof of concept It helps me coping with my grinchiness PA Enviado desde mi iPhone > El 31 dic 2023, a las 15:37, Ihor Radchenko escribió: > > Pedro Andres Aranda Gutierrez writes: > >> I was just wondering whether it

[PATCH] doc/org-manual.org (Summary): Clarify the Org markup is human-readable

I'd like to amend the Org manual introduction as in the attached patch. The idea is to highlight that Org markup is designed to be human-readable first and foremost rather than just computer-readable. This is the first section of the manual. Most of the new users will see it. So, I'd like to

Re: Should org-link-parser add type "file" when link has no "file:" prefix?

Joseph Turner writes: >> It would be more reliable to provide a separate link type. >> We might even extend the special file+application: link type syntax that >> already allows special behavior for opening file links. > > Thank you! Would you explain about extending file+application syntax?

Re: Month-week and quarter-week datetrees (RFC and package announcement)

Jack Kamm writes: > https://gitlab.com/jackkamm/org-grouped-weektree > > I'd appreciate feedback on 2 points: > > 1. Are any of these datetree formats worth upstreaming into org-mode >proper? That would make sense. > 2. Can we add a public interface for `org-datetree--find-create', and >

Re: Suggestion to add hook to be run when org-indent completes a buffer's initialization

dark.key8...@151e.ai writes: > Although there are some workarounds for the particular issue above, a cleaner > solution would be org-indent calling some hook at the end of the preparation. > As per link above, jdtsmith proposes to add such call in > org-indent-initialize-buffer: > >

Re: Adding functionality to org-latex-classes

Pedro Andres Aranda Gutierrez writes: > I was just wondering whether it would be possible to add further > functionality to org-latex-classes and would like to start a discussion ;-) > > My use case is the following: > > The document class is tightly coupled with ~org-latex-subtitle-format~ >

Re: [PATCH] Fix org-agenda-skip-scheduled-if-deadline-is-shown bug

Morgan Smith writes: > lisp/org-agenda.el (org-agenda-get-scheduled): Consolidate deadline > fetching code. Don't check if deadline is shown when > 'org-agenda-skip-scheduled-if-deadline-is-shown' has a value of > 'repeated-after-deadline'. > > Currently when

Re: [PATCH] org-babel-demarcate-block: duplicate switches too

gerard.vermeu...@posteo.net writes: > The purpose of this patch is to duplicate switches when > org-babel-demarcate-block > duplicates headers (meaning point in the source block when demarcating). Thanks for the patch! Would you mind also adding a test for `org-babel-demarcate-block' in

Re: [BUG] M-x org-lint gives spurious warning when file contains a link with percent-encoded url [9.6.13 ( @ /home/user/.emacs.d/elpa/org-9.6.13/)]

Suhail Singh writes: > Running M-x org-lint on an org file with below contents results in a > spurious "Link escaped with obsolete percent-encoding syntax" warning. > > #+begin_src org > * org-lint url percent-encoding syntax warning > [[https://www.example.com?param=hello%20world][test url]] >

Re: [PATCH] Set Python shell in Org edit buffer

Jack Kamm writes: >> What might be more robust is to provide an explicit "start session >> from Org Src buffer" command for ob-python and re-bind `run-python' to >> this command in Org Src buffers. > > We could refactor `org-babel-python-initiate-session-by-key' to call a > separate

Re: [PATCH] Change default ob-python session command to match run-python

Jack Kamm writes: > Thanks for the feedback! I attach a followup patch in response. If all > looks good, I will squash before applying. LGTM. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at