From: npostavs@users.sourceforge.net
To: "Kelly Dean" <kelly@prtime.org>
Cc: 19471@debbugs.gnu.org
Subject: bug#19471: Emacs can't copy text
Date: Sun, 03 Jul 2016 23:31:09 -0400 [thread overview]
Message-ID: <87a8hydqpu.fsf@users.sourceforge.net> (raw)
In-Reply-To: <VckpTvtqmEIv1BN6wuuZBdhRWidSb9kHIiUd1g02dHi@local> (Kelly Dean's message of "Tue, 30 Dec 2014 09:53:52 +0000")
retitle 19471 Can't copy display-string text
severity 19471 wishlist
found 19471 25.0.95
quit
"Kelly Dean" <kelly@prtime.org> writes:
> Do:
> C-h i g (elisp)translation keymaps RET
> C-HOME C-SPACE DOWN M-w
> C-x b foo RET C-y
>
> What it looks like you copied is ⌜(elisp)Top > Keymaps > Translation Keymaps⌝. But when you paste it, you instead get
> ⌜File: elisp.info, Node: Translation Keymaps, Next: Key Binding Commands, Prev: Remapping Commands, Up: Keymaps⌝
>
> I suppose that's rational in some twisted sense, but it's unreasonable user-unfriendliness for a text editor.
> See my message ⌜Re: Correspondence between web-pages and Info-pages⌝ in emacs-devel for why this matters.
>
> I tried switching the buffer to fundamental mode in order to copy the
> text, but that didn't solve the problem, so Emacs apparently has some
> kind of low-level text-mangling voodoo that hijacks kill-ring-save.
It's implemented by an overlay with a display property. Normal Emacs
text copying commands work on the underlying text, rather than the
displayed one. You can see the what overlays/properties are in effect
by doing C-u C-x = on the string in question.
Perhaps we could add some feature to be able to copy the displayed
string instead of the underlying text.
next prev parent reply other threads:[~2016-07-04 3:31 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 [this message]
2016-07-04 9:03 ` Stephen Berman
2016-07-04 9:21 ` Stephen Berman
2016-07-04 15:00 ` Eli Zaretskii
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
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=87a8hydqpu.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=19471@debbugs.gnu.org \
--cc=kelly@prtime.org \
/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).