all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: kelly@prtime.org, 19471@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#19471: Emacs can't copy text
Date: Mon, 04 Jul 2016 18:00:04 +0300	[thread overview]
Message-ID: <83d1mtphxn.fsf@gnu.org> (raw)
In-Reply-To: <87oa6d7o7q.fsf@gmx.net> (message from Stephen Berman on Mon, 04 Jul 2016 11:21:45 +0200)

> From: Stephen Berman <stephen.berman@gmx.net>
> Date: Mon, 04 Jul 2016 11:21:45 +0200
> Cc: Kelly Dean <kelly@prtime.org>, 19471@debbugs.gnu.org
> 
> On Mon, 04 Jul 2016 11:03:39 +0200 Stephen Berman <stephen.berman@gmx.net> wrote:
> 
> > In fact, with text properties instead of overlays, the displayed string
> > is copied (cf. the variable yank-handled-properties), as can be seen by
> > copying the first line below the section title of the above Info node:
> >
> >    When the ‘read-key-sequence’ function reads a key sequence (*note Key
> >
> > "see " is a display text property, but appears when this text is yanked.
> 
> Well, what showed up here as "*note " did appear as "see " when I yanked
> that text into the Message mode buffer...

And that's the crux of the issue, AFAIU: the OP wanted to be able to
copy/paste the display string so that it would be visible even outside
of Emacs, e.g. when sent in an email message or written to a disk
file.  In that case, text properties and overlay properties/strings
behave the same: you lose them.

The fact that text properties are copied with the text, while overlay
strings and properties aren't is the intended behavior, Emacs does
that since the day overlays were introduced.





  reply	other threads:[~2016-07-04 15:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30  9:53 bug#19471: Emacs can't copy text Kelly Dean
2016-07-04  3:31 ` npostavs
2016-07-04  9:03   ` Stephen Berman
2016-07-04  9:21     ` Stephen Berman
2016-07-04 15:00       ` Eli Zaretskii [this message]
2016-07-04 14:46   ` 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=83d1mtphxn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=19471@debbugs.gnu.org \
    --cc=kelly@prtime.org \
    --cc=npostavs@users.sourceforge.net \
    --cc=stephen.berman@gmx.net \
    /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.