unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: 42708@debbugs.gnu.org
Cc: rms@gnu.org
Subject: bug#42708: Let users copy "*Char Help*" buffer
Date: Tue, 04 Aug 2020 21:41:17 +0800	[thread overview]
Message-ID: <87r1smy1du.5.fsf@jidanni.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 354 bytes --]

There is a buffer "*Char Help*" that emacs makes sure the user is never
able to copy. (What if Stallman found out about this?)

First, if the user tries C-x o, to maneuver from the minibuffer into the
*Char Help* buffer, emacs already knows the user will try this trick,
and thwarts it right away, despite C-x not being explicitly listed in
the prompt,


[-- Attachment #2: *Char Help* prompt --]
[-- Type: image/jpeg, Size: 18757 bytes --]

[-- Attachment #3: Type: text/plain, Size: 851 bytes --]


Second, one might think "Oh, the *Char Help* buffer might be left around
later and then we can copy it." Nope, the emacs police have that one
covered too. It is destroyed right away after use, faster than Jim
Phelps' burning classified audio tape in Mission Impossible.

There is only one place that those "you are not allowed to copy" police
cannot control: when viewed with emacs -nw. (Oops, I leaked it.) Else
one's only option is a screenshot.

So where does one encounter this disappearing "*Char Help*" buffer?
Well when using
  C runs the command dired-do-copy (found in dired-mode-map), which is
  an interactive autoloaded compiled Lisp function in ‘dired-aux.el’.

emacs-version "26.3"

And why would one want to copy the contents of the boring "*Char Help*"
buffer? Well, that's the subject of my next bug report...

             reply	other threads:[~2020-08-04 13:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04 13:41 積丹尼 Dan Jacobson [this message]
2020-08-04 23:42 ` bug#42708: Let users copy "*Char Help*" buffer Juri Linkov
2020-08-05  9:24   ` Lars Ingebrigtsen
2020-08-05 23:52     ` Juri Linkov
2020-08-06  7:12       ` Lars Ingebrigtsen
2020-10-13  2:59         ` Lars Ingebrigtsen
2020-10-13 15:27           ` Drew Adams
2020-11-03 18:57           ` Juri Linkov
2020-11-09 13:39             ` Lars Ingebrigtsen
2020-11-10 19:51               ` Juri Linkov
2020-11-10 20:26                 ` Drew Adams
2020-11-11  5:40                   ` Richard Stallman
2020-11-11  8:09                   ` Juri Linkov
2020-11-11 19:41                     ` Drew Adams
2020-11-11 20:07                       ` Juri Linkov
2020-11-11 21:24                         ` Drew Adams
2020-11-12  7:32                           ` Juri Linkov
2020-11-12 18:09                             ` Drew Adams
2020-11-11 10:28                 ` Lars Ingebrigtsen
2020-11-11 19:19                   ` Juri Linkov

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=87r1smy1du.5.fsf@jidanni.org \
    --to=jidanni@jidanni.org \
    --cc=42708@debbugs.gnu.org \
    --cc=rms@gnu.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).