all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Mon, 17 Feb 2014 19:19:19 -0500	[thread overview]
Message-ID: <jwvppmljmz1.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAFgFV9N1+7_M383k5dVdb9zq-zFagjZROfEMu_0YVYmK5hixVg@mail.gmail.com> (Fabrice Popineau's message of "Mon, 17 Feb 2014 23:10:04 +0100")

>> > |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.

Wait, I think I completely misunderstood your problem.
You're not talking about Emacs Lisp code but about "other Lisp" code
(Common Lisp?), right?

In that case |rdf|:|someClass| might be fine, indeed, but in that case
also a syntax of "\"" for ?| sounds like the right thing to do (e.g. so
that forward-sexp will properly jump over the |)| symbol).

> I recently used buffers with lots of symbols of the form
> |rdf|:|someClass| and smartparen can't behave well in this case,

Might be a problem in smartparen.  What does it do that you dislike?


        Stefan



  reply	other threads:[~2014-02-18  0:19 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 [this message]
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=jwvppmljmz1.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.