(copy-marker nil)

[Andreas Röhler]

Hi,

being surprised WRT behavior of copy-marker:

(setq a (copy-marker nil)) -> #<marker in no buffer>
(markerp a) -> t
a -> #<marker in no buffer>

Is taking nil by copy-marker reasonable?

Wanted to check for a valid buffer position, which doesn't seem possible 
that way. While without copy-marker, the variable a would be set to nil, 
now the result evaluates to  #<marker in no buffer>, which is a kind of t.


Cheers,

Andreas