From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Guidelines for the "symbol" syntax class
Date: Mon, 4 Jan 2016 02:58:56 +0200 [thread overview]
Message-ID: <5689C3D0.1050708@yandex.ru> (raw)
In-Reply-To: <jwvsi2ew4qi.fsf-monnier+emacs@gnu.org>
On 01/04/2016 02:51 AM, Stefan Monnier wrote:
> With things like Foo:Bar (or Foo.bar or what have you), there are indeed
> conflicting definitions of "symbol" and there's usually not a single one
> that works everywhere.
But as a major mode author, I *do* have to pick one. That's the main
choice I'm asking about.
Splitting Foo::Bar into two symbols is a done decision (`::' is a scope
resolution operator anyway). Still undecided whether the symbol-at-point
at instance variable (@var) should include the @ sign, and whether the
symbol-at-point at a Symbol literal (:symbol) should include the colon.
And what to do about syntax-sugared Symbol literals (symbol: value).
> IOW you can't expect Emacs's notion of "symbol"
> to cover all the use cases. More specifically, Emacs's notion of symbol
> can only be used as a stepping stone on which to construct the things
> you need, on a case by case basis.
Naturally, the use cases left suboptimal by the eventual choice would
need to be handled specially.
next prev parent reply other threads:[~2016-01-04 0:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-03 5:09 Guidelines for the "symbol" syntax class Dmitry Gutov
2016-01-03 22:56 ` John Wiegley
2016-01-04 0:46 ` Dmitry Gutov
2016-01-04 0:51 ` Stefan Monnier
2016-01-04 0:58 ` Dmitry Gutov [this message]
2016-01-04 1:13 ` John Yates
2016-01-04 1:18 ` Dmitry Gutov
[not found] ` <CAJnXXog5fO_h5UNnVR67EJtT+u7+G-BVMFV3FnJgK=weGj0m_w@mail.gmail.com>
2016-01-04 2:01 ` Dmitry Gutov
2016-01-04 0:55 ` John Wiegley
2016-01-04 1:14 ` Dmitry Gutov
2016-01-04 2:56 ` Stefan Monnier
2016-01-04 3:47 ` Dmitry Gutov
[not found] ` <CAJnXXogonsWpqadNpX0BijzoiztorYP1d=b31seBfvGVBwwT_Q@mail.gmail.com>
[not found] ` <5689CC5C.4000408@yandex.ru>
[not found] ` <CAJnXXojy1b6LUdXcC+cDVPYT-OJMXCE8m8yqObE9oUYwU_PGbg@mail.gmail.com>
2016-01-04 2:34 ` Dmitry Gutov
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=5689C3D0.1050708@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).