> From: Ihor Radchenko
> Cc: emacs-de...@gnu.org, emacs-orgmode@gnu.org
> Date: Mon, 05 Feb 2024 22:56:05 +
>
> Jim Porter writes:
>
> > On 2/5/2024 7:07 AM, Ihor Radchenko wrote:
> >> It would make sense to add a number of alists:
> >> - bounds-of-thing-at-point-provider-alist
> >> - same
Eli Zaretskii writes:
> I think we do want to allow extending of this, but doesn't
> thingatpt.el already provide such capabilities? For example, I see
> this in bounds-of-thing-at-point:
> ...
> (cond
> ((get thing 'bounds-of-thing-at-point)
> (funcall (
> From: Ihor Radchenko
> Cc: jporterb...@gmail.com, stefankan...@gmail.com, emacs-de...@gnu.org,
> emacs-orgmode@gnu.org
> Date: Tue, 06 Feb 2024 12:38:19 +
>
> Eli Zaretskii writes:
>
> > I think we do want to allow extending of this, but doesn't
> > thingatpt.el already provide such capa
Jack Kamm writes:
> Ihor Radchenko writes:
>
>> What we can do is to introduce a new backend template function
>> org-babel-session-buffer: that will be passed a session name and
>> src block params and return the session buffer name.
>>
>> If such function is not defined, we fall back to assump
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
--
I also see the warnings. In my case it's because I'm using outline-minor
mode in an elisp file. I'm not sure it's supported, but it worked years
ago: I could fold and unfold sections with usual org-mode keys like C-tab.
I miss that feature. I never managed to learn the real outline-mode
keys/concep
On Mon, Feb 05 2024, Ihor Radchenko wrote:
> Leo Butler writes:
>
>> Q: if #+setupfile points to a real file available to download, does Org
>> evaluate that file?
>
> keywords and startup options are taken from there. No Elisp code present
> in #+SETUPFILE is evaluated.
>
> That said, if the fi
Leo Butler writes:
> So, it is *possible* to have the setupfile set-up arbitrary elisp code
> that would be evaluated at some later time (during export or src block
> evaluation, as you wrote)? Is that correct?
Yes. That's why we prompt when SETUPFILE is remote.
--
Ihor Radchenko // yantar92,
Daniel Clemente writes:
> I also see the warnings. In my case it's because I'm using outline-minor
> mode in an elisp file. I'm not sure it's supported, but it worked years
> ago: ...
It is not supported by Org mode.
The modern outline mode has `outline-cycle'.
--
Ihor Radchenko // yantar92,
O
Zhitao writes:
> This commit is problematic:
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=0a58a53edac955381266e49bd68d1140fbece33e
>
> The old matcher for file+olp+datetree was:
>
> (`(file+olp+datetree ,path . ,outline-path)
> ...
> The new matcher does not match empty outli
Hi Ihor, Jack,
Ihor Radchenko writes:
> Jack Kamm writes:
>
>> I agree that it would be good to redesign it, but am not sure where to
>> start.
>
> For example,
>
> 1. Change `org-babel-comint-async-register' to return UUID and to store
>PARAMS as passed by the backend (current approach
Ihor Radchenko writes:
> Sławomir Grochowski writes:
>
>> +(defun org-columns-move-up ()
>> + (interactive)
>> ...
>> +(defun org-columns-move-down ()
>> + (interactive)
>> ...
>
> May you also add docstrings?
> And maybe better names would be org-columns-next/previous-line.
> ...
Applied, o
[[[ 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. ]]]
> 1. Org mode manual itself, just like the other Emacs manuals may need to
> be tra
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
--
14 matches
Mail list logo