unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Christopher Dimech <dimech@gmx.com>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: RE: RE: Symbol Properties having global context
Date: Sun, 6 Dec 2020 15:01:31 -0800 (PST)	[thread overview]
Message-ID: <59ee1af6-86d1-4689-905a-6a4e553e2bf6@default> (raw)
In-Reply-To: <trinity-093046f0-8dfe-4618-92f9-ecb8942f867c-1607286310524@3c-app-mailcom-bs11>

> I got to "9.2 Defining Symbols".  It only mentions that defvar and
> defconst define a symbol as a global variable.
> 
> Could something be written and your comments were very enlightening.

If you got to 9.2 then you likely passed through 9 and 9.1.
9.1 tells you about symbol properties, and functions `symbol-name',
`symbol-function', and `symbol-plist'.  It also tells you about the
value cell (but it neglects mentioning function `symbol-value').

9.3 tells you about obarrays and `symbol-value'.  9.4.1 tells you
about getting and setting symbol properties.  And so on.

`i' in Info is your friend.  It has all of these completions for
`symbol' in the Elisp manual:

symbol
symbol components
symbol equality
symbol evaluation 
symbol forms
symbol function indirection
symbol in keymap
symbol name hashing 
symbol property
symbol that evaluates to itself
symbol with constant value 
symbol, where defined
symbol-file
symbol-function
symbol-name 
symbol-plist
symbol-value
symbolic links
symbolic links <1> 
symbolp
symbols-consed

And if you have substring completion there are more than
twice that number of completions of `symbol'.

Another friend: `M-x apropos'.  With input `symbol' it
shows you a ton of relevant user options, other variables,
commands, non-interactive functions, and macros about
symbols.  Enter additional keywords for more focus.



  reply	other threads:[~2020-12-06 23:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-06 20:09 Symbol Properties having global context Christopher Dimech
2020-12-06 20:13 ` Drew Adams
2020-12-06 20:25   ` Christopher Dimech
2020-12-06 23:01     ` Drew Adams [this message]
2020-12-06 23:20       ` Christopher Dimech
2020-12-06 23:52     ` Michael Heerdegen

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=59ee1af6-86d1-4689-905a-6a4e553e2bf6@default \
    --to=drew.adams@oracle.com \
    --cc=dimech@gmx.com \
    --cc=help-gnu-emacs@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.
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).