From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 32839@debbugs.gnu.org
Subject: bug#32839: 27.0.50; recenter doesn't redisplay
Date: Mon, 01 Oct 2018 08:34:18 +0300 [thread overview]
Message-ID: <83ftxq44dh.fsf@gnu.org> (raw)
In-Reply-To: <87efdau63h.fsf@mail.linkov.net> (message from Juri Linkov on Sun, 30 Sep 2018 22:40:18 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: 32839@debbugs.gnu.org
> Date: Sun, 30 Sep 2018 22:40:18 +0300
>
> > I don't think I agree. The current name reflects what that argument
> > causes, you just interpret "redisplay" to mean "redraw the frame",
> > which is not an accurate interpretation, since the display engine has
> > its own logic to decide what exactly needs to be redrawn at any
> > particular moment.
>
> When an argument name is a verb in the imperative mood, this means only
> one thing: it should do what it claims it will do.
And it does: it redisplays the current window. It does _not_ always
redisplay other windows, and does _not_ redraw the entire frame unless
another argument tells it to do so.
IOW, "redisplay" is not the same as "redraw the frame". If the
argument's name were "redraw-frame", then I'd agree with you that the
name is misleading.
> > Renaming the argument as you propose would be a step backwards, since
> > it describes the _purpose_ (as opposed to _effect_) of that argument,
> > and that could easily change with further development, and is not
> > accurate even with the current code.
>
> Other commands that use the argument name 'interactive' have the same
> assumption of describing the purpose, not effect.
It is possible that in other cases that name is the best one we found;
or it could be that some of those arguments need to be renamed to
something else. The decision is on a per-case basis, and cannot be
global.
next prev parent reply other threads:[~2018-10-01 5:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 19:11 bug#32839: 27.0.50; recenter doesn't redisplay Juri Linkov
2018-09-25 20:08 ` Eli Zaretskii
2018-09-25 20:55 ` Juri Linkov
2018-09-26 5:39 ` Eli Zaretskii
2018-09-26 23:55 ` Juri Linkov
2018-09-27 6:44 ` Eli Zaretskii
2018-09-27 22:59 ` Juri Linkov
2018-09-28 6:22 ` Eli Zaretskii
2018-09-29 23:32 ` Juri Linkov
2018-09-30 6:08 ` Eli Zaretskii
2018-09-30 19:40 ` Juri Linkov
2018-10-01 5:34 ` Eli Zaretskii [this message]
2018-09-29 23:38 ` Juri Linkov
2018-09-30 6:22 ` Eli Zaretskii
2018-09-30 19:46 ` Juri Linkov
2018-10-01 6:58 ` Eli Zaretskii
2018-10-08 22:56 ` Juri Linkov
2018-10-09 7:44 ` martin rudalics
2020-02-07 0:30 ` Juri Linkov
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=83ftxq44dh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32839@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.