unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>,
	"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : forward-sexp
Date: Fri, 11 Aug 2023 17:43:17 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488DA1FA58E72DA59A0DBAAF310A@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <53741ea9-b3ac-67a6-519f-b8977df30bf9@easy-emacs.de>

> 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 ]
> [(&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.

  reply	other threads:[~2023-08-11 17:43 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 ` Drew Adams [this message]
2023-08-11 17:58   ` [External] : forward-sexp Emanuel Berg
2023-08-11 19:20   ` Andreas Röhler
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=SJ0PR10MB5488DA1FA58E72DA59A0DBAAF310A@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=andreas.roehler@easy-emacs.de \
    --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).