unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Juri Linkov <juri@linkov.net>
Cc: 29713@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#29713: 26.0; Provide completion for `make-frame-on-display'
Date: Wed, 24 Mar 2021 21:59:42 +0000	[thread overview]
Message-ID: <878s6c2oxd.fsf@tcd.ie> (raw)
In-Reply-To: <87mtv0nzam.fsf@mail.linkov.net> (Juri Linkov's message of "Thu,  18 Mar 2021 19:32:01 +0200")

Juri Linkov <juri@linkov.net> writes:

>> Maybe fall back to previous implementation replaced by x-display-list
>> in 0746a9e275d, i.e.
>>
>>   (if (fboundp 'x-display-list)
>>       (x-display-list)
>>     (delete-dups
>>      (mapcar (lambda (frame)
>>                (frame-parameter frame 'display))
>>              (frame-list))))
>
> Or maybe better to fall back to 'make-frame'?
> I.e. don't signal an error, don't ask a question,
> just create a new frame on the current display.
>
> So on --without-x builds, make-frame-on-display
> could be like an alias to make-frame.

I have no strong preference between this option or just signalling an
error in the interactive spec.  What do others think?

Thanks,

-- 
Basil





  reply	other threads:[~2021-03-24 21:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 20:40 bug#29713: 26.0; Provide completion for `make-frame-on-display' Drew Adams
2019-07-14 18:04 ` Lars Ingebrigtsen
2019-07-14 19:46   ` Juri Linkov
2019-07-14 22:17     ` Drew Adams
2019-07-15 10:14     ` Robert Pluim
2019-07-15 22:09     ` Juri Linkov
2021-03-18 14:02     ` Basil L. Contovounesios
2021-03-18 14:36       ` Eli Zaretskii
2021-03-18 15:09         ` Basil L. Contovounesios
2021-03-18 15:50           ` Eli Zaretskii
2021-03-18 17:04       ` Juri Linkov
2021-03-18 17:32         ` Juri Linkov
2021-03-24 21:59           ` Basil L. Contovounesios [this message]
2021-03-25  6:16             ` Eli Zaretskii
2021-03-25  9:38               ` Juri Linkov
2021-03-26 17:42                 ` Basil L. Contovounesios
2021-03-24 21:57         ` Basil L. Contovounesios

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=878s6c2oxd.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=29713@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=larsi@gnus.org \
    /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).