From: Philippe Vaucher <philippe.vaucher@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Namespaces - summary, conclusion
Date: Mon, 4 May 2020 18:25:35 +0200 [thread overview]
Message-ID: <CAGK7Mr6UCtJ6BxNn9cKgE2yBJTU5N_a6Um6e+Nmu+u9EvzH4gA@mail.gmail.com> (raw)
In-Reply-To: <837dxroj4k.fsf@gnu.org>
> I think you jump to conclusions too quickly. Each one of the named
> individuals expressed quite different views about the
> renaming/aliasing proposals. In particular, the degree of resistance
> to any and all such changes from each one of those people was very
> different. AFAIU, only Alan is completely opposed to any such change.
Ah, ok I somehow inferred that Alan was the only one to say out loud
what you guys also thought, given your "resistance".
> That said, if we are willing to continue discussing this, we might be
> able to agree to some small enough group of functions for which more
> systematically-named aliases could be added.
>
> > Until now every one of the proposed aliases (in string- or regexp-)
> > were rejected for arguably good reasons but the message is pretty
> > clear, I think aliases in Emacs core are a dead end (for now, that
> > might change later) and will only live in libraries in MELPA (or ELPA
> > is authors care).
>
> That's not my conclusion. I think a small number of aliases could be
> agreed to, based on the responses.
>
> I urge you not to give up.
Thanks. Until now I haven't seen any of the "string-" proposition
where there was the beginning of a consensus, but I'll look again. If
you have something in mind please share.
Regexp looked more promising, should we focus there first?
Philippe
next prev parent reply other threads:[~2020-05-04 16:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 9:27 Namespaces - summary, conclusion Philippe Vaucher
2020-05-04 10:11 ` Philippe Vaucher
2020-05-04 11:38 ` Stefan Kangas
2020-05-04 12:42 ` Philippe Vaucher
2020-05-04 13:13 ` Alfred M. Szmidt
2020-05-04 13:24 ` Stefan Kangas
2020-05-04 13:35 ` Joost Kremers
2020-05-04 14:18 ` Alfred M. Szmidt
2020-05-04 15:35 ` tomas
2020-05-04 16:32 ` Philippe Vaucher
2020-05-04 14:59 ` 조성빈
2020-05-04 16:28 ` Philippe Vaucher
2020-05-05 10:22 ` 조성빈
2020-05-04 15:00 ` Eli Zaretskii
2020-05-04 16:36 ` Philippe Vaucher
2020-05-04 16:52 ` Alfred M. Szmidt
2020-05-04 16:52 ` Alfred M. Szmidt
2020-05-05 16:12 ` Alfred M. Szmidt
2020-05-04 17:08 ` Eli Zaretskii
2020-05-04 18:47 ` Stefan Monnier
2020-05-04 17:36 ` Stefan Monnier
2020-05-04 18:05 ` Philippe Vaucher
2020-05-04 18:25 ` Drew Adams
2020-05-04 14:43 ` Eli Zaretskii
2020-05-04 16:25 ` Philippe Vaucher [this message]
2020-05-04 23:40 ` chad
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGK7Mr6UCtJ6BxNn9cKgE2yBJTU5N_a6Um6e+Nmu+u9EvzH4gA@mail.gmail.com \
--to=philippe.vaucher@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.