From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: bug#46621: Copy line Date: Wed, 22 Jun 2022 21:24:51 +0300 Organization: LINKOV.NET Message-ID: <86iloseeto.fsf@mail.linkov.net> References: <87tuq99ova.fsf@mail.linkov.net> <07496A25-CD5D-46E6-8F1C-7BD29143F3C8@acm.org> <87o7yoyj38.fsf@gnus.org> <449B2624-107D-4083-AE74-989F39C93936@acm.org> <871qvkvft6.fsf@gnus.org> <181B4CC3-B934-45AE-A7E8-9AF2B70C302E@acm.org> <87bkum1eyc.fsf@gnus.org> <861qvikk4l.fsf@mail.linkov.net> <87zgi5uyr1.fsf@gnus.org> <86o7yl9oc4.fsf@mail.linkov.net> <878rppuo9j.fsf@gnus.org> <87wnd8r4v2.fsf@codeisgreat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10398"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (x86_64-pc-linux-gnu) Cc: 46621@debbugs.gnu.org To: Pankaj Jangid Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jun 22 20:38:15 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o45F1-0002X2-Cy for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 22 Jun 2022 20:38:15 +0200 Original-Received: from localhost ([::1]:50562 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o45Ez-0006PX-EV for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 22 Jun 2022 14:38:13 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55592) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o45Eo-0006PH-1L for bug-gnu-emacs@gnu.org; Wed, 22 Jun 2022 14:38:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:42668) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o45En-00023Z-Ov for bug-gnu-emacs@gnu.org; Wed, 22 Jun 2022 14:38:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1o45En-00079n-Kn for bug-gnu-emacs@gnu.org; Wed, 22 Jun 2022 14:38:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 22 Jun 2022 18:38:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 46621 X-GNU-PR-Package: emacs Original-Received: via spool by 46621-submit@debbugs.gnu.org id=B46621.165592303827458 (code B ref 46621); Wed, 22 Jun 2022 18:38:01 +0000 Original-Received: (at 46621) by debbugs.gnu.org; 22 Jun 2022 18:37:18 +0000 Original-Received: from localhost ([127.0.0.1]:36565 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o45E6-00078j-Bd for submit@debbugs.gnu.org; Wed, 22 Jun 2022 14:37:18 -0400 Original-Received: from relay3-d.mail.gandi.net ([217.70.183.195]:44387) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o45E0-00078H-AP for 46621@debbugs.gnu.org; Wed, 22 Jun 2022 14:37:16 -0400 Original-Received: (Authenticated sender: juri@linkov.net) by mail.gandi.net (Postfix) with ESMTPSA id 0B64B60002; Wed, 22 Jun 2022 18:37:03 +0000 (UTC) In-Reply-To: <87wnd8r4v2.fsf@codeisgreat.org> (Pankaj Jangid's message of "Wed, 22 Jun 2022 22:51:37 +0530") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:235045 Archived-At: >>> 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 > #include > ... > > 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. It seems in both cases you expect point to be at the duplicated line, either at the beginning or the end of the duplicated line. But the problem is that currently point stays at the original line.