Jonas Bernoulli writes:
> In 2022 I changed Melpa to get ob-spice.el from
> https://repo.or.cz/ob-spice.git in response to
> https://github.com/melpa/melpa/issues/7872#issuecomment-1034945112.
>
> But org-contrib still contains that file and the README at the new
> location still contains
>
>>
The documentation for both text markup and TeX-style LaTeX fragments states
that their contents (CONTENTS for text markup, BODY for TeX-style LaTeX
fragments) cannot span more than three lines, but I'm not seeing such
limitation for either in practice. I don't know if this is a documentation
Jonas Bernoulli writes:
> Ihor Radchenko writes:
>
>> Jonas Bernoulli writes:
>>
>>> In 2022 I changed Melpa to get ob-spice.el from
>>> https://repo.or.cz/ob-spice.git in response to
>>> https://github.com/melpa/melpa/issues/7872#issuecomment-1034945112.
>>
>> The last discussion was back in
On Sun, Aug 27, 2023 at 2:26 PM Jack Kamm wrote:
> Ihor Radchenko writes:
>
> > Confirmed.
> >
> > It looks like `python-shell-first-prompt-hook' does not get triggered
> > in the described scenario with exit() and we enter infinite loop in the
> > code below.
>
> I think
* lisp/org-table.el (org-table-make-reference): Replace 'eq' with
'string-empty-p' to resolve "Warning: 'eq' called with literal string
that may never match" issued on every 'make' invocation.
---
lisp/org-table.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Ihor Radchenko writes:
> Peter Mao writes:
>
>> Expectation: When running ob-python code blocks, I should be able to
>> kill the python session in the *Python* buffer and run another code
>> block (or the same one).
>>
>> Problem: ob-python works fine on the first execution, but after
>>
Hi org-mode developers, Ihor,
I got these warnings when I followed an id: link
(org-open-at-point) within diary.org
I have no idea why diary.org_archive was opened at that
time. The following is the complete contents of the
*Warnings* buffer at the moment:
■ Warning (org-element-cache):
Wow, that's a great video Dr. Kitchen; I'll have to find time to take a
deeper dive into your OrgRef software
This question from Mr. Maske is interesting, "...The session load gets too
high, the editor becomes too slow,...etc."
* Suggest making smaller .org files
* Suggest also trying to mix in
Ihor Radchenko writes:
> Jack Kamm writes:
>
>>>FAILED 376/1256 test-ob-python/session-multiline (0.011955 sec) at
>>> ../lisp/test-ob-python.el:105
>>
>> Hmmm. Do you have an idea of how long this has been happening, and how
>> frequently it breaks?
>
> For months.
>
>> My first
Edgar Lux writes:
> On Aug 27, 2023 at 1:28 PM, Ihor Radchenko wrote:
>
9. M-& make repro REPRO_ARGS="-l /tmp/bug.el /tmp/bug.org"
>
>> Please run this command from terminal.
>> It should spawn a clean Emacs instance with Org version from the repository.
>
> No warning after C-c C-x C-l
On Aug 27, 2023 at 1:28 PM, Ihor Radchenko wrote:
>>> 9. M-& make repro REPRO_ARGS="-l /tmp/bug.el /tmp/bug.org"
> Please run this command from terminal.
> It should spawn a clean Emacs instance with Org version from the repository.
No warning after C-c C-x C-l(2x)
--
Ihor Radchenko
Ihor Radchenko writes:
> Although, the name "inlinetask" is actually awkward in such use case.
> Something like inlinesection would fit better. Or inlineheading.
Completely agree. I like inlinesection and inlineheading equally.
> And what about drawers? Don't they fit the idea of "detached"
Den sön 27 aug. 2023 kl 09:49 skrev Ihor Radchenko :
> Henrik Frisk writes:
>
> >> Hmm. Did you customize `org-src-fontify-natively'?
> >>
> >
> > This is what I have:
> >
> > (setq org-confirm-babel-evaluate nil
> > org-src-fontify-natively t
> > org-src-tab-acts-natively t)
>
>
On Saturday, 26 Aug 2023 at 12:30, Ihor Radchenko wrote:
> That will indeed work. But then the todo will not appear in agenda.
Indeed. Luckily, for me, I don't tend to want the actions within my
long documents to be listed in my agenda. Essentially, I have global
todo items (which appear in my
Edgar Lux writes:
> On Aug 26, 2023 at 6:28 PM, Ihor Radchenko wrote:
>
>> Did you see a new Emacs instance at this point?
>
> Nope. I just launched Emacs again (there is another instance running) and
> copied the command
>
>>> 9. M-& make repro REPRO_ARGS="-l /tmp/bug.el /tmp/bug.org"
Please
Could be used M-right or M-left to align paragraphs which are
immediately below a list?
In a list, if pressing Enter, the next paragraph is aligned below the
item of the list:
+ Item 1
Text indented, belongs to Item 1.
If there are subitems, the text could be needed to be aligned below a
On Aug 26, 2023 at 6:28 PM, Ihor Radchenko wrote:
> Did you see a new Emacs instance at this point?
Nope. I just launched Emacs again (there is another instance running) and
copied the command
>> 9. M-& make repro REPRO_ARGS="-l /tmp/bug.el /tmp/bug.org"
Shell buffer shows
#+begin_example
Ihor Radchenko writes:
> Jonas Bernoulli writes:
>
>> In 2022 I changed Melpa to get ob-spice.el from
>> https://repo.or.cz/ob-spice.git in response to
>> https://github.com/melpa/melpa/issues/7872#issuecomment-1034945112.
>
> The last discussion was back in 2020
>
Juan Manuel Macías writes:
> Ihor Radchenko writes:
>
>> In other words, it is not the section itself, but other
>> headline/inlinetask features, like todo keywords, tags, planning. Right?
>
> No, it is the section itself (or the concept of "section", with its toys
> in Org, of course) that is
zhaoyiyu writes:
> When I track down a issue about org-journal, with org v9.7
> I noticed that when execute
> (org-up-heading-safe)
> it's different with org v9.6, which would caused the org-journal issue.
> In detail as follows org file. After execution the cursor position will
> change to
>
>
Hi Ihor
On August 23, 2023 12:44:32 PM GMT+01:00, Ihor Radchenko
wrote:
>Ihor Radchenko writes:
>
>> What about generalizing the idea and providing a way to set Emacs
>> buffer-local variables in the tangled files?
>>
>> Can be something like:
>>
>> #+begin_src elisp :file-locals
Henrik Frisk writes:
>> Hmm. Did you customize `org-src-fontify-natively'?
>>
>
> This is what I have:
>
> (setq org-confirm-babel-evaluate nil
> org-src-fontify-natively t
> org-src-tab-acts-natively t)
Then, might be https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63579
If it is,
Samuel Loury writes:
> IMHO, "-tag&-todo=TODO" is totally ok. I even imagine we could say that
> & and | are forbidden to say anything else than AND and OR and people
> would be ok with that.
Actually, explicit & or | might be an easier way to not worry about
escaping things. Except escaping &
Den lör 26 aug. 2023 kl 18:23 skrev Ihor Radchenko :
> Henrik Frisk writes:
>
> >> Is lilypond library is loaded when you open Org file?
> >> What happens if you run C-c ' on an src-block?
> >>
> >
> > That works fine, code is syntax highlighted.
>
> Hmm. Did you customize
I have a dumb question.
IIUC, it needs a lot of effort to deal with implicit & correctly. I
initially used it because de manual said it was ok, but I would have
used explicit & if the manual had said so.
I wonder if we could just stop saying that & is optional and have a
simpler parsing.
IMHO,
25 matches
Mail list logo
