[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#13687: /srv/bzr/emacs/trunk r111878: * lisp/replace.el(read-regexp):

From: Jambunathan K
Subject: bug#13687: /srv/bzr/emacs/trunk r111878: * lisp/replace.el(read-regexp): Let-bind `default' to the first
Date: Sat, 09 Mar 2013 00:00:11 +0530
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

"Drew Adams" <address@hidden> writes:

> E.g., in the code I cited, if a user does not want the same defaulting
> behavior for commands `occur', `how-many', etc., she can set option
> `search/replace-default-fn' to a function that distinguishes them
> (e.g., using `this-command', as Jambunathan suggested).

Interesting suggestion there.

This makes me think that there is no need for multiple
`hi-lock-read-regexp-defaults-function' and a separate
`occur-read-regexp-defaults-function' etc.  But a single
`read-regexp-defaults-function' that cases on `this-command'.

The function can return a symbol token like `t' for `this-command's
which it doesn't want to meddle with but return nil or a regexp or list
of regexps for commands it wants to insinuate.

Is there any problem with this `read-regexp-defaults-function' approach?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]