unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@online.de>
To: emacs-devel@gnu.org
Cc: Barry Warsaw <barry@python.org>, Eli Zaretskii <eliz@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: python minor-mode
Date: Thu, 7 Apr 2022 09:49:14 +0200	[thread overview]
Message-ID: <443acc41-a840-09ab-305c-97b5327174d5@online.de> (raw)
In-Reply-To: <jwvo81yju38.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 942 bytes --]


Am 22.03.22 um 09:07 schrieb Stefan Monnier:
> [...]
> I don't really know how the two compare in functionality, but based on
> size, I'd guess that we'd end up with Emacs's python.el being the "core"
> mode and `python-mode.el` being the "derived" mode that provides
> extra features.  Depending on how things end up, the derived mode could
> be replaced with a minor mode.

An interesting idea, which may reduce the burden of maintenance on  both 
sides.

The point I'm afraid of: For example, if python-mode.el uses python.el's 
setup-code machinery, it might want to modify vars there.

Afterwards it will be not obvious, wherefrom values are set. For now 
there should be no conflict, beside of the name of the major-mode itself.

So, not sure if proceeding in that direction would make sense.

Best,

Andreas

> In any case, it's a non-trivial job which would require
> someone to figure out all the details.
>
>
>          Stefan
>
>

[-- Attachment #2: Type: text/html, Size: 1587 bytes --]

      reply	other threads:[~2022-04-07  7:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21  8:19 python minor-mode Andreas Röhler
2022-03-21 12:35 ` Eli Zaretskii
2022-03-21 13:37 ` T.V Raman
2022-03-21 15:20   ` Barry Warsaw
2022-03-21 16:09     ` T.V Raman
2022-04-01  0:31       ` Barry Warsaw
2022-04-01 13:55         ` T.V Raman
2022-04-01 18:09           ` Barry Warsaw
2022-04-02  1:39             ` T.V Raman
2022-03-22  8:07 ` Stefan Monnier
2022-04-07  7:49   ` Andreas Röhler [this message]

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=443acc41-a840-09ab-305c-97b5327174d5@online.de \
    --to=andreas.roehler@online.de \
    --cc=barry@python.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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).