From: Eli Zaretskii <eliz@gnu.org>
To: charles@aurox.ch
Cc: 32956@debbugs.gnu.org
Subject: bug#32956: 26.1.50; t-m-m mark deactivation documentation
Date: Mon, 08 Oct 2018 05:28:33 +0300 [thread overview]
Message-ID: <83woqtyxwu.fsf@gnu.org> (raw)
In-Reply-To: <m28t391r3k.fsf@aurox.ch> (charles@aurox.ch)
> Date: Sun, 07 Oct 2018 21:42:07 +0200
> From: charles@aurox.ch (Charles A. Roelli)
> Cc: 32956@debbugs.gnu.org
>
> FWIW, this change for emacs-26 should fix it, as well as adding an
> entry for activating the mark.
>
> diff --git a/doc/emacs/mark.texi b/doc/emacs/mark.texi
> index 0ffa9f7..1050587 100644
> --- a/doc/emacs/mark.texi
> +++ b/doc/emacs/mark.texi
> @@ -17,11 +17,13 @@ Mark
> changes.
>
> @cindex active region
> +@cindex activating the mark
> Setting the mark at a position in the text also @dfn{activates} it.
> When the mark is active, we say also that the region is active; Emacs
> indicates its extent by highlighting the text within it, using the
> @code{region} face (@pxref{Face Customization}).
>
> +@cindex deactivating the mark
> After certain non-motion commands, including any command that
> changes the text in the buffer, Emacs automatically @dfn{deactivates}
> the mark; this turns off the highlighting. You can also explicitly
Fine with me, thanks.
next prev parent reply other threads:[~2018-10-08 2:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<<m2in2f17jo.fsf@aurox.ch>
[not found] ` <<5399d374-2089-492a-b830-9eb2baac82a6@default>
[not found] ` <<m2efd2272p.fsf@aurox.ch>
2018-10-07 1:02 ` bug#32956: 26.1.50; t-m-m mark deactivation documentation Drew Adams
2018-10-07 14:39 ` Charles A. Roelli
2018-10-07 19:42 ` Charles A. Roelli
2018-10-08 2:28 ` Eli Zaretskii [this message]
2018-10-08 17:23 ` Charles A. Roelli
[not found] <<m2in2f17jo.fsf@aurox.ch>
2018-10-06 14:48 ` Drew Adams
2018-10-06 19:44 ` Charles A. Roelli
2018-10-06 14:19 Charles A. Roelli
2018-10-06 16:39 ` Eli Zaretskii
2018-10-06 19:29 ` Charles A. Roelli
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=83woqtyxwu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32956@debbugs.gnu.org \
--cc=charles@aurox.ch \
/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.