unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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 15:13:45 +0200	[thread overview]
Message-ID: <CAAeL0STXt7hn4-Ciqmy39SH8q6jTtoS_Gq0a2z50rm16f_7MAQ@mail.gmail.com> (raw)
In-Reply-To: <83imodvvhl.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 645 bytes --]

On Fri, Oct 25, 2019 at 2:51 PM Eli Zaretskii <eliz@gnu.org> wrote:

> The last sentence should be the 2nd, because you mention WINDOW in the
> first sentence of the doc string.

Ok.

> Are these comments really no longer relevant?

They are relevant for the obsolete code, but they are misleading because
they describe an implementation that's no longer used.

I don't think we want to spend time fixing these functions, or any bugs in
them, and we don't want to encourage *more* unbundled packages or user code
using these functions. It's better to strip the comment, put a notice, and
let it be until we feel it's safe to just remove it all.

[-- Attachment #2: Type: text/html, Size: 824 bytes --]

  reply	other threads:[~2019-10-25 13:13 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
2019-10-25 12:51           ` Eli Zaretskii
2019-10-25 13:13             ` Juanma Barranquero [this message]
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=CAAeL0STXt7hn4-Ciqmy39SH8q6jTtoS_Gq0a2z50rm16f_7MAQ@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).