all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Liu <sdl.web@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: emacs: are multi-char parentheses possible?
Date: Tue, 10 Jun 2014 08:14:37 +0800	[thread overview]
Message-ID: <m3lht5lixe.fsf@gmail.com> (raw)
In-Reply-To: <jwvbnu2w15i.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 09 Jun 2014 11:38:44 -0400")

On 2014-06-09 11:38 -0400, Stefan Monnier wrote:
> Maybe you tried a "forward up-list" where the closing ">>" hadn't yet been
> syntax-propertized?
>
> This technique has some downsides, but in the case of << ... >> it might
> work well enough.

Thanks for the confirmation. With the syntax-table property the normal
sexp motion commands actually work. But I was in a smie mode which
redefines forward-sexp and the lexer and grammar aren't setup to handle
<< and >> so it appeared forward-sexp failed. I was looking in the wrong
direction for fix.

> For things like "begin...end" it's more annoying (e.g. backward word
> will stop right between the "b" and the "egin" and forward-word will
> stop right between "en" and "d").  For those, SMIE might be a better
> option (which uses hooks in show-paren and forward-sexp to try and make
> them do The Right Thing, tho the up-list case is only 90% working).

I like this feature ;)

Leo



  reply	other threads:[~2014-06-10  0:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3ppiilhna.fsf@gmail.com>
2014-06-09 15:38 ` emacs: are multi-char parentheses possible? Stefan Monnier
2014-06-10  0:14   ` Leo Liu [this message]
2014-06-10  2:21     ` Stefan Monnier
2014-06-10  9:22       ` Leo Liu
2014-06-10 20:20         ` Stefan Monnier
2014-06-11  7:40         ` Andreas Röhler
2014-06-10  5:13   ` Andreas Röhler

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=m3lht5lixe.fsf@gmail.com \
    --to=sdl.web@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.