unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Thibaut Verron <thibaut.verron@gmail.com>
To: Pierre Rouleau <prouleau001@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: How to make `forward-sexp` handle other balanced character-pairs such as < and > or << and >> in erlang-mode or others?
Date: Tue, 28 Sep 2021 05:45:00 +0200	[thread overview]
Message-ID: <CAFsi02T3nEg_9mSwJBaJTqD=OWAjugd4ZAGEW5Ct1YOFmKeU5Q@mail.gmail.com> (raw)
In-Reply-To: <CALTqLibhPqjm0JL1yF8+XRYihsiUqiquaA-Mg4UUXHsnushyiw@mail.gmail.com>

On Mon, 27 Sep 2021, 23:48 Pierre Rouleau, <prouleau001@gmail.com> wrote:

>
>
> On Mon, Sep 27, 2021 at 5:34 PM Thibaut Verron <thibaut.verron@gmail.com>
> wrote:
>
>> Le lun. 27 sept. 2021 à 23:22, Pierre Rouleau <prouleau001@gmail.com> a
>> écrit :
>>
>> > On Mon, Sep 27, 2021 at 5:14 PM Thibaut Verron <
>> thibaut.verron@gmail.com> wrote:
>> >>
>>
>> How are you modifying the syntax table? Directly in the source code of
>> the erlang mode, or in your user configuration?
>>
>> For investigation purpose I modified the erlang.el file directly and then
> byte compiled it,
> ensuring that my modifications are taken by adding a special variable I
> can check.
>

That's a good approach, investigation purposes or not. If you want to
accelerate the feedback cycle, you don't even need to byte compile, just
delete the elc file (or tell emacs to always prefer a newer el over an elc,
there is a variable for that) and load the mode normally.


> I commented out the lines that identified ?< and ?> as "." and added after
> the following 2 lines:
>
> (modify-syntax-entry ?< "(>" table)
> (modify-syntax-entry ?> "(<" table)
>

There is a typo there, the second one should be )<.

Best wishes,
Thibaut


  reply	other threads:[~2021-09-28  3:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 20:53 How to make `forward-sexp` handle other balanced character-pairs such as < and > or << and >> in erlang-mode or others? Pierre Rouleau
2021-09-27 21:13 ` Nikolay Kudryavtsev
2021-09-27 21:17   ` Pierre Rouleau
2021-09-27 21:14 ` Thibaut Verron
2021-09-27 21:22   ` Pierre Rouleau
2021-09-27 21:34     ` Thibaut Verron
2021-09-27 21:48       ` Pierre Rouleau
2021-09-28  3:45         ` Thibaut Verron [this message]
2021-09-28 11:22           ` Pierre Rouleau

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFsi02T3nEg_9mSwJBaJTqD=OWAjugd4ZAGEW5Ct1YOFmKeU5Q@mail.gmail.com' \
    --to=thibaut.verron@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=prouleau001@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).