unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: master 7df302d285 2/2: Remove some XEmacs compat code from pascal.el
Date: Fri, 13 May 2022 21:46:54 +0800	[thread overview]
Message-ID: <87mtfltui9.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkmmeD4Ogx_rck3z_d=w-4K4G1kPD2sMrcMi5U2hMjeB2jQ@mail.gmail.com> (Stefan Kangas's message of "Fri, 13 May 2022 15:29:39 +0200")

Stefan Kangas <stefan@marxist.se> writes:

> No, I don't think we care about that.  We have been routinely removing
> such compat code all over the place for several years now.

Don't we have lots of compat code in things like CC Mode which continue
to work in XEmacs?  The last time I checked, CC Mode does work, but that
was before it was converted to lexical binding.

> IMHO, any XEmacs/SXEmacs users out there should consider using Emacs instead.
>
> See also:
> https://lists.gnu.org/archive/html/emacs-devel/2004-10/msg01211.html
> https://lists.gnu.org/archive/html/emacs-devel/2004-10/msg01294.html

I think the conclusion there was to let people working on the file
decide whether or not to keep support for XEmacs.  So the question is
probably where those people are for pascal.el, and what they think.



  parent reply	other threads:[~2022-05-13 13:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <165244532007.20025.13387232261531378518@vcs2.savannah.gnu.org>
     [not found] ` <20220513123522.302F5C01686@vcs2.savannah.gnu.org>
2022-05-13 13:02   ` master 7df302d285 2/2: Remove some XEmacs compat code from pascal.el Po Lu
2022-05-13 13:29     ` Stefan Kangas
2022-05-13 13:42       ` Lars Ingebrigtsen
2022-05-13 13:46       ` Po Lu [this message]
2022-05-13 13:57         ` Lars Ingebrigtsen
2022-05-13 14:24     ` Stefan Monnier

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=87mtfltui9.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=stefan@marxist.se \
    /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).