From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <incal@dataswamp.org>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : forward-sexp
Date: Sun, 13 Aug 2023 15:08:31 +0000 [thread overview]
Message-ID: <SJ0PR10MB54889138A99A288F52963C1AF316A@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87sf8nkize.fsf@dataswamp.org>
> >>> Put your cursor just before a `[' char and use `C-u C-x
> >>> ='. Same thing for a `(' char and a `"' char. What does it
> >>> say for syntax?
> >>
> >> One EASY way of solving this would be that
> >> everyone just used the Lisp syntax ...
> >
> > Solving what? If you think you see a bug, then `M-x
> > report-emacs-bug'. (I don't see any bug.) [...] Vive
> > la différence!
>
> But if everyone used the same syntax, everyone could
> access everyone's data in any way they would like.
"La différence" in question is not this person
versus that person (but that too is available,
through customization). The difference is that
of different major modes. And different major
modes are often for different programming or
natural _languages_.
And different languages treat different char
and sequences of chars differently. Likewise
different kinds of textual data - "everyone's
data" is not the same. The syntax of JSON
data is not that of XML data.
> So in a way it would be even more different
> what way. But I think it would be awkward to
> submit this as a bug to Emacs
I don't expect such a bug/ER to gain traction,
but then again, nothing specific specifying
what's requested has been presented so far.
Maybe the devil is in the details.
My point in suggesting `M-x report-emacs-bug'
is that that's how to specify some change in
behavior you'd like Emacs to adopt. (It's not
the only way, but it is one recommended way.)
> - especially since we already use the Lisp syntax.
No, we don't. Certainly not for many major
modes. Otherwise, much of what a major mode
defines wouldn't even exist - from movement
(including `forward-sexp'), to font-locking,
to error handling, to ...
This is the point. (And I'm surprised it's
not getting across more easily.) Different
modes use different syntax. Sometimes,
often (even most often?). Is this really a
surprise or hard to fathom?
next prev parent reply other threads:[~2023-08-13 15:08 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
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 [this message]
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=SJ0PR10MB54889138A99A288F52963C1AF316A@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=incal@dataswamp.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).