all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: nljlistbox2@gmail.com (N. Jackson)
Cc: 32047@debbugs.gnu.org
Subject: bug#32047: 26.1; Misleading/confusing text about `C-k' in TUTORIAL
Date: Wed, 11 Jul 2018 19:12:11 +0300	[thread overview]
Message-ID: <83h8l5g3ac.fsf@gnu.org> (raw)
In-Reply-To: <87o9fn2386.fsf@moondust.localdomain> (nljlistbox2@gmail.com)

> From: nljlistbox2@gmail.com (N. Jackson)
> Date: Tue, 03 Jul 2018 21:34:33 -0400
> 
> 414 >> Move the cursor to the beginning of a line which is not empty.
> 415    Then type C-k to kill the text on that line.
> 416 >> Type C-k a second time.  You'll see that it kills the Newline
> 417    which follows that line.
> 418 
> 419 Note that a single C-k kills the contents of the line, and a second
> 420 C-k kills the line itself, and makes all the other lines move up.  C-k
> 421 treats a numeric argument specially: it kills that many lines AND
> 422 their contents.  This is not mere repetition.  C-u 2 C-k kills two
> 423 lines and their Newlines; typing C-k twice would not do that.
> 
> The example(s) given in Lines 414 to 417 are correct. But the
> sentence beginning on Line 419 is misleading. It is only true
> when point is at the beginning of the line.

But in this case, point _is_ at the beginning of the line, isn't it?
So I wonder whether it is worth it to complicate the text just for
accuracy's sake?

What do others think?

Thanks.





  reply	other threads:[~2018-07-11 16:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04  1:34 bug#32047: 26.1; Misleading/confusing text about `C-k' in TUTORIAL N. Jackson
2018-07-11 16:12 ` Eli Zaretskii [this message]
2018-07-11 19:14   ` Filipp Gunbin
2018-07-11 20:45     ` N. Jackson
2018-07-12 16:06       ` Filipp Gunbin
2018-07-11 19:46   ` N. Jackson
2018-07-12 14:14     ` Eli Zaretskii
2018-07-12 20:09 ` N. Jackson
2018-07-13  6:19   ` Eli Zaretskii

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=83h8l5g3ac.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=32047@debbugs.gnu.org \
    --cc=nljlistbox2@gmail.com \
    /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.