[PATCH] Highlight ANSI sequences in the whole buffer (was [PATCH] ANSI color on example blocks and fixed width elements)

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 nicely >> colored and escape

Re: [BUG] Propertized space in Agenda's mode-name [9.5.2 (release_9.5.2-3-geb9f34 @ /usr/local/share/emacs/28.0.91/lisp/org/)]

Gustavo Barros writes: > I get that. But please look at it from my perspective too. This is a > reiteration of a previous report. Now you are asking me to make a > third one, which would have to start from scratch. Not from scratch, if you link this discussion. > Also, if Emacs devs are

Re: [BUG] Propertized space in Agenda's mode-name [9.5.2 (release_9.5.2-3-geb9f34 @ /usr/local/share/emacs/28.0.91/lisp/org/)]

Hi Ihor, On Thu, 13 Apr 2023 at 12:10, Ihor Radchenko wrote: > Basically, we need to bring Emacs devs in. Because I have no clue what > is going on. And reporting to Emacs bug tracker is the way to involve > Emacs devs. I get that. But please look at it from my perspective too. This is a

Re: [BUG] Propertized space in Agenda's mode-name [9.5.2 (release_9.5.2-3-geb9f34 @ /usr/local/share/emacs/28.0.91/lisp/org/)]

Gustavo Barros writes: >> It looks like Emacs bug then. I suspect some funny staff going on during >> compilation. >> May you report it to Emacs bug tracker, linking to this bug report? > > Mhm, I don't know why you say it is an Emacs bug. From my side, it > only affects Org Agenda. So I've

Re: [BUG] Propertized space in Agenda's mode-name [9.5.2 (release_9.5.2-3-geb9f34 @ /usr/local/share/emacs/28.0.91/lisp/org/)]

Hi Ihor, On Thu, 13 Apr 2023 at 11:52, Ihor Radchenko wrote: > I inspected `mode-name'. > I tried harder, and I was able to reproduce using literally emacs -Q. Thanks, and I'm glad to know I'm not crazy then. > It looks like Emacs bug then. I suspect some funny staff going on during >

Re: [BUG] Propertized space in Agenda's mode-name [9.5.2 (release_9.5.2-3-geb9f34 @ /usr/local/share/emacs/28.0.91/lisp/org/)]

Gustavo Barros writes: >> I still cannot reproduce on bugfix. > > thanks for checking this again. When you say you can't reproduce you > mean that you get no blank gaps in the mode line, or that, if you > inspect `mode-name`, the space is not propertized? (Just tested the > latter and I do find

Re: [BUG] Propertized space in Agenda's mode-name [9.5.2 (release_9.5.2-3-geb9f34 @ /usr/local/share/emacs/28.0.91/lisp/org/)]

Hi Ihor, On Thu, 13 Apr 2023 at 11:24, Ihor Radchenko wrote: > > Gustavo Barros writes: > > > For the record, I'm trying the new Emacs pretest with Org 9.6.3 and > > the `mode-name` is still has the propertized space and, in some > > situations (e.g. `org-tags-view`) the blank gap in the mode

Re: [BUG] Propertized space in Agenda's mode-name [9.5.2 (release_9.5.2-3-geb9f34 @ /usr/local/share/emacs/28.0.91/lisp/org/)]

Gustavo Barros writes: > For the record, I'm trying the new Emacs pretest with Org 9.6.3 and > the `mode-name` is still has the propertized space and, in some > situations (e.g. `org-tags-view`) the blank gap in the mode line still > creeps in for me. I still cannot reproduce on bugfix. --

Re: [BUG] Propertized space in Agenda's mode-name [9.5.2 (release_9.5.2-3-geb9f34 @ /usr/local/share/emacs/28.0.91/lisp/org/)]

Hi All, On Sat, 22 Oct 2022 at 07:51, Gustavo Barros wrote: > > On Sat, 22 Oct 2022 at 04:14, Ihor Radchenko wrote: > > > I am unable to reproduce with the latest Org. > > thanks for checking this report. > I've retested things here and, though I can still reproduce it with > Org 9.5.5, I can

Re: how to omit section numbers from theindex.html when publishing a project

"Christopher W. Ryan" writes: > Well, my IT department did some major damage to my computer system, and > now the output of publishing a project (my only one) to html is > different. Specifically, the numbers next to each alphabetical letter in > theindex.html are shown, whereas before they were

Re: [PATCH v2] Add compat.el support to Org (was: [POLL] Use compat.el in Org? (was: Useful package? Compat.el))

Max Nikulin writes: >> +;; Package-Requires: ((emacs "26.1") (compat "29.1.4.1")) > > Is there a way to express (or (compat "29.1.4.1") (emacs "28.1")) to > avoid installing compat in the case of sufficiently new emacs? E.g. > dpkg/apt allows such alternatives. No, AFAIK: D.8 Conventional

Re: [BUG] org-latex-packages-alist type specification [9.6.3 (release_9.6.3-2-gf2949d @ /usr/local/share/emacs/29.0.90/lisp/org/)]

> On Apr 13, 2023, at 19:23, Ihor Radchenko wrote: > > Ruijie Yu via "General discussions about Org-mode." > writes: > >> From 0be8702357ddf699c5ff1814a5fa57a6443b10de Mon Sep 17 00:00:00 2001 >> From: Ruijie Yu >> Date: Thu, 13 Apr 2023 13:14:36 +0800 >> Subject: [PATCH] * lisp/org.el

Re: [BUG] org-latex-packages-alist type specification [9.6.3 (release_9.6.3-2-gf2949d @ /usr/local/share/emacs/29.0.90/lisp/org/)]

Ruijie Yu via "General discussions about Org-mode." writes: > From 0be8702357ddf699c5ff1814a5fa57a6443b10de Mon Sep 17 00:00:00 2001 > From: Ruijie Yu > Date: Thu, 13 Apr 2023 13:14:36 +0800 > Subject: [PATCH] * lisp/org.el org-latex-packages-alist: fixed type definition Thanks! May I know if

Re: #o544 is user rw?

Timothy writes: > Any objections? Fixed, by Timothy, on bugfix. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=6a96054f0 -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at

Re: [BUG] Killing link located at beginning of line does not kill full link if region is selected to beginning or end of line by either mouse or arrow keys [9.5.2 (release_9.5.2-13-gdd6486 @ c:/Progra

"Miguel Garza" writes: > Yes, I think there could be arguments for different behaviors, but I suspect > the expected behavior should be the same as when you select the link by other > methods, such as starting a region at one end and then jumping to the > beginning or end of the line with