unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Subject: proposal: obsolete-var-funcs.el or compatibility-var-funcs.el
Date: Thu, 13 Oct 2022 14:22:17 +0200	[thread overview]
Message-ID: <878rljzzeu.fsf@mat.ucm.es> (raw)


Hi 

The latest master has caused me some headaches, because according to the
NEWS file a lot of obsolete variables and functions have been removed.

In some cases these definitions are rather simple, like 


(define-obsolete-function-alias 'set-face-underline-p
                                'set-face-underline "24.3")

(defcustom gnus-local-domain nil
  "Local domain name without a host name.
The DOMAINNAME environment variable is used instead if it is defined.
If the function `system-name' returns the full Internet name, there is
no need to set this variable."
  :group 'gnus-message
  :type '(choice (const :tag "default" nil)
		 string))
(make-obsolete-variable 'gnus-local-domain nil "24.1")

So could such simple definitions just moved to a file 

obsolete-var-funcs.el or compatibility-var-funcs.el

Instead of being deleted.

That would help users who for one or the other reason still rely on old
code, can try to survive for a bit longer.

Regards

Uwe Brauer 


-- 
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine. 




             reply	other threads:[~2022-10-13 12:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13 12:22 Uwe Brauer [this message]
2022-10-13 16:35 ` proposal: obsolete-var-funcs.el or compatibility-var-funcs.el Stefan Monnier
2022-10-13 16:47   ` Uwe Brauer
2022-10-13 20:04     ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2022-10-13 15:12 Uwe Brauer

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=878rljzzeu.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --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 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).