[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "Final" version of tty child frames
From: |
Gerd Möllmann |
Subject: |
Re: "Final" version of tty child frames |
Date: |
Thu, 12 Dec 2024 08:04:17 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Thu, 12 Dec 2024 00:11:01 -0500
>> From: Jared Finder <jared@finder.org>
>> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org, rudalics@gmx.at
>>
>> I think it would be good for unimplemented features to communicate that
>> state to the user so users know clearly what is going on. Right now the
>> error a user sees is "Can’t change the ‘minibuffer’ parameter of this
>> frame". Wouldn't it be better to have make-terminal-frame (a brand new
>> function with no existing clients to support) error with something like
>> "Minibuffer only frames are not supported in terminals"?
>
> I think minibuffer-only frames _are_ implemented on TTYs (albeit not
> very useful there). They are not implemented as child frames, I
> think.
>
> But yes, emitting an explicit error message about something not
> implemented would be definitely better.
Pushed something like that to the branch.
Re: "Final" version of tty child frames, martin rudalics, 2024/12/11