* bug#8422: 24.0.50; doc of `apropos-internal'
@ 2011-04-04 16:13 Drew Adams
2011-07-15 12:39 ` Lars Magne Ingebrigtsen
2016-04-28 10:33 ` Lars Ingebrigtsen
0 siblings, 2 replies; 4+ messages in thread
From: Drew Adams @ 2011-04-04 16:13 UTC (permalink / raw)
To: 8422
Please add to the doc string some info about what the context is
when/where PREDICATE is invoked. Suppose, for instance, you wanted to
use a PREDICATE such as this:
(lambda (c)
(and (commandp c)
(where-is-internal c overriding-local-map 'non-ascii))
The behavior of the PREDICATE depends on which buffer is current when it
is invoked. Can we assume that the buffer is the same one as when
`apropos-internal' was invoked? Likewise wrt the selected window.
To find this info, users currently need to look at the C source code.
In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
of 2011-04-04 on 3249CTO
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.5) --no-opt --cflags
-Ic:/imagesupport/include'
^ permalink raw reply [flat|nested] 4+ messages in thread* bug#8422: 24.0.50; doc of `apropos-internal'
2011-04-04 16:13 bug#8422: 24.0.50; doc of `apropos-internal' Drew Adams
@ 2011-07-15 12:39 ` Lars Magne Ingebrigtsen
2016-04-28 10:33 ` Lars Ingebrigtsen
1 sibling, 0 replies; 4+ messages in thread
From: Lars Magne Ingebrigtsen @ 2011-07-15 12:39 UTC (permalink / raw)
To: Drew Adams; +Cc: 8422
"Drew Adams" <drew.adams@oracle.com> writes:
> Please add to the doc string some info about what the context is
> when/where PREDICATE is invoked. Suppose, for instance, you wanted to
> use a PREDICATE such as this:
>
> (lambda (c)
> (and (commandp c)
> (where-is-internal c overriding-local-map 'non-ascii))
>
> The behavior of the PREDICATE depends on which buffer is current when it
> is invoked. Can we assume that the buffer is the same one as when
> `apropos-internal' was invoked? Likewise wrt the selected window.
>
> To find this info, users currently need to look at the C source code.
That sounds reasonable, but I'm not quite sure that's how the predicate
is meant to be used. That is, I'm not sure it's an implementation
detail what buffer the predicate is called from, or whether it's
supposed to be that way.
Anybody know?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#8422: 24.0.50; doc of `apropos-internal'
2011-04-04 16:13 bug#8422: 24.0.50; doc of `apropos-internal' Drew Adams
2011-07-15 12:39 ` Lars Magne Ingebrigtsen
@ 2016-04-28 10:33 ` Lars Ingebrigtsen
2016-04-28 13:48 ` Drew Adams
1 sibling, 1 reply; 4+ messages in thread
From: Lars Ingebrigtsen @ 2016-04-28 10:33 UTC (permalink / raw)
To: Drew Adams; +Cc: 8422
"Drew Adams" <drew.adams@oracle.com> writes:
> Please add to the doc string some info about what the context is
> when/where PREDICATE is invoked. Suppose, for instance, you wanted to
> use a PREDICATE such as this:
>
> (lambda (c)
> (and (commandp c)
> (where-is-internal c overriding-local-map 'non-ascii))
>
> The behavior of the PREDICATE depends on which buffer is current when it
> is invoked. Can we assume that the buffer is the same one as when
> `apropos-internal' was invoked? Likewise wrt the selected window.
>
> To find this info, users currently need to look at the C source code.
Uhm... no. As far as I can see, apropos-internal does nothing weird
like changing buffers or windows? So it would be rather odd to document
that it doesn't do <one weird thing>. Other mapping functions like
`sort' certainly doesn't. Closing.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#8422: 24.0.50; doc of `apropos-internal'
2016-04-28 10:33 ` Lars Ingebrigtsen
@ 2016-04-28 13:48 ` Drew Adams
0 siblings, 0 replies; 4+ messages in thread
From: Drew Adams @ 2016-04-28 13:48 UTC (permalink / raw)
To: Lars Ingebrigtsen; +Cc: 8422
> Uhm... no. As far as I can see, apropos-internal does nothing weird
> like changing buffers or windows? So it would be rather odd to document
> that it doesn't do <one weird thing>. Other mapping functions like
> `sort' certainly doesn't. Closing.
That contradicts what a certain Lars Ingebrigtsen wrote in
this bug thread in 2011:
> To find this info, users currently need to look at the C source code.
That sounds reasonable, but I'm not quite sure that's how the predicate
is meant to be used. That is, I'm not sure it's an implementation
detail what buffer the predicate is called from, or whether it's
supposed to be that way.
Anybody know?
Of course, we all have the right to change our minds. ;-)
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-04-28 13:48 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-04-04 16:13 bug#8422: 24.0.50; doc of `apropos-internal' Drew Adams
2011-07-15 12:39 ` Lars Magne Ingebrigtsen
2016-04-28 10:33 ` Lars Ingebrigtsen
2016-04-28 13:48 ` Drew Adams
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).