From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 44932@debbugs.gnu.org, juri@linkov.net
Subject: bug#44932: 28.0.50; MINIBUF 'nomini' for window-in-direction
Date: Mon, 30 Nov 2020 19:49:44 -0800 (PST) [thread overview]
Message-ID: <54f141f9-0861-4b2e-a87c-db1c5253bd7f@default> (raw)
In-Reply-To: <<83sg8qi4yy.fsf@gnu.org>>
> > > I don't know why MINI-WINDOW would be better than
> > > MINIBUF. Is this distinction significant here?
> >
> > IMHO, MINI-WINDOW would be worse. It's not
> > about a small window.
>
> "Mini-window" is accepted terminology in Emacs, it is used, e.g., in
> resize-mini-windows. So there's nothing wrong with using that. (And
> yes, usually that window _is_ small.)
You're discussing only how to refer to this
parameter in doc strings. I contributed my 2 cents.
As for the "accepted terminology" of "mini-window",
I've also given my opinion about that unfortunate
name more generally:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=11276#24
"it is wrong to use only "mini" here. This is not
just a mini-window, i.e., a small window - it is a
minibuffer window. See bug #3320, deemed "wont-fix"
by Lars:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3320.
Perhaps now that others consider that
`resize-mini-windows' is a misnomer (for
additional reasons), this misuse of "mini" can
be reconsidered."
Bug #3320 was filed at the request of another who also
felt that such "accepted terminology" is unfortunate:
"these misleading names have bitten me too."
> it is used, e.g., in resize-mini-windows"
And now what was discussed as a bad-name bug has
been canonized as a model of good naming.
You have a chance now, when considering parameter
names, to start to put things on the right track,
even if you don't rename `resize-mini-windows'.
Multiplying wrongs doesn't make a right.
next parent reply other threads:[~2020-12-01 3:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2020-12-01 15:38 ` bug#44932: 28.0.50; MINIBUF 'nomini' for window-in-direction Eli Zaretskii
2020-11-28 20:40 Juri Linkov
2020-11-29 8:22 ` martin rudalics
2020-11-29 19:49 ` Juri Linkov
2020-11-30 9:05 ` martin rudalics
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
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=54f141f9-0861-4b2e-a87c-db1c5253bd7f@default \
--to=drew.adams@oracle.com \
--cc=44932@debbugs.gnu.org \
--cc=eliz@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.