From: Drew Adams <drew.adams@oracle.com>
To: Heime <heimeborgia@protonmail.com>,
Dr Rainer Woitok <rainer.woitok@gmail.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: Setting value 1 when matching two strings
Date: Sun, 16 Oct 2022 21:23:48 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488AB9F15441853B9CEA2B6F3269@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <D5VorrkcdCKSTRg-DNFmc0-jI4zPvCpU5PtWqI3NSftRhBs91DvGIgAqLfqSrJ7tWCIV8r3KmhKjptLrIZqWs6DHphroD7JN6HffjBJWOHg=@protonmail.com>
If two objects are `eq' then they are also `equal'.
(`equal' tests with `eq' as the first test it tries.
If that succeeds it returns `t', else it tries other
tests.)
All of this is so clearly explained in the Elisp
manual. There's really no reason not to consult it.
Even laziness isn't a reason. Just `i eq RET' takes
you directly to node `Equality Predicates', which
tells you all you need to know, and likely in better
ways than you'll find here.
Which is quicker and easier, `i eq RET' or sending
a mail to help-gnu-emacs@gnu.org and hoping for a
reply that makes sense to you?
Do yourself a favor: Ask Emacs.
next prev parent reply other threads:[~2022-10-16 21:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 15:51 Setting value 1 when matching two strings Heime via Users list for the GNU Emacs text editor
2022-10-16 16:23 ` Dr Rainer Woitok
2022-10-16 16:33 ` Heime
2022-10-16 20:21 ` Heime
2022-10-16 21:23 ` Drew Adams [this message]
2022-10-16 22:33 ` [External] : " Heime
2022-10-16 23:16 ` Michael Heerdegen
2022-10-16 23:21 ` Heime
2022-10-16 23:39 ` Michael Heerdegen
2022-10-17 0:17 ` Heime
2022-10-17 0:41 ` Drew Adams
2022-10-17 0:57 ` Michael Heerdegen
2022-10-17 1:06 ` Drew Adams
2022-10-17 0:42 ` Michael Heerdegen
2022-10-17 1:40 ` Christopher Dimech
2022-10-17 1:46 ` Michael Heerdegen
2022-10-17 2:17 ` Heime
2022-10-17 0:42 ` Drew Adams
2022-10-17 4:31 ` Jean Louis
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=SJ0PR10MB5488AB9F15441853B9CEA2B6F3269@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=rainer.woitok@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.