From: Nick Roberts <nickrob@snap.net.nz>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Incompatible change without "warning"
Date: Mon, 2 May 2005 10:43:31 +1200 [thread overview]
Message-ID: <17013.23443.440554.608805@farnswood.snap.net.nz> (raw)
In-Reply-To: <E1DSJcv-0003d8-G9@fencepost.gnu.org>
> Quite a lot with no timestamp.
>
> They might be obsolete since long long ago. What are they?
desktop.el: desktop-enable
desktop-buffer-modes-to-save
desktop-buffer-misc-functions
desktop-buffer-handlers
desktop-load-default
dired-x.el: dired-omit-files-p
font-core.el: font-lock-defaults-alist
font-lock.el: font-lock-reference-face
log-edit.el: cvs-commit-buffer-require-final-newline
cvs-changelog-full-paragraphs
mwheel.el: mouse-wheel-down-button
mouse-wheel-up-button
mouse-wheel-click-button
outline.el: outline-visible
pcvs-defs.el: cvs-diff-ignore-marks
cvs-diff-buffer-name
subr.el: assoc-ignore-case
assoc-ignore-representation
tree-widget.el: tree-widget-format-handler
vc-hooks.el: vc-ignore-vc-files
vc-master-templates
vc-header-alist
cc-cmds.el: c-comment-line-break-function
cc-vars.el: c-comment-continuation-stars
compile.el: compile-internal
next prev parent reply other threads:[~2005-05-01 22:43 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 14:48 Incompatible change without "warning" Frank Schmitt
2005-04-19 19:09 ` Eli Zaretskii
2005-04-19 20:53 ` Nick Roberts
2005-04-19 21:25 ` Stefan Monnier
2005-04-19 22:10 ` Kevin Rodgers
2005-04-20 14:57 ` Richard Stallman
2005-04-20 23:21 ` Nick Roberts
2005-04-21 14:17 ` Lute Kamstra
2005-04-21 22:35 ` Nick Roberts
2005-04-22 9:46 ` Lute Kamstra
2005-04-22 21:32 ` Nick Roberts
2005-04-23 7:17 ` Lute Kamstra
2005-04-23 7:31 ` David Kastrup
2005-04-23 19:25 ` Lute Kamstra
2005-04-23 8:10 ` Nick Roberts
2005-04-23 9:44 ` Eli Zaretskii
2005-04-23 19:27 ` Lute Kamstra
2005-04-21 19:56 ` Richard Stallman
2005-04-21 23:14 ` Nick Roberts
2005-04-21 23:56 ` Lute Kamstra
2005-04-23 16:15 ` Richard Stallman
2005-04-26 9:15 ` Nick Roberts
2005-04-26 21:06 ` Stefan Monnier
2005-04-26 21:35 ` Nick Roberts
2005-04-26 21:45 ` Stefan Monnier
[not found] ` <20050430231856.CE9369F511@mirror.positive-internet.com>
2005-05-01 3:50 ` Nick Roberts
2005-05-01 12:07 ` Richard Stallman
2005-05-01 14:06 ` Nick Roberts
2005-05-01 15:18 ` Luc Teirlinck
2005-05-01 23:39 ` Richard Stallman
2005-05-02 2:28 ` Luc Teirlinck
2005-05-01 18:57 ` Richard Stallman
2005-05-01 21:18 ` Luc Teirlinck
2005-05-01 18:57 ` Richard Stallman
2005-05-01 18:57 ` Richard Stallman
2005-05-01 22:43 ` Nick Roberts [this message]
2005-05-02 7:38 ` David Kastrup
2005-05-02 22:55 ` Nick Roberts
2005-05-03 4:31 ` Luc Teirlinck
2005-05-03 7:17 ` David Kastrup
2005-05-04 22:04 ` Richard Stallman
2005-05-03 17:12 ` Richard Stallman
2005-05-02 23:40 ` Richard Stallman
2005-05-02 15:21 ` Richard Stallman
2005-04-20 14:57 ` Richard Stallman
2005-04-19 21:35 ` Nick Roberts
2005-04-20 23:14 ` Luc Teirlinck
2005-04-21 0:56 ` Nick Roberts
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=17013.23443.440554.608805@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--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).