From: MON KEY <monkey@sandpframing.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 6787@debbugs.gnu.org, 6785@debbugs.gnu.org
Subject: bug#6787: bug#6785: Documentation: `kill-region' needs to be re-filled in at least two places
Date: Wed, 4 Aug 2010 15:16:24 -0400 [thread overview]
Message-ID: <AANLkTimPBHAckT78SKNX+HEw1hZV6n617-4e=VDrc92A@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik5bxUQCV5Ms9+qCDGWuHEtRRDH9O7BQv5D9M7N@mail.gmail.com>
On Tue, Aug 3, 2010 at 6:07 PM, Juanma Barranquero <lekktu@gmail.com> wrote:
> On Tue, Aug 3, 2010 at 23:17, MON KEY <monkey@sandpframing.com> wrote:
>
>> In general, that doc prob. needs some attention w/re formatting,
>> and adding some more "\n" would go a long way.
>
> Don't hesitate to send a patch :-)
OK. Following is my attempt at tweaking that doc.
Note, I took the liberty of also adjusting for the problem I described in
bug#6787 http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6787
"Kill (\"cut\") buffer text in region between point and mark.
This removes the text from the buffer saving it on the kill ring.
Use the command \\[yank] to retrieve the killed text on the kill ring.
\(To save the region without killing it, use \\[kill-ring-save].)
Commands which call this function are \"kill commands\".
When the most recent previous command was a kill command, the text to be
killed by the current kill command can be appended to the most recently
killed text on the kill ring such that the killed text of each of the two
kill commnads are combined into one entry at the beginning of the kill ring.
To append the killed region to the last killed text, use \\[append-next-kill]
before \\[kill-region].
When invoked in a read-only buffer Emacs will ding and does not remove the
text from the buffer, however the text of the region is placed on kill ring.
This means a region killing command will \"copy\" text in read-only buffers
even when it does not appear to be killed (\"cut\") in the buffer.
This function is intended as the primary interface for lisp programs which
kill text (as opposed to deleting text as if by `delete-region').
When called from a program the arguments BEG and END are buffer positions
indicating the stretch of text to be killed.
When the optional third arg YANK-HANDLER is non-nil, the killed text has the
yank-handler property set non-nil. Setting this property non-nil affects
wether yank commands will apply `yank-excluded-properties' as described in
the doc string for `insert-for-yank-1', which see."
> Juanma
>
--
/s_P\
prev parent reply other threads:[~2010-08-04 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 18:29 bug#6785: Documentation: `kill-region' needs to be re-filled in at least two places MON KEY
2010-08-03 21:01 ` Juanma Barranquero
[not found] ` <AANLkTimfCDGzXGLKYAfmMvGu0mfniv65JRKE99LR6Q3_@mail.gmail.com>
[not found] ` <AANLkTik5bxUQCV5Ms9+qCDGWuHEtRRDH9O7BQv5D9M7N@mail.gmail.com>
2010-08-04 19:16 ` MON KEY [this message]
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='AANLkTimPBHAckT78SKNX+HEw1hZV6n617-4e=VDrc92A@mail.gmail.com' \
--to=monkey@sandpframing.com \
--cc=6785@debbugs.gnu.org \
--cc=6787@debbugs.gnu.org \
--cc=lekktu@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 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).