From: Matthias Meulien <orontee@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 58200@debbugs.gnu.org, Augusto Stoffel <arstoffel@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#58200: osc.el name conflict
Date: Sat, 01 Oct 2022 08:50:01 +0200 [thread overview]
Message-ID: <877d1kt4va.fsf@gmail.com> (raw)
In-Reply-To: <87wn9kwofu.fsf@gmail.com> (Matthias Meulien's message of "Fri, 30 Sep 2022 23:19:01 +0200")
[-- Attachment #1: Type: text/plain, Size: 194 bytes --]
Matthias Meulien <orontee@gmail.com> writes:
> A patch that renames related files and adds the ansi-osc- prefix is attached.
I just realized that the customization group hasn't been defined.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Define-ansi-osc-customization-group.patch --]
[-- Type: text/x-diff, Size: 1589 bytes --]
From da4bca9eb2b7c5d28e47e7c2bc522731c770d0e3 Mon Sep 17 00:00:00 2001
From: Matthias Meulien <orontee@gmail.com>
Date: Sat, 1 Oct 2022 08:46:50 +0200
Subject: [PATCH] Define ansi-osc customization group
* lisp/ansi-osc.el (ansi-osc): Define ansi-osc customization group
(ansi-osc-for-compilation-buffer): Fix wrong group
---
lisp/ansi-osc.el | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/lisp/ansi-osc.el b/lisp/ansi-osc.el
index 67a8551628..34154998cd 100644
--- a/lisp/ansi-osc.el
+++ b/lisp/ansi-osc.el
@@ -155,6 +155,17 @@ ansi-osc-hyperlink-handler
(and (string-match ";\\(.+\\)" text)
(cons (point-marker) (match-string-no-properties 1 text)))))
+(defgroup ansi-osc nil
+ "Interpretation of OSC escape sequences.
+Handlers for OSC 2, 7 and 8 (for window title, current directory
+and hyperlinks respectively) are provided. OSC (Operating System
+Commands) control sequences are defined in section 8.3.89 of the
+ECMA-48 standard is freely available at
+<URL:https://www.ecma-international.org/publications/standards/Ecma-048.htm>
+as a PDF file."
+ :version "29.1"
+ :group 'processes)
+
(defcustom ansi-osc-for-compilation-buffer 'filter
"What to do with OSC escape sequences in compilation output.
@@ -170,7 +181,7 @@ ansi-osc-for-compilation-buffer
:type '(choice (const :tag "Do nothing" nil)
(const :tag "Filter out OSC" filter)
(other :tag "Translate OSC" t))
- :group 'osc
+ :group 'ansi-osc
:version "29.1")
(defvar compilation-filter-start)
--
2.30.2
[-- Attachment #3: Type: text/plain, Size: 15 bytes --]
--
Matthias
next prev parent reply other threads:[~2022-10-01 6:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 18:32 bug#58200: osc.el name conflict Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-30 19:51 ` Matthias Meulien
2022-09-30 19:57 ` Lars Ingebrigtsen
2022-09-30 20:08 ` Augusto Stoffel
2022-10-01 9:57 ` Lars Ingebrigtsen
2022-09-30 20:10 ` Matthias Meulien
2022-09-30 21:19 ` Matthias Meulien
2022-10-01 6:50 ` Matthias Meulien [this message]
2022-10-01 9:59 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877d1kt4va.fsf@gmail.com \
--to=orontee@gmail.com \
--cc=58200@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).