From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?UTF-8?B?QW5kcmVhcyBSw7ZobGVy?= Newsgroups: gmane.emacs.devel Subject: Re: fill-paragraph ill designed Date: Wed, 26 Aug 2015 14:22:21 +0200 Message-ID: <55DDAF7D.4000809@online.de> References: <55DC2621.4030905@online.de> <55DD5D02.9090407@online.de> <87bndule6e.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1440591793 24607 80.91.229.3 (26 Aug 2015 12:23:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 26 Aug 2015 12:23:13 +0000 (UTC) Cc: Tassilo Horn , rms@gnu.org, Stefan Monnier To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 26 14:23:05 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZUZjG-0007Ax-58 for ged-emacs-devel@m.gmane.org; Wed, 26 Aug 2015 14:22:58 +0200 Original-Received: from localhost ([::1]:38026 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZUZjF-0005y3-MN for ged-emacs-devel@m.gmane.org; Wed, 26 Aug 2015 08:22:57 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46359) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZUZiv-0005vn-65 for emacs-devel@gnu.org; Wed, 26 Aug 2015 08:22:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZUZir-0001Ou-8v for emacs-devel@gnu.org; Wed, 26 Aug 2015 08:22:37 -0400 Original-Received: from mout.kundenserver.de ([212.227.126.131]:62780) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZUZiq-0001Np-W6; Wed, 26 Aug 2015 08:22:33 -0400 Original-Received: from [192.168.178.31] ([77.6.218.200]) by mrelayeu.kundenserver.de (mreue003) with ESMTPSA (Nemesis) id 0Le960-1YwJFR1FZE-00pqeR; Wed, 26 Aug 2015 14:22:29 +0200 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 In-Reply-To: <87bndule6e.fsf@gnu.org> X-Provags-ID: V03:K0:jQ5nAjsStqvZ71dvp402DgiOKC3V2cwptfbPULf+hoIizp7KUSQ +a8LUsmncpBYBUTyqFk3m3Nna/+fplItAgMIy8uo1vo8ySiZGZ2zwPpxYS1awpIYr+zu37m 2RgBx+QC5ZxlXkC5Zkla25tPrQk8LnPtXWORjl3YkGKvd52Z0viKu0PIRiOmRDvBUkZLes7 TfQohZR+LQ7y0NU9epq5Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:FWIwT3lQSm4=:LMjLhaEP0jpoQb5ghUHck4 nB1PN9f/Af0u/1U+zTW48ouHk9GioLPnD+BmXMLV7H5G4gN9kkSkoSPE8U0Zwh+DaBrM+nGVc 3HjHk7sJn2JjAL1usEXjGI9LaogWuP/ioNmS0mbxbGsmUgK4V5hMVMHB2AtMCkX4hNhgdP23f WxXV7XL8WYluJiMR43S9y867L8+l/QW8tTlxn6Iw3AvOfxN2DSaqciNMneY7NjEVhTH5Q3aV7 zvghRTOplghX0YpJdeAItLh7daOsoRss1Y9ERDlVmnnRqCYaLvelpXLgTroMPvVMBaNGgQ0cf +I9YCxnYvKD43SLvCDkUj4EqUYQDsRcehXfWdGS9Kq2/QY4oVtEfgg+K4Hr3kU7mAITJxLgnE 92vrzTpCWHULpKql9BeJlXkvSYg5VQg9q+P6D0XqHQrkNUXwHIq7PnyaFQZ6/QxGsCA4LLd5Y KAcfRon4ZXOmyaBPSV31qCaVXQUEelwVD8qGq9M//FITansI62Ufl/1nZiwcUaXr6RWLxMx4E W1XmFXFaIEUjCSfKFza6Tw2CZr2F+5Jj0hWsfhhLqt9dd3o0FzQL7mwYv/0kANGOqg4WMBE36 /+NuAKw/cQ6vSTz5Aqn9sq3/cKo6orFoS20v50JwywHQsfAoP12p7d7LnznLc/3Qzy7F67aDU v4xAfwzR+dnr4q9msFk4dQXT9BL6vx9msmq/nrVWHeRm6vs3rrtmPJTpubtP066HFzSM3emuy QHdyuNO4algdUTV9 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 212.227.126.131 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:189193 Archived-At: Am 26.08.2015 um 09:08 schrieb Tassilo Horn: > Andreas Röhler writes: > >>> There is a lot of ugliness in the way fill-paragraph works, but >>> developing a replacement that works ok in practice is harder than it >>> looks. I recall a time that we tried. >> What would prevent switching the clauses as suggested? > IMO, it makes completely sense that `fill-paragraph' delegates to > `fill-region' if the region is active so that not every mode-specific > `fill-paragraph-function' has to do that on its own. Let's assume region is up to or inside a documentation-string in Python. Then fill-region will be called instead of fill-paragraph-function. But how should fill-region get access or know about Python docu-string styles?