GNU bug report logs - #58200
osc.el name conflict

Previous Next

Full log

Message #20 received at 58200 <at> debbugs.gnu.org (full text, mbox):

From: Matthias Meulien <orontee <at> gmail.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 58200 <at> debbugs.gnu.org, Augusto Stoffel <arstoffel <at> gmail.com>,
 Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: Re: bug#58200: osc.el name conflict
Date: Fri, 30 Sep 2022 23:19:01 +0200

[Message part 1 (text/plain, inline)]

Matthias Meulien <orontee <at> gmail.com> writes:

> Lars Ingebrigtsen <larsi <at> gnus.org> writes:
>
>> Matthias Meulien <orontee <at> gmail.com> writes:
>>
>>> Sure.  And I can do the renaming, but what would be a good name?
>>> What do you think of osc-sequences.el?
>>
>> Would ansi-osc.el be totally misleading?
>
> I am ok with that.
>
> My understanding was that OSC sequences are more related to ECMA because
> the most precise description I read is here:
> https://www.ecma-international.org/publications-and-standards/standards/ecma-48/
> but Wikipedia page on ANSI escape sequences tends to present OSC
> sequences as a particular case of ANSI sequences, aligned with your
> suggestion,
> https://en.wikipedia.org/wiki/ANSI_escape_code#OSC_(Operating_System_Command)_sequences.
>
> We could use the prefix ansi-osc- which isn't that long.

A patch that renames related files and adds the ansi-osc- prefix is attached.

[0001-Rename-osc.el-to-ansi-osc.el-bug-58200.patch (text/x-diff, attachment)]

[Message part 3 (text/plain, inline)]

-- 
Matthias

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.