unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Will Monroe <wtmonroe.ls@gmail.com>,
	Marcin Borkowski <mbork@wmi.amu.edu.pl>,
	help-gnu-emacs@gnu.org
Subject: RE: Advice on troubleshooting function to "unscroll"
Date: Sun, 25 Jan 2015 17:33:20 -0800 (PST)	[thread overview]
Message-ID: <05bf1f27-c5d9-4930-ab5e-ea5170fe993b@default> (raw)
In-Reply-To: <54C595A7.9020204@gmail.com>

> I'll have to go back and look at what "interactive" actually means.

It means that you invoked it by name or via a key binding (which
includes a menu-item binding).

More precisely, it means that `called-interactively-p' returns
non-nil.  See also `interactive-p'.

> 'scroll-up' is advised (and invoked?) in the code below.

Advised, not invoked.  Invoked means called.  `scroll-up' is not
called in the advice definition you show.

> Not sure if that means that I am also invoking it interactively.

The advice applies whenever and however the function is called,
in particular, whether it is called interactively or not.

> I thought being invoked, "as a command", meant that I was
> invoking it using `M-x scroll-up`.

`M-x' invokes commands interactively, but it is not the only way
to do that - see above.  Note that `M-: (scroll-up)' does *not*
invoke `scroll-up' interactively.

> Marcin, I also wondering what prompted the addition of
> scroll-up-command.  I think Drew addresses this but I probably need to
> look at the docstrings for both to grasp it more clearly.

Look too at the beginning of the code for `scroll-up-command':
  (cond ((null scroll-error-top-bottom)
         (scroll-up arg))
        ...

That tells you that when the option is nil (the default value)
`scroll-up-command' just calls `scroll-up'.



  parent reply	other threads:[~2015-01-26  1:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-25 20:52 Advice on troubleshooting function to "unscroll" Will Monroe
2015-01-25 21:35 ` Marcin Borkowski
2015-01-25 21:43   ` Will Monroe
2015-01-25 21:55     ` Marcin Borkowski
2015-01-25 22:01       ` Will Monroe
2015-01-25 21:45 ` Marcin Borkowski
2015-01-25 22:03   ` Will Monroe
2015-01-25 22:09     ` Marcin Borkowski
2015-01-25 22:45     ` Drew Adams
2015-01-25 22:56       ` Will Monroe
2015-01-25 23:15         ` Marcin Borkowski
2015-01-26  0:03         ` Drew Adams
2015-01-26  0:16           ` Marcin Borkowski
2015-01-26  1:06             ` Drew Adams
2015-01-26  1:17             ` Will Monroe
2015-01-26  1:21               ` Marcin Borkowski
2015-01-26  1:33               ` Drew Adams [this message]
     [not found] <mailman.18583.1422219396.1147.help-gnu-emacs@gnu.org>
2015-01-25 21:35 ` Joost Kremers
2015-01-25 21:57   ` Will Monroe

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=05bf1f27-c5d9-4930-ab5e-ea5170fe993b@default \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=mbork@wmi.amu.edu.pl \
    --cc=wtmonroe.ls@gmail.com \
    /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).