From: nljlistbox2@gmail.com (N. Jackson)
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: 32047@debbugs.gnu.org
Subject: bug#32047: 26.1; Misleading/confusing text about `C-k' in TUTORIAL
Date: Wed, 11 Jul 2018 16:45:29 -0400 [thread overview]
Message-ID: <87efg94i3a.fsf@moondust.localdomain> (raw)
In-Reply-To: <m2r2k9oa9p.fsf@fgunbin.playteam.ru> (Filipp Gunbin's message of "Wed, 11 Jul 2018 22:14:10 +0300")
At 22:14 +0300 on Wednesday 2018-07-11, Filipp Gunbin wrote:
>
>>> 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.
> I think the doc is clear
This is not the documentation of C-k, it is the Emacs Tutorial.
> and cannot see what's so special about the beginning of line..
Perhaps you did not read the OP [1]. There's nothing special
about the beginning of the line when using C-k to kill the rest
of the line, but when C-k is used to "kill the contents of the
line" -- as it is in the example -- then point must be at the
beginning of the line.
The writer of the Tutorial makes an assumption that point is at
the beginning of the line without telling the reader of that
assumption.
[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32047#5
next prev parent reply other threads:[~2018-07-11 20:45 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
2018-07-11 19:14 ` Filipp Gunbin
2018-07-11 20:45 ` N. Jackson [this message]
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=87efg94i3a.fsf@moondust.localdomain \
--to=nljlistbox2@gmail.com \
--cc=32047@debbugs.gnu.org \
--cc=fgunbin@fastmail.fm \
/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.