Faster edit several code-objects, called THING here.
Commands for a lot of known code objects as `symbol', `list', `sexp', `defun' are provided already.
Maybe have a look thing-at-
If not delivered, all what's needed is a function, which will determine the beginning resp. the end of the object.
(put 'MY-FORM 'beginning-op-at
(lambda () MY-FORWARD-
(put 'MY-FORM 'end-op-at
(lambda () MY-BACKWARD-
When done, it's should be available, i.e. copied and returned like this
(defun MY-FORM-atpt (&optional arg)
(ar-th 'MY-FORM arg))
Now a whole bunch of commands WRT to MY-FORM below called THING are available:
Also a couple of commands, whose use is much less probable:
Other Files in this project:
thing-in-thing.el employs a defined THING within the
range of a second THING.
insides brackets within the given line. Resp.
Caveat: thing-in-thing files deliver a large number of commands
resp. symbols, so `apropos'-output might get
Beside of `thing-
it's not recommended loading them all at the beginning.
Which implementations are to be expected, see the contents of lists at the bottom of
For example `M-x ar-doubleslash-
which would turn an active region of
foo bar baz
\\(foo\\) \\(bar\\) \\(baz\\)
It resides in thing-classes-
It's in "ar-atpt-rest-list" were forms employing common items like
`word', `region', `line', `paragraph' are stored.
M-x find . -maxdepth 1 -type f -name "*.el" -print0 | xargs -0 -e grep -nH -e MY_FORMS_WANTED
called from inside thing-in-thing dired-directory should help.
Comment-lor.el: it's suffix `-lor' means
`line-or-region': If no active region exists, line is
commented or uncommented. Thus taking action to mark
a region is no longer needed.
All blueprints Latest blueprints
Registered on 2013-10-10
Registered on 2012-06-20
Establish rules for related functions return values
Registered on 2010-10-07