From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Robert Pluim <rpluim@gmail.com>, emacs-devel@gnu.org
Subject: Re: master 57d2f24: * lisp/frame.el (make-frame-on-monitor): New command. (Bug#34516)
Date: Wed, 27 Feb 2019 22:59:03 +0200 [thread overview]
Message-ID: <877edluew8.fsf@mail.linkov.net> (raw)
In-Reply-To: <83ef7umv4v.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 26 Feb 2019 17:23:12 +0200")
>> Iʼve lost track: did we still want to fake monitor names on recent
>> versions of macOS where the existing name retrieval methods donʼt work
>> anymore?
Yes, please add fake monitor names to support this command on macOS too.
> In any case, this new command needs to be documented in the user
> manual. Please don't leave NEWS as the only documentation.
Now it's documented in the user manual.
But I'm not sure about the menu. Currently the File menu contains:
"New Frame on Display..."
but the File menu already is so long that I think a new menu item like
"New Frame on Monitor..."
won't fit into it.
For the same reason I haven't added a menu item for ‘vc-root-version-diff’
to another overly long menu ‘vc-menu-map’.
BTW, a related question about the menu: shouldn't the menu item
"Search Files (Grep)..." run a more user-friendly command ‘rgrep’
instead of ‘grep’?
next prev parent reply other threads:[~2019-02-27 20:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190225211142.21954.14993@vcs0.savannah.gnu.org>
[not found] ` <20190225211144.0DD23206A2@vcs0.savannah.gnu.org>
2019-02-26 9:12 ` master 57d2f24: * lisp/frame.el (make-frame-on-monitor): New command. (Bug#34516) Robert Pluim
2019-02-26 15:23 ` Eli Zaretskii
2019-02-27 20:59 ` Juri Linkov [this message]
2019-02-28 9:38 ` Robert Pluim
2019-02-28 16:52 ` Robert Pluim
2019-02-28 20:40 ` Juri Linkov
2019-03-01 13:40 ` Robert Pluim
2019-03-02 21:09 ` Juri Linkov
2019-03-03 1:05 ` Drew Adams
2019-03-03 21:30 ` Juri Linkov
2019-03-04 0:01 ` Drew Adams
2019-03-04 8:53 ` Robert Pluim
2019-02-28 18:11 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877edluew8.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.