From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Lisp mode syntax table
Date: Mon, 17 Feb 2014 23:10:04 +0100 [thread overview]
Message-ID: <CAFgFV9N1+7_M383k5dVdb9zq-zFagjZROfEMu_0YVYmK5hixVg@mail.gmail.com> (raw)
In-Reply-To: <jwv8ut9mr5i.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
2014-02-17 21:19 GMT+01:00 Stefan Monnier <monnier@iro.umontreal.ca>:
> > Is there a good reason why:
> > (with-syntax-table lisp-mode-syntax-table
> > (string (char-syntax ?\|)))
> > "\""
>
> IIRC some Lisps use that for symbols.
>
> > |rdf|:|someClass| and smartparen can't behave well in this case,
>
> If it hurts don't do that. Really, it seems like a particularly bad idea.
>
>
Usually, I try not to hurt myself too much but you know what it is...
Care to explain why it is such a bad idea?
Sometimes you need case-sensitive symbols
in Lisp, and semantic web (RDF, OWL and so on) is one.
> > Would that switch imply any drawbacks I can't think of?
>
> I'm not sure what lisp-mode-syntax-table should use, but so far
> emacs-lisp-mode-syntax-table should use "_" for the syntax of ?|
>
>
And this is what I advocated for.
> OTOH, someone might want to make |...| into a new syntax for symbols, in
> which case your |rdf|:|someClass| might break in the future.
>
> Sure but the same guy could also redefine ( and ) in the reader ...
Fabrice
[-- Attachment #2: Type: text/html, Size: 1939 bytes --]
next prev parent reply other threads:[~2014-02-17 22:10 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 [this message]
2014-02-18 0:19 ` Stefan Monnier
2014-02-18 5:53 ` Fabrice Popineau
2014-02-18 14:00 ` Stefan Monnier
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=CAFgFV9N1+7_M383k5dVdb9zq-zFagjZROfEMu_0YVYmK5hixVg@mail.gmail.com \
--to=fabrice.popineau@gmail.com \
--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 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.