From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mattias.engdegard@gmail.com, 66706@debbugs.gnu.org,
Stefan Kangas <stefankangas@gmail.com>
Subject: bug#66706: [PATCH] Automatic elisp dialect insertion
Date: Wed, 25 Oct 2023 07:56:54 -0400 [thread overview]
Message-ID: <jwv8r7qyla3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83v8avjuv8.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 25 Oct 2023 05:31:23 +0300")
> enough. It is not Emacs's business to force users into something they
> don't want to do.
Not inserting a cookie (i.e. what we do now) forces the use of the
dynbind dialect. In my experience, most users either don't know which
dialect they want or want the lexbind dialect.
This is reflected in the fact that almost all the code I find out there,
is either using lexbind or is old: the only code still using dynbind is
the code that started its life before lexbind existed, pretty much.
And this is to be expected: lexical scoping is the standard in virtually
all programming languages (e.g. Python, JavaScript, C, C++, Java, C#,
Rust, ...) so programmers are much more at ease with that choice.
So we currently do "force users into something they don't want to do"
and the patch will simply let us do that less often.
Stefan
next prev parent reply other threads:[~2023-10-25 11:56 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 17:46 bug#66706: [PATCH] Automatic elisp dialect insertion Mattias Engdegård
2023-10-23 18:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-23 18:44 ` Eli Zaretskii
2023-10-23 19:21 ` Stefan Kangas
2023-10-23 20:20 ` Mattias Engdegård
2023-10-24 17:31 ` Mattias Engdegård
2023-10-24 18:25 ` Eli Zaretskii
2023-10-24 19:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-24 20:22 ` Stefan Kangas
2023-10-25 2:31 ` Eli Zaretskii
2023-10-25 11:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-10-25 12:17 ` Stefan Kangas
2023-10-25 12:54 ` Dmitry Gutov
2023-10-26 0:31 ` Michael Heerdegen
2023-10-26 6:35 ` Eli Zaretskii
2023-10-27 3:14 ` Michael Heerdegen
2023-10-27 6:26 ` Eli Zaretskii
2023-10-27 7:24 ` Michael Heerdegen
2023-10-27 7:32 ` Eli Zaretskii
2023-10-27 14:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-29 12:26 ` Eli Zaretskii
2023-10-25 0:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 1:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 2:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 3:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 11:48 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 12:46 ` Dmitry Gutov
2023-10-25 12:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 14:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 16:04 ` Eli Zaretskii
2023-10-26 0:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 12:03 ` Eli Zaretskii
2023-10-25 13:06 ` Dmitry Gutov
2023-10-25 13:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 13:40 ` Dmitry Gutov
2023-10-26 0:07 ` Jim Porter
2023-10-26 0:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 0:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 1:19 ` Jim Porter
2023-10-26 1:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 3:48 ` Jim Porter
2023-10-26 5:56 ` Jim Porter
2023-10-26 7:09 ` Eli Zaretskii
2023-10-26 2:37 ` Drew Adams
2023-10-26 2:28 ` Drew Adams
2023-10-26 5:21 ` Eli Zaretskii
2023-10-25 13:57 ` Eli Zaretskii
2023-10-25 15:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 16:08 ` Eli Zaretskii
2023-10-25 16:10 ` Dmitry Gutov
2023-10-25 16:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 0:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 18:19 ` Mattias Engdegård
2023-10-25 18:40 ` Eli Zaretskii
2023-10-25 19:09 ` Mattias Engdegård
2023-10-25 23:43 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 0:07 ` Jim Porter
2023-10-26 2:34 ` Drew Adams
2023-10-26 3:56 ` Jim Porter
2023-10-26 5:22 ` Eli Zaretskii
2023-10-26 6:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 13:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 14:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 15:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 8:32 ` Mattias Engdegård
2023-10-26 11:39 ` Nikolay Kudryavtsev
2023-10-26 15:36 ` Drew Adams
2023-10-25 12:36 ` Nikolay Kudryavtsev
2023-10-25 12:48 ` Dmitry Gutov
2023-10-26 11:06 ` Nikolay Kudryavtsev
2023-10-25 2:27 ` Eli Zaretskii
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=jwv8r7qyla3.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=66706@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mattias.engdegard@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@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).