From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@linkov.net>
Cc: 44932@debbugs.gnu.org
Subject: bug#44932: 28.0.50; MINIBUF 'nomini' for window-in-direction
Date: Mon, 30 Nov 2020 10:05:41 +0100 [thread overview]
Message-ID: <5dbd99a5-a51e-318f-0c9d-81dae921af96@gmx.at> (raw)
In-Reply-To: <87h7p8zeim.fsf@mail.linkov.net>
>> One day we should make up our mind whether we want this arg to be called
>> MINI, MINIBUF or MINIBUFFER. I have no personal preference but the
>> current state (in particular on the C-level) confuses the hell out of
>> me.
>
> I think MINIBUF is the shortest that is still unambiguous.
It gives the impression that it stands for a buffer where it means a
window that may also display the echo area. 'resize-mini-windows' and
'max-mini-window-height' tried to establish the "mini-windows (the
minibuffer and the echo area)" nomenclature and we now take a step back
in the other direction?
> Now at least renaming in window-in-direction is pushed to master.
And left MINI in the .texi file. I spent some time trying to make
manual and doc-strings congruent in this regard ...
martin
next prev parent reply other threads:[~2020-11-30 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 20:40 bug#44932: 28.0.50; MINIBUF 'nomini' for window-in-direction Juri Linkov
2020-11-29 8:22 ` martin rudalics
2020-11-29 19:49 ` Juri Linkov
2020-11-30 9:05 ` martin rudalics [this message]
2020-11-30 20:49 ` Juri Linkov
2020-11-30 21:09 ` Drew Adams
2020-12-01 3:24 ` Eli Zaretskii
2020-12-01 9:34 ` martin rudalics
[not found] <<87r1odtdtx.fsf@mail.linkov.net>
[not found] ` <<342c23a3-e379-452c-6c5e-29dab7592c28@gmx.at>
[not found] ` <<87h7p8zeim.fsf@mail.linkov.net>
[not found] ` <<5dbd99a5-a51e-318f-0c9d-81dae921af96@gmx.at>
[not found] ` <<87eekaa8au.fsf@mail.linkov.net>
[not found] ` <<27c3eec9-5675-47ae-937e-b5440becf6b6@default>
[not found] ` <<83sg8qi4yy.fsf@gnu.org>
2020-12-01 3:49 ` Drew Adams
2020-12-01 15:38 ` 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=5dbd99a5-a51e-318f-0c9d-81dae921af96@gmx.at \
--to=rudalics@gmx.at \
--cc=44932@debbugs.gnu.org \
--cc=juri@linkov.net \
/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.