unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: [External] : forward-sexp
Date: Sun, 20 Aug 2023 05:50:36 +0200	[thread overview]
Message-ID: <87lee6bcdv.fsf@dataswamp.org> (raw)
In-Reply-To: CALTqLiZszq1cg+LaHtZK8HVLTKd0OWqVzzS94Pk2gMrC2LE4Rw@mail.gmail.com

Pierre Rouleau wrote:

>> No, that would be the way to do it, if there is no notion
>> of symbolic expressions, one would fall back to some other
>> behavior, preferably something not to far away from both
>> the name of the function or the usual way it is used in
>> practice, i.e. what would be thought to be expected to
>> reflect that in the supposed sexp-less setting ...
>>
>> So either one would have a small set of functions that
>> would work everywhere, but differently depending on the
>> context, _or_ one would have a huge, always growing set of
>> functions and every one of those would work in one and only
>> one context ...
>>
>
> Would it not help to have a selectable behaviour: - by
> default the end of a balanced expression expects inner
> expressions to also be balanced (ignoring nested comments) -
> another mode would try to match the starting character to
> the matching end character, ignoring comments and
> unbalanced/partial expressions made of other characters.

For programming one could absolutely think of such an idea,
a default behavior.

Because there is so much that are based on the parenthesis,
brackets and such delimiters.

And it would be harmless to since if the local modes didn't
like it, they could overwrite the functions with local ones.

And it would be even cooler if the local variation would be
a local variation of the sexp, local to that mode, and then
the navigation would not have to be reset, just the
local sexp!

Maybe difficult to do so overwriting the navigation would
still be allowed ;)

-- 
underground experts united
https://dataswamp.org/~incal




  parent reply	other threads:[~2023-08-20  3:50 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
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 [this message]
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=87lee6bcdv.fsf@dataswamp.org \
    --to=incal@dataswamp.org \
    --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).