all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrew Kurn <kurn@sfu.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: kurn@sfu.ca, 9936@debbugs.gnu.org
Subject: bug#9936: kill-line problem
Date: Wed, 2 Nov 2011 15:12:50 -0700	[thread overview]
Message-ID: <20111102221250.GA20214@sfu.ca> (raw)
In-Reply-To: <20145.41970.282049.500375@fencepost.gnu.org>

On Wed  2 Nov 2011 16:11 -0400, Glenn Morris wrote:
> 
> 
> (Please keep 9936@debbugs cc'd)
> 
> Andrew Kurn wrote (on Wed, 2 Nov 2011 at 09:50 -0700):
> 
> > > It sounds like the intended behaviour. With kill-whole-line non-nil,
> > > kill-line kills up to wherever forward-visible-line ends up. Ie,
> > > invisible newlines are ignored.
> > 
> > No, sorry, but there are several visible newlines in the way.  It eats
> > them all up.
> 
> Can you give a recipe showing how to reproduce the problem, starting
> from emacs -q --no-site-file?


This seems to work:

emacs -nw -q --no-site-file

(setq ss (concat (make-string 10 ?X) "," ))


(put-text-property 0 10 'invisible t ss)


(insert ss ss ss "\n" ss ss ss "\n" ss ss ss "\n" ss ss ss "\n" )


(setq kill-whole-line t)

---

Then use ^K to kill the first line.  They all disappear.


(let ((kill-whole-line t))
  (kill-line))


This seems to have the value "kill-region" . . . if that makes any
sense.

Andrew





  reply	other threads:[~2011-11-02 22:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01 20:46 bug#9936: kill-line problem Andrew Kurn
2011-11-02  1:19 ` Glenn Morris
2011-11-02 16:50   ` Andrew Kurn
2011-11-02 20:11     ` Glenn Morris
2011-11-02 22:12       ` Andrew Kurn [this message]
2011-11-04  0:05         ` Johan Bockgård
2011-11-04  0:55           ` Glenn Morris

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111102221250.GA20214@sfu.ca \
    --to=kurn@sfu.ca \
    --cc=9936@debbugs.gnu.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.