unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: "Jan D." <jan.h.d@swipnet.se>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: select-active-regions, Emacs not X
Date: Mon, 30 Aug 2010 13:35:28 -0400	[thread overview]
Message-ID: <87fwxwxau7.fsf@stupidchicken.com> (raw)
In-Reply-To: <4C7BE2FA.6080003@easy-emacs.de> ("Andreas Röhler"'s message of "Mon, 30 Aug 2010 18:57:30 +0200")

Andreas Röhler <andreas.roehler@easy-emacs.de> writes:

> Doesn't meet my observations.
>
> In the original case cursor motion followed an exchange-point-and-mark
> over a string found.  Afterwards, moving the cursor, any active region
> went into the clipboard. Next yank got it from there.  Whilst the
> string found and copied has been expected, but was not returned.
>
> Ie got some arbitrary content resp. to the move away from the match-point.

This description is too vague.  Could you please provide a precise,
step-by-step recipe, starting from `emacs -Q'?

> The big difference IMHO is the cursor-motion-region-setting in emacs.
> In X, regions are expressingly marked, while in Emacs it just the
> difference beween point and any previously set mark.

select-active-regions only takes effect when Transient Mark mode is
enabled, which means the region is explicitly marked.  Again, if this is
not what you see, please provide a step-by-step recipe, starting from
`emacs -Q', to demonstrate the problem.



  reply	other threads:[~2010-08-30 17:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30 12:14 select-active-regions, Emacs not X Andreas Röhler
2010-08-30 14:18 ` Chong Yidong
2010-08-30 16:57   ` Andreas Röhler
2010-08-30 17:35     ` Chong Yidong [this message]
2010-08-30 18:44       ` Andreas Röhler
2010-08-30 19:27         ` Jan Djärv
2010-08-31  5:54           ` Andreas Röhler
2010-08-31  9:38             ` Jan Djärv
2010-08-31 10:18               ` Andreas Röhler
2010-08-31  8:08         ` Miles Bader
2010-08-31 10:13           ` Andreas Röhler
2010-08-31 21:45         ` David De La Harpe Golden
2010-09-02 10:33           ` Andreas Röhler
2010-09-02 15:15             ` Chong Yidong
2010-09-02 16:24               ` Stefan Monnier
2010-09-02 16:45               ` Andreas Röhler
2010-09-02 21:56                 ` David De La Harpe Golden
2010-09-03  6:11                   ` Andreas Röhler
2010-09-03  6:47                     ` Miles Bader
2010-09-03  8:45                       ` Andreas Röhler
2010-09-03  9:00                         ` Miles Bader
2010-09-03  9:29                           ` Andreas Röhler
2010-09-03  9:55                             ` Miles Bader
2010-09-03 10:30                               ` Andreas Röhler

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=87fwxwxau7.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=andreas.roehler@easy-emacs.de \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    /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).