Re: [External] : Re: master 927b885 1/3: Disable filtering of commands in M-x completion

[Eli Zaretskii <eliz@gnu.org>]

> From: Drew Adams <drew.adams@oracle.com>
> CC: "juri@linkov.net" <juri@linkov.net>,
>         "stefankangas@gmail.com"
> 	<stefankangas@gmail.com>,
>         "emacs-devel@gnu.org" <emacs-devel@gnu.org>
> Date: Thu, 18 Feb 2021 20:45:55 +0000
> 
> > Are you sure you have no mark?
> 
> No, there's a mark.  (I guess just from
> defining the command or invoking it.)

No, defining a command doesn't set the mark, nor does invoking it.
maybe you've pasted the definition from somewhere?

> But even if `mark-even-if-inactive' is nil,
> the region _exists_, no?

If the mark is set, then the region exists, but it is not necessarily
"active".

> The doc string of `mark-even-if-inactive'
> doesn't actually say what the behavior is
> when nil.

It does here:

  Non-nil means you can use the mark even when inactive.
  This option makes a difference in Transient Mark mode.
  When the option is non-nil, deactivation of the mark
  turns off region highlighting, but commands that use the mark
  behave as if the mark were still active.

As usual, when the description is about what happens when something is
non-nil means that those things do NOT happen when that thing is nil.

> It says only that if NON-nil then "you can
> use the mark" even when inactive.  A guess
> is that if nil then you CANNOT use the mark
> when inactive.  But what does "use the mark"
> really mean, here?

It mentions Transient Mark mode, and that should tell you what that
means.

> I see that the Elisp manual does say that
> an error is raised for `r' if the mark is not
> SET.  But even the manual says nothing about
> what `r' does for an inactive region/mark.

It does now.