all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 58513@debbugs.gnu.org
Subject: bug#58513: describe-function should say that defconst variables are constant
Date: Fri, 14 Oct 2022 14:23:51 +0200	[thread overview]
Message-ID: <87zgdy8ug8.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmk7caBptdR45D0r1pjj-Htcs0Du_jfXOkrN1-EK5Tn0ew@mail.gmail.com> (Stefan Kangas's message of "Fri, 14 Oct 2022 14:04:09 +0200")

Stefan Kangas <stefankangas@gmail.com> writes:

> Evaluate this:
>
>    (prog1 (defconst foo "bar" "help") (describe-variable 'foo))
>
> How about adding a note to the help page of variables declared with
> defconst saying that they are constants, or something to that effect?

I don't think we know that it's supposed to be constant?  Or do we,
somehow?  I thought it was just syntactic sugar, saying what our
intentions for the variable is.

But it doesn't really...  do anything, so we'd have to start to keep
track of which variables are really "constants".  Which would then be
confusing, because you can change values to these as with any other
variable.





  reply	other threads:[~2022-10-14 12:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 12:04 bug#58513: describe-function should say that defconst variables are constant Stefan Kangas
2022-10-14 12:23 ` Lars Ingebrigtsen [this message]
2022-10-14 12:35   ` Phil Sainty
2022-10-14 12:40     ` Lars Ingebrigtsen
2022-10-14 13:03       ` Stefan Kangas
2022-10-14 13:07         ` Lars Ingebrigtsen
2022-10-14 13:34           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 14:25             ` Lars Ingebrigtsen
2022-10-14 16:44               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-15 10:04                 ` Lars Ingebrigtsen
2022-10-16 20:51                   ` Richard Stallman
2022-10-16 21:11                     ` Drew Adams
2022-10-17  5:41                     ` Stefan Kangas
2022-10-17 10:41                       ` Lars Ingebrigtsen
2022-10-15 12:33             ` Stefan Kangas
2022-10-15 14:11               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zgdy8ug8.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=58513@debbugs.gnu.org \
    --cc=stefankangas@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.