Subject: bug#21195: 25.0.50; Let MARKER arg to `set-marker' be a number

From: Lars Ingebrigtsen <[email-masked]>
Date: Sat, 30 Apr 2016 23:42:53 +0200

Drew Adams <[email-masked]> writes:

> Minor enhancement request.  Let `set-marker' (aka `move-marker') accept
> a buffer position that is just a number as its first arg.  IOW, give
> `set-marker' this behavior:
>
> (defun new-set-marker (num-or-marker position &optional buffer)
>   "..."
>   (unless (markerp num-or-marker)
>     (setq num-or-marker  (with-current-buffer buffer
>                            (copy-marker num-or-marker))))
>   (set-marker num-or-marker position buffer))

Hm...  Well, I don't really see the point.  `set-marker' is so
conceptually clean.  And saying `(set-marker (make-marker) ...)' is so
easy.  Closing.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no