unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 12436@debbugs.gnu.org
Subject: bug#12436: 24.2.50; rename `(next|previous)-multiframe-window'
Date: Thu, 28 Apr 2016 19:23:03 +0200	[thread overview]
Message-ID: <87fuu57img.fsf@gnus.org> (raw)
In-Reply-To: <41448D3E81B245CAA20C88FD41B31D26@us.oracle.com> (Drew Adams's message of "Thu, 13 Sep 2012 09:30:43 -0700")

"Drew Adams" <drew.adams@oracle.com> writes:

> Rename these commands and deprecate the old names.  There is no such
> thing as a multiframe window, which would mean a window on more than one
> frame.  These commands should be called something like:
> `(next|previous)-window-any-frame'.

I agree.  Any objections?  There does not seem to be many users of these
functions:

./frame.el:522:(defun next-multiframe-window ()
./frame.el:530:(defun previous-multiframe-window ()
./term/ns-win.el:105:(define-key global-map [?\s-'] 'next-multiframe-window)


-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2016-04-28 17:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13 16:30 bug#12436: 24.2.50; rename `(next|previous)-multiframe-window' Drew Adams
2016-04-28 17:23 ` Lars Ingebrigtsen [this message]
2019-10-30 22:30   ` Stefan Kangas
2019-10-30 22:46     ` Lars Ingebrigtsen
2019-10-30 23:20     ` Drew Adams
2019-10-31 14:05     ` Eli Zaretskii
2019-11-02  1:37       ` Stefan Kangas
2019-11-05 23:51         ` Stefan Kangas

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=87fuu57img.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=12436@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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).