From: andy.ling@quantel.com
To: Glenn Morris <rgm@gnu.org>
Cc: 4538@emacsbugs.donarmstrong.com
Subject: bug#4538: 23.1; kill-line doesn't with show-trailing-whitespace
Date: Thu, 24 Sep 2009 09:48:16 +0100 [thread overview]
Message-ID: <OFD12FD7A7.42788396-ON8025763B.00301587-8025763B.0030F5C6@Quantel.Com> (raw)
In-Reply-To: <x64oqt58d2.fsf@fencepost.gnu.org>
Glenn Morris <rgm@gnu.org> wrote on 24/09/2009 04:28:41:
> andy.ling@quantel.com wrote:
>
> > Run emacs -q
> > open a buffer and enter a line of spaces
> > go to the beginning of line and kill line (C-a C-k)
> > The line is deleted through the newline to the next line
> > Now execute (setq show-trailing-whitespace t)
> > Again enter a line of spaces and go to the beginning of the line.
> > This time the spaces should be hilighted in red.
> > Now kill the line. The line is only killed up to the newline.
>
> It seems this is deliberate:
>
> http://lists.gnu.org/archive/html/emacs-devel/2004-02/msg00190.html
>
> At first glance, it does seem a bit odd. It is also undocumented.
>
I'd say it seems odd at second glance too :-)
I can't believe everybody wants this behaviour. So to that end
can I suggest the traditional emacs approach is adopted and
it is made configurable.
Regards
Andy Ling
--
Quantel is the trade name used by Quantel Holdings Limited and its
subsidiaries. Quantel Holdings Limited is registered in England & Wales.
Registration No: 4004913
Contact details for all Quantel Offices and Companies can be found on our
website www.quantel.com or by writing to the holding company.
Registered address: Turnpike Road, Newbury, Berkshire, RG14 2NX, United
Kingdom
next prev parent reply other threads:[~2009-09-24 8:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 14:13 bug#4538: 23.1; kill-line doesn't with show-trailing-whitespace andy.ling
2009-09-24 3:28 ` Glenn Morris
2009-09-24 8:48 ` andy.ling [this message]
2009-09-25 6:17 ` Glenn Morris
2009-09-25 10:47 ` andy.ling
2011-09-18 8:36 ` Lars Magne Ingebrigtsen
2011-09-22 7:13 ` Glenn Morris
2011-09-23 10:56 ` Lars Magne Ingebrigtsen
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=OFD12FD7A7.42788396-ON8025763B.00301587-8025763B.0030F5C6@Quantel.Com \
--to=andy.ling@quantel.com \
--cc=4538@emacsbugs.donarmstrong.com \
--cc=rgm@gnu.org \
/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).