unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: schwab@suse.de, jidanni@jidanni.org, mbork@mbork.pl,
	25131@debbugs.gnu.org
Subject: bug#25131: thwarted from copying what one sees in Info
Date: Wed, 7 Dec 2016 15:21:13 -0800 (PST)	[thread overview]
Message-ID: <bede32b1-7e1b-4e46-ab7d-bcba96f24c0f@default> (raw)
In-Reply-To: <<83k2bbil94.fsf@gnu.org>>

> > On the other hand, I disagree that we should add a special command
> > just for copying Info breadcrumbs.  A _general_ solution to the need
> > to copy displayed stuff (including overlays) should instead be sought.
> 
> What would be the UI, assuming we don't want the user to have to find
> out on her own that there's an overlay or a display property at some
> point?

I don't know.  We can think about that possibility.

But for this bug, I think just extending the existing command that
gives you the node name, by letting a prefix arg give it to you as
a full path (breadcrumbs - in whatever textual form), would be good.

Wrt knowing whether an overlay etc. present (e.g., whether some
displayed text is copiable from the buffer or is a display artifact):
That's a general UI problem.  Perhaps when a user tries to perform
some actions (e.g. copy text) a message should tell her that the
text is just for display etc.





       reply	other threads:[~2016-12-07 23:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<87r35kmc1v.fsf@jidanni.org>
     [not found] ` <<87r35jr97l.fsf@jidanni.org>
     [not found]   ` <<3529e973-7e42-49b9-9bf0-85cba12a91af@default>
     [not found]     ` <<83k2bbil94.fsf@gnu.org>
2016-12-07 23:21       ` Drew Adams [this message]
2016-12-07  7:30 bug#25131: thwarted from copying what one sees in Info 積丹尼 Dan Jacobson
2016-12-07 11:29 ` Marcin Borkowski
2016-12-07 16:17   ` Eli Zaretskii
2016-12-07 16:25     ` Andreas Schwab
2016-12-07 16:59       ` Eli Zaretskii
     [not found]     ` <<mvmwpfbhfjw.fsf@hawking.suse.de>
     [not found]       ` <<83lgvrisjv.fsf@gnu.org>
2016-12-07 17:46         ` Drew Adams
2016-12-07 11:35 ` 積丹尼 Dan Jacobson
2016-12-07 16:32 ` 積丹尼 Dan Jacobson
2016-12-07 17:02   ` Drew Adams
2016-12-07 19:37     ` Eli Zaretskii
2016-12-07 17:11 ` 積丹尼 Dan Jacobson

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=bede32b1-7e1b-4e46-ab7d-bcba96f24c0f@default \
    --to=drew.adams@oracle.com \
    --cc=25131@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=mbork@mbork.pl \
    --cc=schwab@suse.de \
    /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).