From: Deniz Dogan <deniz.a.m.dogan@gmail.com>
To: Rudi Schlatte <rudi@constantly.at>
Cc: emacs-devel@gnu.org
Subject: Re: Please consider fixing #3437 before release
Date: Sat, 13 Jun 2009 12:21:59 +0200 [thread overview]
Message-ID: <7b501d5c0906130321w1e368305l5032bd88e09e2fad@mail.gmail.com> (raw)
In-Reply-To: <m2ws7g62g0.fsf@constantly.at>
2009/6/13 Rudi Schlatte <rudi@constantly.at>:
> Teemu Likonen <tlikonen@iki.fi> writes:
>
>> I heard that Emacs 23 will be released soon so I'd like to ask Emacs
>> maintainers or release managers to consider fixing bug #3437 before the
>> release:
>>
>> http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=3437
>>
>> The bug report even has a patch attached.
>>
>> The bug is about kill-visual-line command behaving unexpectedly when
>> executed at the end of a logical line. I think everybody would expect it
>> to delete only the newline, like kill-line does, but kill-visual-line
>> deletes not only the newline character but also the next line up to the
>> cursor position. See the bug report for a concrete example.
>
> Aaah, so that's the reason for some of the half-sentences I produced
> recently! Seems I'm so sure about the behavior of C-k that I just
> remove the newline and jump elsewhere, without realizing that too much
> is deleted.
>
> In other words, this has caused me data loss (text loss) and will now
> slow down my typing speed until a fix is in.
I felt exactly the same when I found this thread. I recently finished
my master thesis and way too often did I find only the second half of
sentences in AUCTeX. I thought I accidentally hit some modifier before
C-k causing this behavior... That being said, I think this bug should
have the highest possible priority.
--
Deniz Dogan
next prev parent reply other threads:[~2009-06-13 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 21:56 Please consider fixing #3437 before release Teemu Likonen
2009-06-13 7:02 ` Rudi Schlatte
2009-06-13 10:21 ` Deniz Dogan [this message]
2009-06-13 18:28 ` Chong Yidong
2009-06-13 18:57 ` Chong Yidong
2009-06-13 19:09 ` Deniz Dogan
2009-06-13 19:54 ` Teemu Likonen
2009-06-14 8:21 ` Miles Bader
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7b501d5c0906130321w1e368305l5032bd88e09e2fad@mail.gmail.com \
--to=deniz.a.m.dogan@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rudi@constantly.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).