From: Rudolf Schlatte <rudi@constantly.at>
To: emacs-devel@gnu.org
Subject: Re: Should yaml-ts-mode inherit from prog-mode?
Date: Tue, 21 Mar 2023 14:54:09 +0100 [thread overview]
Message-ID: <m2bkkm2ose.fsf@eduroam-193-157-164-7.wlan.uio.no> (raw)
In-Reply-To: 83ileu6xrv.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
> We should instead fix yaml-ts-mode by providing a proper
> fill-paragraph-function for it. No one said that the default
> text-mode one will do TRT.
Quoting yaml.org: “YAML is a human-friendly data serialization language
for all programming languages.” (See https://yaml.org/spec/1.2.2/ for
all the gory details.) Both whitespace and line breaks are semantically
meaningful.
One meaningful behavior for `fill-paragraph' could be to allow it only
within YAML flowed blocks and flow scalars (see
https://yaml-multiline.info):
script: |
# this block cannot be refilled.
apt-get -y update
apt-get -y install my-necessary-package
description: >
The above script updates the system and installs a necessary
package.
This is a second line, where we give more information We had to
leave an empty line in the yaml file to get a line break.
comment: "This is a double-quoted flow scalar.
We have to escape line breaks like this:\
All other line breaks in the string
are read as spaces."
next prev parent reply other threads:[~2023-03-21 13:54 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 19:07 Should yaml-ts-mode inherit from prog-mode? Romanos Skiadas
2023-03-03 4:23 ` Richard Stallman
2023-03-04 18:24 ` Romanos Skiadas
2023-03-20 1:52 ` Randy Taylor
2023-03-20 12:07 ` Eli Zaretskii
2023-03-20 14:37 ` Rudolf Schlatte
2023-03-20 16:20 ` Brian Cully via Emacs development discussions.
2023-03-20 16:53 ` Eli Zaretskii
2023-03-21 11:19 ` Jostein Kjønigsen
2023-03-21 13:26 ` Eli Zaretskii
2023-03-21 13:54 ` Rudolf Schlatte [this message]
2023-03-21 14:43 ` Yuri Khan
2023-03-21 15:03 ` Rudolf Schlatte
2023-03-22 6:04 ` Yuri Khan
2023-03-22 2:37 ` David Ongaro
2023-03-21 3:13 ` Randy Taylor
-- strict thread matches above, loose matches on Subject: below --
2023-02-28 12:24 Romanos Skiadas
2023-02-28 15:52 ` Basil Contovounesios
2023-03-01 14:08 ` Randy Taylor
2023-03-01 14:28 ` Lynn Winebarger
2023-03-01 16:35 ` Vasilij Schneidermann
2023-03-02 12:55 ` Lynn Winebarger
2023-03-02 13:44 ` Philip Kaludercic
2023-03-03 9:00 ` Rudolf Schlatte
2023-03-03 21:58 ` Yuan Fu
2023-03-04 18:45 ` Juri Linkov
2023-02-28 17:50 ` Daniel Fleischer
2023-02-28 17:56 ` Daniel Fleischer
2023-02-28 18:33 ` Dmitry Gutov
2023-03-01 13:35 ` Basil Contovounesios
2023-03-12 2:14 ` Ongaro
2023-03-12 9:20 ` Daniel Fleischer
2023-03-12 12:31 ` Rudolf Schlatte
2023-03-13 8:44 ` Yuri Khan
2023-03-14 1:45 ` David Ongaro
2023-03-01 7:46 ` Matthias Meulien
2023-03-01 13:45 ` Basil Contovounesios
2023-03-07 11:27 ` Jostein Kjønigsen
2023-03-07 14:28 ` Matthias Meulien
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2bkkm2ose.fsf@eduroam-193-157-164-7.wlan.uio.no \
--to=rudi@constantly.at \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.