all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: eggert@cs.ucla.edu, 50444@debbugs.gnu.org
Subject: bug#50444: Remove support for the curses library
Date: Tue, 07 Sep 2021 09:03:41 +0300	[thread overview]
Message-ID: <83zgsoq5vm.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkTRZFiaSFz1d+fKiVwKWdP-AC8g87D4YngiAo4wraMNw@mail.gmail.com> (message from Stefan Kangas on Tue, 7 Sep 2021 02:28:31 +0200)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Tue, 7 Sep 2021 02:28:31 +0200
> Cc: paul eggert <eggert@cs.ucla.edu>
> 
> Building with curses is, according to Paul Eggert:
> 
>     "Completely broken" in the sense it won't link and Emacs won't build,
>     yes. (It will link in master, due to a patch I installed recently.)
> 
>     And yes, the original curses library has been obsolete for at least two
>     decades.
> 
> See the discussion here:
> https://lists.gnu.org/archive/html/emacs-devel/2021-01/msg00416.html
> 
> The conclusion from that thread AFAIU is that support for curses
> should be removed.  (We should keep ncurses though.)

Doesn't that mean we will be removing support for AIX (and any other
systems that cannot use ncurses due to the same problem)?  Are we
willing to drop support for those platforms because of curses?  AFAIU,
the original problem was fixed, and there's no longer a link error
when using curses.

In any case, if we are planning to drop support for curses, we need
to obsolete it first, i.e. add a configure-time warning for that.





  reply	other threads:[~2021-09-07  6:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07  0:28 bug#50444: Remove support for the curses library Stefan Kangas
2021-09-07  6:03 ` Eli Zaretskii [this message]
2021-09-07  6:41   ` Paul Eggert
2021-09-07  6:44     ` Stefan Kangas
2021-09-08  3:28   ` Richard Stallman

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=83zgsoq5vm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=50444@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --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 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.