Re: mark not set after a yank

[David Kastrup]

Warren L Dodge <address@hidden> writes:

>>  Content-Type: text/plain; charset=ISO-8859-15
>>  From: Richard Stallman <address@hidden>
>>  CC: address@hidden
>>  Reply-to: address@hidden
>>  Date: Sun, 01 Apr 2007 10:00:10 -0400
>>  
>>      Very often when I do a move of the point using M-< followed by
>>      a C-w emacs complains about the mark not being set. emacs-21.3
>>      and prior always seems to work as it should. My work around is
>>      to do c-x c-x and then c-w
>>  
>>      This seems to indicate the c-x c-x knows about the mark but not c-w
>>  
>>  That is what would happen in Transient Mark mode, I think.
>>  Is it possible you enabled that mode?
>>  
>
> I do not do Transient Mark mode myself. 
>
> This one is hard to repeat. Everytime I see it happen I try to
> repeat it and it won't. The most common is the M-< as originally
> stated but I also see it other times. I believe this second way is
> when I position the cursor at the start of some text and then do a
> c-s sequence to move to some text farther down. I'll then hit <cr>
> to terminate the search and then c-w to cut the text block from the
> start of the search to the end of the search string. Sometimes I
> would also type c-a to not cut the line I searched to.
>
> Most of the time the c-x works fine but every so often it says mark
> is not set in the buffer. Then the c-x-c-x c-w sequence works.

I often have an active mark when doing a followup in gnus.  In some
extreme cases, mark-active is set while (marker-buffer (mark-marker))
returns nil, leading to errors.

I have not yet found a reliable recipe for repeating it, but it is not
rare.

-- 
David Kastrup