Subject: Re: bug#7503: copy-and-insert-previous-line

From: martin rudalics <[email-masked]>
Date: Sun, 28 Nov 2010 17:11:00 +0100

> Because it's a useful level of abstraction?

Should be.  Unfortunately dwarfed by the field motion constraints :-(

It takes me more time to understand something like

   This function constrains the returned position to the current field
   unless that would be on a different line than the original,
   unconstrained result.  If N is nil or 1, and a rear-sticky field ends
   at point, the scan stops as soon as it starts.

than to code `forward-line' within a `save-excursion'.  YMMV.

martin