unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 45443@debbugs.gnu.org
Subject: bug#45443: 28.0.50; Can't find definition of compilation--message->loc
Date: Sun, 27 Dec 2020 00:38:17 -0500	[thread overview]
Message-ID: <E1ktOkz-0006j7-R2@fencepost.gnu.org> (raw)
In-Reply-To: <83a6u0n8y7.fsf@gnu.org> (message from Eli Zaretskii on Sat, 26 Dec 2020 12:44:00 +0200)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > It's a general problem with uses of cl-defstruct and similar
  > constructs: they generate functions and macros that the Help functions
  > are unable to find.  In this case, see this part of compile.el:

  >   (cl-defstruct (compilation--message

What causes the problem?  There has to be a way to fix it.

Does the fact that the defining form name does not start with `def'
have anything to do with it?  We could call it `def-cl-struct'.

There is also this:

            (:conc-name compilation--message->))

Years have taught me that enabling a definition to be a little shorter
by making names by concatenation is a bad idea.  It makes the code
harder to understand because there are references to these names that
you can't find with simple searching.

Is there a way to rewrite that definition so it does not concatenate
names?

If there is none, can we create one?

-- 
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)







  reply	other threads:[~2020-12-27  5:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-26 10:18 bug#45443: 28.0.50; Can't find definition of compilation--message->loc Richard Stallman
2020-12-26 10:44 ` Eli Zaretskii
2020-12-27  5:38   ` Richard Stallman [this message]
     [not found] <<E1kt6ez-0000D4-0e@fencepost.gnu.org>
     [not found] ` <<83a6u0n8y7.fsf@gnu.org>
2020-12-26 18:58   ` Drew Adams
2020-12-27  0:51     ` Unknown
2020-12-27  8:07       ` Lars Ingebrigtsen
2020-12-27 17:40       ` Eli Zaretskii
2020-12-27 17:59         ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-27 18:05           ` Eli Zaretskii
2020-12-27 19:28           ` Unknown
2020-12-27 19:40             ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-27 19:28           ` Unknown

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=E1ktOkz-0006j7-R2@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=45443@debbugs.gnu.org \
    --cc=eliz@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).