From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: Drew Adams <drew.adams@oracle.com>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: [External] : forward-sexp
Date: Fri, 11 Aug 2023 21:20:34 +0200 [thread overview]
Message-ID: <d422a471-9188-69bb-247b-a0a86328bf8a@easy-emacs.de> (raw)
In-Reply-To: <SJ0PR10MB5488DA1FA58E72DA59A0DBAAF310A@SJ0PR10MB5488.namprd10.prod.outlook.com>
Am 11.08.23 um 19:43 schrieb Drew Adams:
>> M-x forward-sexp RET works from the beginning of the first line, but
>> does nothing from the beginning at the second. Are there reasons for
>> this? [ asdf ] .
> The syntactic definition of "sexp" depends on the context, e.g., the
> current major mode. Without knowing how a "sexp" is defined in your
> context, we can't help much. That said, trying it in a Lisp mode tells
> me that an error is raised when I try it at the beginning of the
> second line, because: Debugger entered--Lisp error: (scan-error
> "Unbalanced parentheses" 450 459) scan-sexps(450 1) forward-sexp(1)
> funcall-interactively(forward-sexp 1) call-interactively(forward-sexp
> nil nil) command-execute(forward-sexp) IOW, the `(' char isn't
> balanced with a `)' char, so parsing to the end of the `[' sexp isn't
> possible.
let assume fundamental mode, cursor at opening bracket: what puzzles me,
with [ asdf ] it recognizes the opening bracket.
In such a case, it should not look inside, just travel onto the closing one.
But with [(&asdf] it fails.
next prev parent reply other threads:[~2023-08-11 19:20 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 17:23 forward-sexp Andreas Röhler
2023-08-11 17:43 ` [External] : forward-sexp Drew Adams
2023-08-11 17:58 ` Emanuel Berg
2023-08-11 19:20 ` Andreas Röhler [this message]
2023-08-11 19:47 ` Pierre Rouleau
2023-08-11 20:02 ` Andreas Röhler
2023-08-11 20:07 ` Drew Adams
2023-08-11 20:09 ` Pierre Rouleau
2023-08-11 20:17 ` Emanuel Berg
2023-08-11 20:14 ` Emanuel Berg
2023-08-12 20:41 ` Drew Adams
2023-08-12 22:23 ` Emanuel Berg
2023-08-13 14:02 ` Pierre Rouleau
2023-08-13 15:42 ` Drew Adams
2023-08-13 16:45 ` Pierre Rouleau
2023-08-20 4:08 ` Emanuel Berg
2023-08-20 4:04 ` Emanuel Berg
2023-08-20 3:50 ` Emanuel Berg
2023-08-13 15:08 ` Drew Adams
2023-08-11 20:23 ` Drew Adams
2023-08-11 20:30 ` Emanuel Berg
2023-08-12 20:42 ` Drew Adams
2023-08-12 22:12 ` Emanuel Berg
2023-08-13 15:08 ` Drew Adams
2023-08-12 6:44 ` Andreas Röhler
2023-08-11 20:09 ` Emanuel Berg
2023-08-11 20:01 ` Drew Adams
2023-08-11 20:06 ` Emanuel Berg
2023-08-12 20:41 ` Drew Adams
2023-08-12 22:14 ` Emanuel Berg
2023-08-13 6:53 ` Andreas Röhler
2023-08-13 6:57 ` Eli Zaretskii
2023-08-13 15:04 ` Drew Adams
2023-08-20 4:48 ` Emanuel Berg
2023-09-09 7:22 ` 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
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=d422a471-9188-69bb-247b-a0a86328bf8a@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@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.
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).