From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Rudolf Schlatte Newsgroups: gmane.emacs.devel Subject: Re: Should yaml-ts-mode inherit from prog-mode? Date: Tue, 21 Mar 2023 16:03:21 +0100 Message-ID: References: <83mt478w48.fsf@gnu.org> <83ileu6xrv.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26466"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (darwin) To: emacs-devel@gnu.org Cancel-Lock: sha1:YteYNmIRV0bV6S4KajVxn4FmbhM= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Mar 22 04:22:05 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pep37-0006gI-2X for ged-emacs-devel@m.gmane-mx.org; Wed, 22 Mar 2023 04:22:05 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pep2I-0004pL-30; Tue, 21 Mar 2023 23:21:14 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pedWN-0000oh-6N for emacs-devel@gnu.org; Tue, 21 Mar 2023 11:03:35 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pedWL-0007Rf-BC for emacs-devel@gnu.org; Tue, 21 Mar 2023 11:03:30 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1pedWI-000Ads-Ou for emacs-devel@gnu.org; Tue, 21 Mar 2023 16:03:26 +0100 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -15 X-Spam_score: -1.6 X-Spam_bar: - X-Spam_report: (-1.6 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Tue, 21 Mar 2023 23:21:12 -0400 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:304690 Archived-At: Yuri Khan writes: > In these cases, some users might want to ‘fill-paragraph’ Markdown > paragraphs inside a literal-styled YAML block. > > description: | > Create a new foo > and return a 201 with `Location:` header set. > > If the input data is invalid, > return a 400 with a detailed error report. > > Without knowing the syntax for the YAML string value, there is not > enough information to allow or restrict ‘fill-paragraph’. > > A sensible compromise could be to allow ‘fill-paragraph’ at user’s > discretion in all string literals, but recognize YAML’s string start > and end as paragraph boundaries. Good points and convincing examples, thank you. It's also easier to describe the behavior that way: "`fill-paragraph' is enabled inside block and flow scalars. Text inside a block or flow scalar will be reflowed as usual, with empty lines acting as paragraph boundaries." I.e., your example would be reflowed like this (after `M-q' on the line starting with "Create" or "and"), if I understood it correctly? description: | Create a new foo and return a 201 with `Location:` header set. If the input data is invalid, return a 400 with a detailed error report.