bug#46621: Copy line

[Pankaj Jangid]

Lars Ingebrigtsen <larsi@gnus.org> writes:

>> BTW, what do you think about the already suggested leaving point
>> at the end of duplicated lines?  This means removing save-excursion
>> and adding backward-char to the end of `duplicate-line' to move point
>> before the last newline.
>
> It was also suggested to leave point at the start of the duplicated
> lines.  I think that makes more sense -- the use case here is to copy
> lines so that you can start altering them, after all.

Behaviour could be different, depending upon what programming construct
your are in. For example, in C,

#include <a.h>
#include <b.h>
...

if I have to include a new library I’ll go to line-no 2 call
duplicate-line and then I want the point at the end. But in the
following lines, I want the opposite behaviour if I want to declare a
variables of other types.

int a1, b1, c1
float a2, b2, c2
// now I want variables of type char

In this case I want the cursor at beginning.

But I feel that former is more useful i.e. point at the end. Think of
different types of statements in a programming language.