unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: help-gnu-emacs@gnu.org
Subject: Re: Annoying arrow key scroll behaviour in emacs 27
Date: Wed, 01 Dec 2021 20:18:19 +0100	[thread overview]
Message-ID: <upzc35nccex0.fsf@dod.no> (raw)
In-Reply-To: <8735ncffc3.fsf@gmail.com> (Robert Pluim's message of "Wed, 01 Dec 2021 17:41:00 +0100")

>>>>> Robert Pluim <rpluim@gmail.com>:

> What are the values of 'focus-in-hook', 'focus-out-hook', and
> 'after-focus-change-function'?

In a regular emacs:

focus-in-hook is a variable defined in ‘frame.el’.
Its value is (flycheck-display-error-at-point-soon t)
Local in buffer index.js<bokbase.web.frontend/src/main/frontend/src>; global value is nil

focus-out-hook is a variable defined in ‘frame.el’.
Its value is (flycheck-cancel-error-display-error-at-point-timer t)
Local in buffer index.js<bokbase.web.frontend/src/main/frontend/src>; global value is nil

after-focus-change-function is a variable defined in ‘frame.el’.
Its value is
#f(advice-wrapper :after ignore blink-cursor--rescan-frames)


In "emacs -Q" (which also toggles scroll-lock-mode when the window is selected):

focus-in-hook is a variable defined in ‘frame.el’.
Its value is nil

focus-out-hook is a variable defined in ‘frame.el’.
Its value is nil

after-focus-change-function is a variable defined in ‘frame.el’.
Its value is
#f(advice-wrapper :after ignore blink-cursor--rescan-frames)



  reply	other threads:[~2021-12-01 19:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-28 20:57 Annoying arrow key scroll behaviour in emacs 27 xenodasein--- via Users list for the GNU Emacs text editor
2021-11-29 17:03 ` Steinar Bang
2021-11-29 17:26   ` Steinar Bang
2021-11-29 22:24     ` Michael Heerdegen
2021-12-01  6:32       ` Steinar Bang
2021-12-01 16:17         ` Steinar Bang
2021-12-01 16:26           ` Steinar Bang
2021-12-01 16:41             ` Robert Pluim
2021-12-01 19:18               ` Steinar Bang [this message]
2021-12-01 21:47                 ` Michael Heerdegen
2021-12-01 16:52             ` Michael Heerdegen
2021-12-01 19:13               ` Steinar Bang
2021-12-01 19:21                 ` Eli Zaretskii
2021-12-02 17:21                   ` Steinar Bang
2021-12-02 17:27                     ` Michael Heerdegen
2021-12-02 17:43                       ` Steinar Bang
2021-12-02 17:53                         ` Steinar Bang
2021-12-02 18:04                           ` Michael Heerdegen
2021-12-02 18:44                           ` Eli Zaretskii
2021-12-02 19:13                             ` Steinar Bang
2021-12-02 18:27                     ` Eli Zaretskii
2021-12-02 18:33                       ` Steinar Bang
  -- strict thread matches above, loose matches on Subject: below --
2021-11-28 20:16 Steinar Bang
2021-11-29 10:15 ` Tassilo Horn
2021-11-29 17:07   ` Steinar Bang

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=upzc35nccex0.fsf@dod.no \
    --to=sb@dod.no \
    --cc=help-gnu-emacs@gnu.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).