From: Jean Louis <bugs@gnu.support>
To: Qiantan Hong <qhong@mit.edu>
Cc: "emacs-tangents@gnu.org" <emacs-tangents@gnu.org>
Subject: Re: Question: what is Emacs mode?
Date: Sat, 24 Apr 2021 07:22:49 +0300 [thread overview]
Message-ID: <YIOdGVko8MgFDQrY@protected.localdomain> (raw)
In-Reply-To: <79668953-FBBB-4843-A5FD-C39E08B50CCC@mit.edu>
* Qiantan Hong <qhong@mit.edu> [2021-04-24 01:05]:
> 1. Do we want node-local modes?
> That looks very natural to have. We may edit our code using sexp-mode,
> but inside docstring, we could use doc-mode locally.
> This also covers lots of thing in Emacs that were done using text-properties.
> E.g. bold-mode and background-color-mode (not sure if they’re
> good idea though).
TECHNOLOGY TEMPLATE PROJECT OHS Framework
https://www.dougengelbart.org/content/view/110/460/
I suggest that you also look at Doug Engelbart's work.
Your plan seem that text will become s-exp, chunked, and this may
allow very fine elementary objects to be incorporated, further you can
read in that reference what else could be done. That type of s-exp
text could become so much more than Hyperlinked text.
> 3. Suppose we now have node-local variables and node-local modes, what’s the relation
> between those of parent nodes and child nodes?
> It seems natural to let child node inherit modes and variables from parent nodes.
> E.g., I might just turn on outline-mode on the ‘((Section title-A …)) node in
> (defun very-complex-function-that-require-a-paper ()
> ‘((Section title-A
> (Paragraph lorem ipsum)
> (Section subtitle-B
> (Paragraph lorem ipsum))))
> *code*)
> And it affects the whole sub-tree.
> However, are there cases that one don’t want a whole subtree to inherit a mode/variable?
> Can we safely assume they all get inherited?
I will say something what may not look possible, I rather think it is
possible. It would be good if each of those nodes would have its
unique ID, as then it becomes possible to have someting similar as
OPML able to reference those parts of text even if the node change its
position. Maybe is not feasible.
When thinking about modes, they are turned on automatically in Emacs
based on some factors of recognition like extension or magic headers
or else. Your each different node could have a different mode, why
not, that is liberty then.
Question is the speed.
Will that system have extension language and which one? Will it be
Emacs Lisp or different?
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
Sign an open letter in support of Richard M. Stallman
https://stallmansupport.org/
https://rms-support-letter.github.io/
next prev parent reply other threads:[~2021-04-24 4:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 20:43 Question: what is Emacs mode? Qiantan Hong
2021-04-23 21:11 ` Jean Louis
2021-04-23 22:04 ` Qiantan Hong
2021-04-24 4:22 ` Jean Louis [this message]
2021-04-24 5:00 ` Qiantan Hong
2021-04-24 9:22 ` Jean Louis
2021-04-29 3:39 ` Qiantan Hong
2021-04-29 5:02 ` Jean Louis
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=YIOdGVko8MgFDQrY@protected.localdomain \
--to=bugs@gnu.support \
--cc=emacs-tangents@gnu.org \
--cc=qhong@mit.edu \
/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).