From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kevin Rodgers Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: longlines mode and kill-line: missing space between boundary words Date: Wed, 12 Dec 2007 06:57:54 -0700 Message-ID: References: <47572D2F.9010307@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1197468182 28453 80.91.229.12 (12 Dec 2007 14:03:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 12 Dec 2007 14:03:02 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 12 15:03:13 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1J2SB6-0005Xg-LK for ged-emacs-devel@m.gmane.org; Wed, 12 Dec 2007 15:03:12 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J2SAo-0003cO-Og for ged-emacs-devel@m.gmane.org; Wed, 12 Dec 2007 09:02:54 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J2S9H-0002Lr-Cp for emacs-devel@gnu.org; Wed, 12 Dec 2007 09:01:19 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J2S9E-0002If-BM for emacs-devel@gnu.org; Wed, 12 Dec 2007 09:01:18 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J2S9C-0002IH-W8 for emacs-devel@gnu.org; Wed, 12 Dec 2007 09:01:15 -0500 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1J2S9C-00056r-E5 for emacs-devel@gnu.org; Wed, 12 Dec 2007 09:01:14 -0500 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1J2S7h-0005Df-2y for emacs-devel@gnu.org; Wed, 12 Dec 2007 13:59:41 +0000 Original-Received: from c-67-162-159-170.hsd1.co.comcast.net ([67.162.159.170]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 Dec 2007 13:59:41 +0000 Original-Received: from kevin.d.rodgers by c-67-162-159-170.hsd1.co.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 Dec 2007 13:59:41 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 41 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: c-67-162-159-170.hsd1.co.comcast.net User-Agent: Thunderbird 1.5.0.13 (Macintosh/20070809) In-Reply-To: <47572D2F.9010307@gmx.at> X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:85092 gmane.emacs.pretest.bugs:20440 Archived-At: martin rudalics wrote: > > In longlines mode when I press C-k (i.e. a kill-line command) in a > > long paragraph with soft linebreaks and then press C-y to yank the > > killed line somewhere, the spaces between the words on soft-broken > > lines' boundaries disapear. > > > ... > > > > I guess after kill-line the longline mode automatically compresses the > > soft-linebreak at the end of the line (because the space is > > temporarily turned into a soft linebreak) and the information about > > the space does not get into the kill ring. > > Yes. `kill-line' kills the line without the newline and longlines mode > removes the newline character after that. > > > The consistent behaviour would be either to add the missing space to > > the kill ring or (it that is impossible or too hard) to kill the whole > > paragraph at once (since it in fact is a single line). The first > > behaviour clearly looks better to me. > > I'm afraid that it's hardly possible to DTRT here. Adding the space is > not quite correct since `kill-line' doesn't kill the newline character > which substitutes the space. Note that you get a similar bug when you > kill the line + the newline character. Reinserting the killed stretch > will get you a hard newline instead of the soft one. > > Killing everything up to the next hard newline appears conceptually > right. It would clash, however, with the current concept that a line > for `kill-line' is pretty much a line as it appears on the screen. > Moreover, `kill-line' would have to become aware of longlines' way of > distinguishing soft and hard newlines. Would it make sense for longlines mode to have a local keymap in which C-k was bound to a new command (named longlines-kill-line, of course) that is aware of longlines' way of distinguishing soft and hard newlines? -- Kevin Rodgers Denver, Colorado, USA