From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Fabrice Popineau <fabrice.popineau@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Lisp mode syntax table
Date: Tue, 18 Feb 2014 09:00:57 -0500 [thread overview]
Message-ID: <jwveh30il2e.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAFgFV9PqZeYRDuQgpu29A8XbmH01f-AcWvhcSsj0PsSzS_ou4w@mail.gmail.com> (Fabrice Popineau's message of "Tue, 18 Feb 2014 06:53:30 +0100")
> The problem may not be the class of ?| per se, but the interaction with ?:
> The whole thing |rdf|:|someClass| should be considered as a symbol.
Right, that is something Emacs syntax tables can't currently express.
> At the moment, using smartparen to push a ?) through this symbol,
> you start by putting it here :
> |rdf|):|someClass|
I think this step is largely unavoidable: your symbol is not
syntactically atomic, instead it has structure. To avoid this step,
Emacs would need to understand that the ":" infix operator can't take
a parenthesized expression on its left hand side.
> then here
> |rdf| :)|someParen|
This step OTOH is definitely avoidable. E.g. SMIE's forward-sexp would
know to skip ":|someClass|" rather than just ":".
> (notice that a space has been added)
Seems like a misfeature of smartparen.
> if ?| shouldn't be part of the symbol rather than a string delimiter.
As mentioned, it has string syntax for things like |)| and | |.
> In CL standard syntax, it is also used in multi lines comments
> #| ... |#
Yes, Emacs understands those, IIRC,
Stefan
next prev parent reply other threads:[~2014-02-18 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 10:43 Lisp mode syntax table Fabrice Popineau
2014-02-17 20:19 ` Stefan Monnier
2014-02-17 22:10 ` Fabrice Popineau
2014-02-18 0:19 ` Stefan Monnier
2014-02-18 5:53 ` Fabrice Popineau
2014-02-18 14:00 ` Stefan Monnier [this message]
2014-02-18 19:34 ` Fabrice Popineau
2014-02-18 6:02 ` Fabrice Popineau
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=jwveh30il2e.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=fabrice.popineau@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.