all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 29713@debbugs.gnu.org, larsi@gnus.org, juri@linkov.net
Subject: bug#29713: 26.0; Provide completion for `make-frame-on-display'
Date: Thu, 25 Mar 2021 08:16:54 +0200	[thread overview]
Message-ID: <83ft0jkbah.fsf@gnu.org> (raw)
In-Reply-To: <878s6c2oxd.fsf@tcd.ie> (contovob@tcd.ie)

> From: "Basil L. Contovounesios" <contovob@tcd.ie>
> Date: Wed, 24 Mar 2021 21:59:42 +0000
> Cc: 29713@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
> 
> > 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?

I think we should signal an error: the user will not get what they
want, so the user must be told.





  reply	other threads:[~2021-03-25  6:16 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
2021-03-25  6:16             ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ft0jkbah.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=29713@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --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 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.