Ihor Radchenko writes:
> Nathaniel Nicandro writes:
Hello,
I've finally implemented a solution to what I've discussed previously,
inserting zero width spaces as boundary characters after an ANSI
sequence to act as a separator from the text after the sequence. This
would handle the scena
Ihor Radchenko writes:
> Nathaniel, is there any particular problem you encountered that your
> patch was aiming to solve? If no, we should probably re-add fontifying
> example blocks as undocumented feature people rely on in practice.
No there wasn't any particular problem, I was just
aware of when trying to write my own tests?
>From 506e8c1e5a177b797a541b1541ea98c95668d5e1 Mon Sep 17 00:00:00 2001
From: Nathaniel Nicandro
Date: Tue, 9 May 2023 19:58:11 -0500
Subject: [PATCH] Highlight ANSI escape sequences
* etc/ORG-NEWS: Describe the new feature.
* org.el (org-fontify-ansi
Matt writes:
> Thank you for bringing this to my attention and thank you Nathaniel for your
> work on this.
No problem, I'm glad to contribute to Org :)
> Nathaniel, if you and I happen to cross paths in one of Ihor's "office
> hours," I would enjoy learning more about what you're doing.
Ihor Radchenko writes:
> It runs fine on my side, although I am not sure if things are working as
> expected for all the cases. For example, headlines never got fontified
> on my side when I tried your patch on top of the latest main branch.
Yes, the headlines are currently not fontified
n_example
- [32mtest[0m
- [31mtest[0m
#+end_example
Paragraph [43mtwo.
:END:
#+RESULTS:
- [42mlist
- one
- three
- two
- three
#+RESULTS:
- [ ] [42mCheckbox
-
-
#+RESULTS:
- [42mList item
- [@5] List item
:drawer:
Interior
- list inner
- one two three
four five
Ihor Radchenko writes:
> Hi,
Hi Ihor,
> A few months have passed since the last activity in this thread.
> May I know if you are still interested in the idea?
I apologize for being unresponsive all these months. Yes I'm still
interested in this idea, although I have not had time to work on
Ihor Radchenko writes:
> Nathaniel Nicandro writes:
>
>>> 1. Do not allow ANSI sequences to intersect markup boundaries of the
>>>same AST depth:
>>>*bold * plain text should not trigger fontification
>>>*bold /italic/ * should trigger
Ihor Radchenko writes:
> Nathaniel Nicandro writes:
>
>> The attached patch now uses `org-element-at-point' and
>> `org-element-context' to query for the bounds of elements.
>
> Thanks!
>
>> Note, I've also attached an updated example file which shows that
Ihor Radchenko writes:
> Nathaniel Nicandro writes:
>
>>> Ideally, fontifying ANSI sequences should be fully controlled by users:
>>> 1. We may not want to touch src blocks by default, when
>>>`org-src-fontify-natively' is set to t. Only, maybe, provide an
Ihor Radchenko writes:
> Nathaniel Nicandro writes:
>
>> Attached is the patch. Without this patch, ANSI escape sequences
>> generated by the output of a source block will be left in the buffer
>> without any fontification. With this patch, the escaped text is nice
that adds in the constraint.
>From 2f1342ad5b13f75387f6a26f0c68aac054903bcc Mon Sep 17 00:00:00 2001
From: Nathaniel Nicandro
Date: Thu, 6 Apr 2023 08:49:20 -0500
Subject: [PATCH] Handle block-type when checking `org-src-fontify-natively`
* lisp/org.el (org-fontify-meta-lines-and-blocks-1): O
Hello,
Attached is the patch. Without this patch, ANSI escape sequences
generated by the output of a source block will be left in the buffer
without any fontification. With this patch, the escaped text is nicely
colored and escape sequences hidden using overlays.
It works for Emacs versions
Ihor Radchenko writes:
> Nathaniel Nicandro writes:
>
>> I would like to submit a patch that adds support for logind to
>> `org-user-idle-seconds`. This patch has been working for me for a long
>> while now and I thought it time for me to submit it. I've contributed
Hello,
I would like to submit a patch that adds support for logind to
`org-user-idle-seconds`. This patch has been working for me for a long
while now and I thought it time for me to submit it. I've contributed
to Emacs in the past so my paperwork should be on file.
Let me know if any changes
> Thanks a lot for your work!
Thanks a lot for maintaining the wonderful Org package!
> Hope it helps.
Thanks, I've previously seen the video and it does help with figuring
out the issues with emacs-jupyter as it currently stands.
> Also, it appears that Jupyter is getting a lot of traction
> Let me echo others’ comments by saying how much I appreciate your work
> on emacs-jupyter. I use the package daily in my work and it’s been
> really fantastic. Thank you very, very much for your huge efforts and
> time investment in creating and maintaining this package.
Your welcome, I've
Ken,
> First, thank you (many times) for maintaining emacs-jupyter. It is one of the
> most-used tools on my computer. I've been using your software daily for the
> past few years to develop code and write papers.
Your welcome, I'm glad that my efforts on the project mean that there are
Hello all,
I'm the maintainer of the emacs-jupyter project
(https://github.com/nnicandro/emacs-jupyter) which essentially
integrates Jupyter kernels (https://jupyter.org) with Org mode source
blocks.
I wanted to make an introduction to the Org community. So...hello! And
thanks for promoting
I am also experiencing this issue. I'm assuming =org-agenda-sticky= is set to
=t= in your configuration since that is what I have in mine.
I've tracked the problem down to (1) the handling of =org-agenda-sticky= in
=org-agenda-goto-date=, (2) how this affects what =org-agenda-mode= (called by
a721c97924b5b965179a2dd90e54d63c7de00317 Mon Sep 17 00:00:00 2001
From: Nathaniel Nicandro <nr...@uic.edu>
Date: Thu, 27 Apr 2017 18:16:41 -0500
Subject: [PATCH] Honor the :python header argument in python src-blocks
* lisp/ob-python.el (org-babel-execute:python):
`org-babel-python-command`
21 matches
Mail list logo
