unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 23130@debbugs.gnu.org
Subject: bug#23130: 25.1.50; `C-h f' etc.: escaping in symbol names
Date: Mon, 28 Mar 2016 07:48:38 -0700 (PDT)	[thread overview]
Message-ID: <e4a50973-9e8b-4475-aaf9-763c649a5228@default> (raw)
In-Reply-To: <87h9fqhe5l.fsf@linux-m68k.org>

> >> > The name of the symbol is "foo.", not "foo\.".
> >>
> >> Both refer to the same symbol, as does "\foo.".
> >
> > Not as `symbol-name' values, they don't.
> 
> It's showing a symbol, not the result of calling symbol-name on it.

Yes, we know.

> > The point is to show the symbol _name_, and to do so in a
> > way that is clear to anyone.
> 
> The point is to show a symbol, unambigously.

The point of this bug report is that the symbol's name should be
shown clearly.  The symbol is already printed using prin1 in the
signature: (foo\.)

Show it as Lisp when showing Lisp.  Show it as a symbol name, as
is the Emacs convention, in help text.  And in that case, show it
enclosed in `...'.

> >> > Or better yet, to remove all ambiguity, even for characters
> >> > such as SPC in the function name, enclose the name in `...':
> >>
> >> The name as printed is already unambigous.
> >
> > "bar\ is a Lisp function." is not only unclear; it is incorrect.
> 
> Of course it's incorrect, but describe-function will never generate
> that.

Why don't you read the bug report and try the recipe for yourself,
starting with `emacs -Q'?  That's exactly what `describe-funcction'
"generates":

(defun bar\  () (message "BARRRR"))

`C-h f RET' with point on "bar\ ":

  bar\ is a Lisp function.

  (bar\ )

  Not documented.





  reply	other threads:[~2016-03-28 14:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-27 23:25 bug#23130: 25.1.50; `C-h f' etc.: escaping in symbol names Drew Adams
2016-03-28  6:57 ` Andreas Schwab
2016-03-28 13:21   ` Drew Adams
2016-03-28 14:26     ` Andreas Schwab
2016-03-28 14:48       ` Drew Adams [this message]
2016-03-28 15:19         ` Andreas Schwab
2016-03-28 15:23           ` Drew Adams
2016-03-28 16:11             ` Andreas Schwab
2016-03-28 17:08               ` Drew Adams
2016-03-28 17:18                 ` Andreas Schwab
2022-02-08  7:04 ` Lars Ingebrigtsen
2022-02-08  9:13   ` Andreas Schwab
2022-02-08  9:29     ` Lars Ingebrigtsen
2022-02-08  9:41       ` Andreas Schwab
2022-03-09 16:30         ` Lars Ingebrigtsen
2022-03-09 17:09           ` Andreas Schwab
2022-03-09 17:11             ` Lars Ingebrigtsen
2022-03-09 17:39               ` Andreas Schwab
2022-03-09 17:42                 ` Lars Ingebrigtsen
2022-03-14  9:23 ` Lars Ingebrigtsen
2022-03-14 14:50   ` bug#23130: [External] : " Drew Adams

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=e4a50973-9e8b-4475-aaf9-763c649a5228@default \
    --to=drew.adams@oracle.com \
    --cc=23130@debbugs.gnu.org \
    --cc=schwab@linux-m68k.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).