From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: martin rudalics <rudalics@gmx.at>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: simplifying windmove-frame-edges
Date: Fri, 25 Oct 2019 14:17:23 +0200 [thread overview]
Message-ID: <CAAeL0SRCmCywenz6SshMhpvVH6PB0LOs-u15V=JUsweS4Qspig@mail.gmail.com> (raw)
In-Reply-To: <83h83yxmgg.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 399 bytes --]
On Thu, Oct 24, 2019 at 4:11 PM Eli Zaretskii <eliz@gnu.org> wrote:
> We cannot just delete them, we need to obsolete them first. They were
> with us for far too long.
I find the argument less than compelling, given the fact that the functions
have been known not to work well in some cases for the past six years or so.
But you're the boss.
Here's the patch, split in three parts for clarity.
[-- Attachment #1.2: Type: text/html, Size: 562 bytes --]
[-- Attachment #2: 0001-windmove.el-Obsolete-code-not-used-since-2013.patch --]
[-- Type: application/x-patch, Size: 4031 bytes --]
[-- Attachment #3: 0002-windmove.el-Fix-docstrings-not-to-refer-to-obsolete-.patch --]
[-- Type: application/x-patch, Size: 1975 bytes --]
[-- Attachment #4: 0003-windmove.el-Remove-comments-about-the-old-implementa.patch --]
[-- Type: application/x-patch, Size: 11568 bytes --]
next prev parent reply other threads:[~2019-10-25 12:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 11:54 simplifying windmove-frame-edges Juanma Barranquero
2019-10-23 16:05 ` martin rudalics
2019-10-23 18:10 ` Juanma Barranquero
2019-10-24 6:44 ` martin rudalics
2019-10-24 14:11 ` Eli Zaretskii
2019-10-25 12:17 ` Juanma Barranquero [this message]
2019-10-25 12:51 ` Eli Zaretskii
2019-10-25 13:13 ` Juanma Barranquero
2019-10-25 13:42 ` Eli Zaretskii
2019-10-25 14:05 ` Juanma Barranquero
2019-10-24 9:12 ` Phil Sainty
2019-10-24 9:37 ` Juanma Barranquero
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='CAAeL0SRCmCywenz6SshMhpvVH6PB0LOs-u15V=JUsweS4Qspig@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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).