From: Augusto Stoffel <arstoffel@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 58200@debbugs.gnu.org, Matthias Meulien <orontee@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#58200: osc.el name conflict
Date: Fri, 30 Sep 2022 22:08:41 +0200 [thread overview]
Message-ID: <CAHixrvaeihp_dcF4ExNihbVLZRyh6Cmq3ga9HgNtD7BhyEJErg@mail.gmail.com> (raw)
In-Reply-To: <871qrsk54g.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
I think the file name in itself doesn't matter too much. But should we also
rename all symbols to have a matching prefix?
Sharing the osc- prefix is not as clean but I guess there's enough space in
it for the two packages...
On Fri, Sep 30, 2022, 21:57 Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Matthias Meulien <orontee@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?
>
[-- Attachment #2: Type: text/html, Size: 963 bytes --]
next prev parent reply other threads:[~2022-09-30 20:08 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 [this message]
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
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=CAHixrvaeihp_dcF4ExNihbVLZRyh6Cmq3ga9HgNtD7BhyEJErg@mail.gmail.com \
--to=arstoffel@gmail.com \
--cc=58200@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=orontee@gmail.com \
/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).