unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 7702@debbugs.gnu.org
Subject: bug#7702: 24.0.50; doc of select-active-regions, cut/paste/kill/yank
Date: Sat, 25 Dec 2010 21:26:43 +0200	[thread overview]
Message-ID: <83d3opd570.fsf@gnu.org> (raw)
In-Reply-To: <46EF3254CF934EAC88E740273D51EAB1@us.oracle.com>

> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <7702@debbugs.gnu.org>
> Date: Sat, 25 Dec 2010 10:50:24 -0800
> 
> > This variable has the same meaning and effect on Windows as on X, and
> > its default value is the same.  So I see nothing that should be said
> > about that.  The only difference -- that on Windows the primary
> > selection exists only within a single Emacs session -- is now in the
> > manual.
> 
> What is missing, I think, is some description of what is meant by "primary
> emulation".  I think we need to say explicitly that wherever the manual speaks
> of the "primary selection" understand that Emacs on Windows uses an internal
> cache (variable, call it what you like) that acts the same as the primary
> selection in X Window, with the one exception about sessions.

I modified the text slightly to mention the internal store.

> IOW, aside from such a (single) clarification/footnote, the doc could just speak
> about primary selection and not mention Windows as being exceptional - not
> mention emulation etc.  IOW2, put the proviso/explanation in a single place, and
> otherwise just refer to this as the primary selection, making no distinction for
> Windows.

That's exactly what I did.  I added a single paragraph about the
Windows specifics; the rest of the text talks about the primary
selection without mentioning X or Windows.

> But if you sprinkle mentions of primary emulation here and there
> users will wonder here and there how much is being emulated, whether
> this or that piece of doc also applies to Windows, etc.

There's no such sprinkling.

> But we can agree to disagree about this.

But we agree.

> 1. Speak here and there about "primary selection emulation", without describing
> the behavior, i.e., without saying how well it's emulated, how the emulated
> behavior differs etc.
> 
> 2. Speak everywhere only about the "primary selection" (or, better, the Emacs
> primary selection).  And in only one place in the manual (only), mention that
> although, technically, Windows has no primary selection, Emacs on Windows does
> effectively have a primary selection:
> 
> Emacs emulates the X Window primary selection internally.  The Emacs primary
> selection behaves everywhere exactly the same as an X Window primary selection.
> One exception: the sessions thing.
> 
> You've chosen #1; I suggested #2.  With choice #1, users can everywhere (e.g.
> each doc string) wonder just what is involved, how it behaves on Windows.

No, I've chosen #2.  If you understood differently, it's a
misunderstanding.





  reply	other threads:[~2010-12-25 19:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22  4:02 bug#7702: 24.0.50; doc of select-active-regions, cut/paste/kill/yank Drew Adams
2010-12-25 11:44 ` Eli Zaretskii
     [not found]   ` <666BE4469D9F466C87AE36367C3947A0@us.oracle.com>
2010-12-25 18:10     ` Eli Zaretskii
2010-12-25 18:50       ` Drew Adams
2010-12-25 19:26         ` Eli Zaretskii [this message]
2010-12-26  0:34           ` Drew Adams

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=83d3opd570.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=7702@debbugs.gnu.org \
    --cc=drew.adams@oracle.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).