Hi
I have been reading about org-bibtex, and I think the mail list were
right when advised it to me
(https://lists.gnu.org/archive/html/emacs-orgmode/2021-10/msg00621.html).
Now... I would like to start using it. I have seen it has a kind of
org-capture template (M-x
* testing/lisp/test-org-agenda.el (test-org-agenda/skip-if): New test.
(test-org-agenda/non-scheduled-re-matces): Fix typo by changing name
to 'test-org-agenda/non-scheduled-re-matches'.
---
testing/lisp/test-org-agenda.el | 62 -
1 file changed, 61 insertions(+),
> On Jul 15, 2023, at 9:11 AM, Thomas S. Dye wrote:
>
>
> Ihor Radchenko writes:
>
>> "Thomas S. Dye" writes:
>>
Am I correct that language-specific header arguments are not yet covered
in the manual? I can't find any reference of "lexical" there.
>>>
>>> Yes, I believe so.
Ihor Radchenko writes:
"Thomas S. Dye" writes:
Am I correct that language-specific header arguments are not
yet
covered
in the manual? I can't find any reference of "lexical" there.
Yes, I believe so. Language-specific header arguments for many
languages are documented at
Hi Ihor,
> I do not think that setting `lexical-binding’ file-local variable in an
> Org file makes much sense. I am sure that we can do better.
I suppose part of the question is what sort of way we treat it? In my mind,
considering the current way lexical scope is seen in Emacs (used everywhere
Ihor Radchenko writes:
> Mauro Aranda writes:
>
>> After emacs -Q:
>> 1. (require 'org)
>> 2. M-x customize-face RET org-property-value
>>
>> A custom buffer shows up, but it says:
>> NO CUSTOMIZATION DATA; not intended to be customized.
>
> Thanks for reporting!
Thanks for your quick
Mauro Aranda writes:
> After emacs -Q:
> 1. (require 'org)
> 2. M-x customize-face RET org-property-value
>
> A custom buffer shows up, but it says:
> NO CUSTOMIZATION DATA; not intended to be customized.
Thanks for reporting!
I am attaching tentative patch that makes `org-property-value' face
After emacs -Q:
1. (require 'org)
2. M-x customize-face RET org-property-value
A custom buffer shows up, but it says:
NO CUSTOMIZATION DATA; not intended to be customized.
Could you please change this definition of org-property-value?
(defface org-property-value nil
"Face used for the value
Mehmet Tekman writes:
> ... I will rewrite to to conform to the
> `org-test-with-temp-text' examples.
Two months have passed since the last message in this thread.
Mehmet, have you had a chance to work on this? May you need any help?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn
Ihor Radchenko writes:
> From a05e2cc235b10a7096538da4f6ae6d17c82a6b25 Mon Sep 17 00:00:00 2001
> Message-ID:
>
> From: Ihor Radchenko
> Date: Wed, 5 Jul 2023 13:14:56 +0300
> Subject: [PATCH] org-store-link: Move already stored link to front by default
Applied, onto main.
"Thomas S. Dye" writes:
>> Am I correct that language-specific header arguments are not yet
>> covered
>> in the manual? I can't find any reference of "lexical" there.
>
> Yes, I believe so. Language-specific header arguments for many
> languages are documented at
>
Max Nikulin writes:
> The idea to find duplicated tests is bright. The code may be transformed
> in a dedicated unit test. I would not drop existing tests blindly though.
Very good idea indeed.
One gotcha is that not every should form is next level after
ert-deftest. And there are also
Timothy writes:
> It occurs to me that this use case could also perhaps be satisfied by
> file-local
> variables? If we presume that mixing tangling to lexically-bound and
> non-lexically bound elisp files is a corner case we don’t care that much
> about,
> a `org-babel-elisp-lexical' variable
Evgenii Klimov writes:
> From ed39640d75df231c8826191f2576fcfd6a5aa723 Mon Sep 17 00:00:00 2001
> From: Evgenii Klimov
> Date: Sat, 15 Jul 2023 00:34:58 +0100
> Subject: [PATCH] org-contrib/babel/languages/index.org: Fix broken link
Thanks!
Applied, onto master.
赵一宇 writes:
> When I try to execute ob-block in a narrowed buffer, there seems to have
> a error on org-babel-result-to-file, with msg "wrong argument type
> stringp, nil"
>
> and the reason is at line marked as -2->, which "buffer-file-name" would
> be nil when in narrowed buffer.
Thanks
15 matches
Mail list logo
