all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jason Vas Dias <jason.vas.dias@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-devel@gnu.org
Subject: Re: lisp-mode: how to disable parentheses matching on non-ASCII '[({]' '[})]' UTF-8 parenthesis chars ?
Date: Tue, 8 Aug 2023 18:23:22 +0100	[thread overview]
Message-ID: <CALyZvKzRxgs13nGttX3cgYhOmWo3kECckGNBV4wsb+DHRe83ig@mail.gmail.com> (raw)
In-Reply-To: <87ttt93n84.fsf@ucl.ac.uk>

That worked, thank you!

 (mapcar (lambda (c)
	 (eval (list 'modify-syntax-entry c "."))
	)
 '( ?\❨ ?\❩ ?\❪ ?\❫ ?\⟮ ?\⟯ ?\⦅ ?\⦆ ?\⸨ ?\⸩ ?\﴾ ?\﴿ ?\《 ?\》 ?\﹙ ?\﹚
?\(  ?\) ?\⦅ ?\⦆)
)

Strange, I am not able to get that to work without the 'eval' .


On 08/08/2023, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> On Tuesday,  8 Aug 2023 at 08:37, Jason Vas Dias wrote:
>>    Please could some emacs guru let me know how the 'lisp-mode' based
>>    source editing modes can be made to ignore / treat as normal
>>    characters such not-ascii-'(' and not-ascii-')' characters and to
>>    NOT attempt to balance them or to consider them parenthesis syntax
>>    ? No LISP parser I am using considers them to be syntax.
>
> You could try
>
>     (modify-syntax-entry ?< ".")
>
> where you replace < with each individual character you do not wish to be
> treated as a paren.
>
> --
> Eric S Fraga via gnus (Emacs 30.0.50 2023-08-07) on Debian 12.1
>
>
>



  reply	other threads:[~2023-08-08 17:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08  7:37 lisp-mode: how to disable parentheses matching on non-ASCII '[({]' '[})]' UTF-8 parenthesis chars ? Jason Vas Dias
2023-08-08  9:19 ` Eric S Fraga
2023-08-08 17:23   ` Jason Vas Dias [this message]
2023-08-08 12:10 ` Eli Zaretskii
2023-08-08 17:10 ` Eric Frederickson

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=CALyZvKzRxgs13nGttX3cgYhOmWo3kECckGNBV4wsb+DHRe83ig@mail.gmail.com \
    --to=jason.vas.dias@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-devel@gnu.org \
    /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.