From unknown Wed Jun 25 03:52:29 2025 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailer: MIME-tools 5.509 (Entity 5.509) Content-Type: text/plain; charset=utf-8 From: bug#3568 <3568@debbugs.gnu.org> To: bug#3568 <3568@debbugs.gnu.org> Subject: Status: 23.0.94; no doc for character composition Reply-To: bug#3568 <3568@debbugs.gnu.org> Date: Wed, 25 Jun 2025 10:52:29 +0000 retitle 3568 23.0.94; no doc for character composition reassign 3568 emacs submitter 3568 "Drew Adams" severity 3568 minor thanks From drew.adams@oracle.com Sun Jun 14 16:17:49 2009 Received: (at submit) by emacsbugs.donarmstrong.com; 14 Jun 2009 23:17:49 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.5-bugs.debian.org_2005_01_02 (2008-06-10) on rzlab.ucr.edu X-Spam-Level: X-Spam-Bayes: score:0.5 Bayes not run. spammytokens:Tokens not available. hammytokens:Tokens not available. X-Spam-Status: No, score=-2.9 required=4.0 tests=AWL,FOURLA autolearn=no version=3.2.5-bugs.debian.org_2005_01_02 Received: from fencepost.gnu.org (fencepost.gnu.org [140.186.70.10]) by rzlab.ucr.edu (8.14.3/8.14.3/Debian-5) with ESMTP id n5ENHiw3001492 for ; Sun, 14 Jun 2009 16:17:46 -0700 Received: from mx10.gnu.org ([199.232.76.166]:37381) by fencepost.gnu.org with esmtp (Exim 4.67) (envelope-from ) id 1MFyxM-0001Ox-1E for emacs-pretest-bug@gnu.org; Sun, 14 Jun 2009 19:17:44 -0400 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1MFyxK-000434-0W for emacs-pretest-bug@gnu.org; Sun, 14 Jun 2009 19:17:43 -0400 Received: from rcsinet12.oracle.com ([148.87.113.124]:45451 helo=rgminet12.oracle.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MFyxI-00041u-VM for emacs-pretest-bug@gnu.org; Sun, 14 Jun 2009 19:17:41 -0400 Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rgminet12.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n5ENHKkP026344 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 14 Jun 2009 23:17:22 GMT Received: from abhmt009.oracle.com (abhmt009.oracle.com [141.146.116.18]) by acsinet15.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n5ENInZJ006298 for ; Sun, 14 Jun 2009 23:18:49 GMT Received: from dradamslap1 (/141.144.160.38) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 14 Jun 2009 16:17:33 -0700 From: "Drew Adams" To: Subject: 23.0.94; no doc for character composition Date: Sun, 14 Jun 2009 16:17:35 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Thread-Index: AcntRk0F/YvRcAyQTz+MYu49LHPLig== X-Source-IP: abhmt009.oracle.com [141.146.116.18] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A01020A.4A35850E.001A:SCFSTAT5015188,ss=1,fgs=0 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 1) I can find no doc at all regarding character composition, beyond the cursory explanation given in the Emacs manual, node Input Methods. In particular, there is nothing in the Elisp manual about it. No documentation of functions such as `compose-region' and `compose-chars'. And there is no usage commentary in `composite.el'. How does one compose characters using Emacs Lisp? If characters have been composed, how do you decompose them? Are there any caveats to be aware of? Users will have such questions. For example, this snippet is commonly used here and there to display the word `lambda' as the Greek character: (font-lock-add-keywords mode `(("\\" (0 (progn (compose-region (match-beginning 0) (match-end 0) ,(make-char 'greek-iso8859-7 107)) nil))))) But removing that keyword entry from font-lock-keywords, unfontifying, then refontifying is not sufficient to display `lambda' as a word again. What needs to be done, to restore the normal display of the word `lambda'? This kind of information is missing. Perusing `composite.el', I see that this will do the job: (font-lock-remove-keywords nil `(("\\" (0 (progn (compose-region (match-beginning 0) (match-end 0) ,(make-char 'greek-iso8859-7 107)) nil))))) (save-excursion (goto-char (point-min)) (while (re-search-forward "\\" nil t) (decompose-region (match-beginning 0) (match-end 0)))) But it would be helpful to have a little doc in the Elisp manual explaining how to use character composition. This feature deserves some doc. Compare, for example, the doc for font-locking with that for character composition. Even if these features are not of the same scale, you can see a qualitative difference in the doc support. Look at the commentary in file font-lock.el - a section explaining clearly "How Font Lock mode fontifies", and another section explaining "What is fontification for?". Plenty of Info doc, in both the Emacs and Elisp manuals. Character composition should be better documented. I can understand if the author is not comfortable providing lots of English doc, but someone who understands character composition should do so. Think in terms of how Emacs users and Emacs-Lisp users might make use of this feature, then write that up for those of us who are ignorant. Thanks. In GNU Emacs 23.0.94.1 (i386-mingw-nt5.1.2600) of 2009-05-24 on SOFT-MJASON Windowing system distributor `Microsoft Corp.', version 5.1.2600 configured using `configure --with-gcc (3.4)' From debbugs-submit-bounces@debbugs.gnu.org Wed Apr 27 15:24:03 2016 Received: (at 3568) by debbugs.gnu.org; 27 Apr 2016 19:24:03 +0000 Received: from localhost ([127.0.0.1]:50614 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1avV47-0007VS-Hz for submit@debbugs.gnu.org; Wed, 27 Apr 2016 15:24:03 -0400 Received: from hermes.netfonds.no ([80.91.224.195]:48169) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1avV45-0007V2-Ab for 3568@debbugs.gnu.org; Wed, 27 Apr 2016 15:24:01 -0400 Received: from cm-84.215.1.64.getinternet.no ([84.215.1.64] helo=mouse) by hermes.netfonds.no with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1avV42-0001lP-SR; Wed, 27 Apr 2016 21:24:00 +0200 From: Lars Ingebrigtsen To: "Drew Adams" Subject: Re: bug#3568: 23.0.94; no doc for character composition References: Date: Wed, 27 Apr 2016 21:23:58 +0200 In-Reply-To: (Drew Adams's message of "Sun, 14 Jun 2009 16:17:35 -0700") Message-ID: <87potadfe9.fsf@gnus.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 3568 Cc: 3568@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.0 (/) "Drew Adams" writes: > I can find no doc at all regarding character composition, beyond the > cursory explanation given in the Emacs manual, node Input Methods. > > In particular, there is nothing in the Elisp manual about it. No > documentation of functions such as `compose-region' and > `compose-chars'. > > And there is no usage commentary in `composite.el'. > > How does one compose characters using Emacs Lisp? If characters have > been composed, how do you decompose them? Are there any caveats to be > aware of? Users will have such questions. `compose-region' has a very long doc string... And it seems to have been added to after you wrote this bug report. Does it answer your questions now? -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no From debbugs-submit-bounces@debbugs.gnu.org Wed Apr 27 15:43:08 2016 Received: (at 3568) by debbugs.gnu.org; 27 Apr 2016 19:43:08 +0000 Received: from localhost ([127.0.0.1]:50637 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1avVMZ-00019Q-Ue for submit@debbugs.gnu.org; Wed, 27 Apr 2016 15:43:08 -0400 Received: from aserp1040.oracle.com ([141.146.126.69]:31418) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1avVMY-00018u-Gy for 3568@debbugs.gnu.org; Wed, 27 Apr 2016 15:43:06 -0400 Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u3RJgxh2018006 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 27 Apr 2016 19:43:00 GMT Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by aserv0022.oracle.com (8.13.8/8.13.8) with ESMTP id u3RJgxmB010694 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 27 Apr 2016 19:42:59 GMT Received: from abhmp0005.oracle.com (abhmp0005.oracle.com [141.146.116.11]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id u3RJgwdW013329; Wed, 27 Apr 2016 19:42:58 GMT MIME-Version: 1.0 Message-ID: <623906f5-d8d6-416b-b435-7f3b0f44944a@default> Date: Wed, 27 Apr 2016 12:42:56 -0700 (PDT) From: Drew Adams To: Lars Ingebrigtsen Subject: RE: bug#3568: 23.0.94; no doc for character composition References: <87potadfe9.fsf@gnus.org> In-Reply-To: <87potadfe9.fsf@gnus.org> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6744.5000 (x86)] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Source-IP: aserv0022.oracle.com [141.146.126.234] X-Spam-Score: -3.3 (---) X-Debbugs-Envelope-To: 3568 Cc: 3568@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > > I can find no doc at all regarding character composition, beyond the > > cursory explanation given in the Emacs manual, node Input Methods. > > > > In particular, there is nothing in the Elisp manual about it. No > > documentation of functions such as `compose-region' and > > `compose-chars'. > > > > And there is no usage commentary in `composite.el'. > > > > How does one compose characters using Emacs Lisp? If characters have > > been composed, how do you decompose them? Are there any caveats to be > > aware of? Users will have such questions. >=20 > `compose-region' has a very long doc string... And it seems to have > been added to after you wrote this bug report. Does it answer your > questions now? No. `compose-region' already had that doc string when the bug was reported. That doc string has been around since at least Emacs 22. I would expect some conceptual explanation of character composition in the Elisp manual. Including how to decompose composed chars etc. What the bug report mentions. I don't think that a doc string for one command covers this topic. From debbugs-submit-bounces@debbugs.gnu.org Wed Apr 27 16:11:49 2016 Received: (at 3568) by debbugs.gnu.org; 27 Apr 2016 20:11:49 +0000 Received: from localhost ([127.0.0.1]:50661 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1avVoL-0001qO-Il for submit@debbugs.gnu.org; Wed, 27 Apr 2016 16:11:49 -0400 Received: from eggs.gnu.org ([208.118.235.92]:36524) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1avVoK-0001qC-D2 for 3568@debbugs.gnu.org; Wed, 27 Apr 2016 16:11:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1avVoA-0004Ec-Kp for 3568@debbugs.gnu.org; Wed, 27 Apr 2016 16:11:43 -0400 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_50,RP_MATCHES_RCVD autolearn=disabled version=3.3.2 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:57157) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1avVoA-0004EY-HE; Wed, 27 Apr 2016 16:11:38 -0400 Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3265 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1avVo9-0004MT-LI; Wed, 27 Apr 2016 16:11:38 -0400 Date: Wed, 27 Apr 2016 23:11:22 +0300 Message-Id: <83mvoeyfpx.fsf@gnu.org> From: Eli Zaretskii To: Drew Adams In-reply-to: <623906f5-d8d6-416b-b435-7f3b0f44944a@default> (message from Drew Adams on Wed, 27 Apr 2016 12:42:56 -0700 (PDT)) Subject: Re: bug#3568: 23.0.94; no doc for character composition References: <87potadfe9.fsf@gnus.org> <623906f5-d8d6-416b-b435-7f3b0f44944a@default> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-Spam-Score: -6.0 (------) X-Debbugs-Envelope-To: 3568 Cc: 3568@debbugs.gnu.org, larsi@gnus.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Eli Zaretskii Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -6.0 (------) > Date: Wed, 27 Apr 2016 12:42:56 -0700 (PDT) > From: Drew Adams > Cc: 3568@debbugs.gnu.org > > No. `compose-region' already had that doc string when the bug was > reported. That doc string has been around since at least Emacs 22. Then I don't understand what else do you want to know about compose-region and character composition in general. > I would expect some conceptual explanation of character composition > in the Elisp manual. Please start by explaining what is missing from the doc string of compose-region, because otherwise it is impossible to translate your expectation to any concrete text. The example you gave in the bug report is not about character composition, it's about font-lock. So maybe that is what you need to be explained. However, the bug report says "character composition", so until you agree it's about something else, "character composition" it is. > Including how to decompose composed chars etc. You can't. This question makes no sense. Character composition converts several characters into one or more glyphs to be displayed; you cannot "decompose" them, and in any case the result of such decomposition is known in advance: they are the original characters. > What the bug report mentions. I don't think that a doc string for > one command covers this topic. Well, I think it does. You could change my mind by telling what is it that you miss in that doc string. From debbugs-submit-bounces@debbugs.gnu.org Wed Apr 27 17:18:33 2016 Received: (at 3568) by debbugs.gnu.org; 27 Apr 2016 21:18:33 +0000 Received: from localhost ([127.0.0.1]:50818 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1avWqv-0003LN-1f for submit@debbugs.gnu.org; Wed, 27 Apr 2016 17:18:33 -0400 Received: from userp1040.oracle.com ([156.151.31.81]:33318) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1avWqt-0003L8-9j for 3568@debbugs.gnu.org; Wed, 27 Apr 2016 17:18:31 -0400 Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u3RLIPMb012034 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 27 Apr 2016 21:18:25 GMT Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by userv0022.oracle.com (8.14.4/8.13.8) with ESMTP id u3RLIOno024506 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 27 Apr 2016 21:18:24 GMT Received: from abhmp0005.oracle.com (abhmp0005.oracle.com [141.146.116.11]) by aserv0122.oracle.com (8.13.8/8.13.8) with ESMTP id u3RLILxH007729; Wed, 27 Apr 2016 21:18:23 GMT MIME-Version: 1.0 Message-ID: Date: Wed, 27 Apr 2016 14:18:20 -0700 (PDT) From: Drew Adams To: Eli Zaretskii Subject: RE: bug#3568: 23.0.94; no doc for character composition References: < <87potadfe9.fsf@gnus.org>> <<623906f5-d8d6-416b-b435-7f3b0f44944a@default>> <<83mvoeyfpx.fsf@gnu.org>> In-Reply-To: <<83mvoeyfpx.fsf@gnu.org>> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6744.5000 (x86)] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Source-IP: userv0022.oracle.com [156.151.31.74] X-Spam-Score: -3.3 (---) X-Debbugs-Envelope-To: 3568 Cc: 3568@debbugs.gnu.org, larsi@gnus.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > > No. `compose-region' already had that doc string when the bug was > > reported. That doc string has been around since at least Emacs 22. >=20 > Then I don't understand what else do you want to know about > compose-region and character composition in general. >=20 > > I would expect some conceptual explanation of character composition > > in the Elisp manual. >=20 > Please start by explaining what is missing from the doc string of > compose-region, because otherwise it is impossible to translate your > expectation to any concrete text. >=20 > The example you gave in the bug report is not about character > composition, it's about font-lock. So maybe that is what you need to > be explained. However, the bug report says "character composition", > so until you agree it's about something else, "character composition" > it is. >=20 > > Including how to decompose composed chars etc. >=20 > You can't. This question makes no sense. Character composition > converts several characters into one or more glyphs to be displayed; > you cannot "decompose" them, and in any case the result of such > decomposition is known in advance: they are the original characters. >=20 > > What the bug report mentions. I don't think that a doc string for > > one command covers this topic. >=20 > Well, I think it does. You could change my mind by telling what is it > that you miss in that doc string. I'd like an explanation of character composition, in the Elisp manual. If you don't want to add one, or you don't think it is useful for users, so be it. As one user, I know nothing about this. And I still know nothing about it after reading that doc string. FWIW. From debbugs-submit-bounces@debbugs.gnu.org Wed Apr 27 17:24:45 2016 Received: (at control) by debbugs.gnu.org; 27 Apr 2016 21:24:45 +0000 Received: from localhost ([127.0.0.1]:50833 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1avWwv-0003V7-Bc for submit@debbugs.gnu.org; Wed, 27 Apr 2016 17:24:45 -0400 Received: from hermes.netfonds.no ([80.91.224.195]:50720) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1avWwu-0003V0-Id for control@debbugs.gnu.org; Wed, 27 Apr 2016 17:24:44 -0400 Received: from cm-84.215.1.64.getinternet.no ([84.215.1.64] helo=mouse) by hermes.netfonds.no with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1avWws-0003oS-Fz for control@debbugs.gnu.org; Wed, 27 Apr 2016 23:24:44 +0200 Date: Wed, 27 Apr 2016 23:24:42 +0200 Message-Id: <8737q6u4md.fsf@gnus.org> To: control@debbugs.gnu.org From: Lars Ingebrigtsen Subject: control message for bug #3568 X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: control X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.0 (/) close 3568 From debbugs-submit-bounces@debbugs.gnu.org Thu Apr 28 01:08:11 2016 Received: (at 3568) by debbugs.gnu.org; 28 Apr 2016 05:08:11 +0000 Received: from localhost ([127.0.0.1]:51059 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1aveBL-0005Tf-SE for submit@debbugs.gnu.org; Thu, 28 Apr 2016 01:08:11 -0400 Received: from eggs.gnu.org ([208.118.235.92]:58604) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1aveBH-0005T6-5z for 3568@debbugs.gnu.org; Thu, 28 Apr 2016 01:08:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aveB8-00077N-0W for 3568@debbugs.gnu.org; Thu, 28 Apr 2016 01:07:57 -0400 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_50,RP_MATCHES_RCVD autolearn=disabled version=3.3.2 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:38630) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aveB7-00077J-Ta; Thu, 28 Apr 2016 01:07:53 -0400 Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3477 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aveB7-0004FL-2v; Thu, 28 Apr 2016 01:07:53 -0400 Date: Thu, 28 Apr 2016 08:07:40 +0300 Message-Id: <83h9emxqw3.fsf@gnu.org> From: Eli Zaretskii To: Drew Adams In-reply-to: (message from Drew Adams on Wed, 27 Apr 2016 14:18:20 -0700 (PDT)) Subject: Re: bug#3568: 23.0.94; no doc for character composition References: < <87potadfe9.fsf@gnus.org>> <<623906f5-d8d6-416b-b435-7f3b0f44944a@default>> <<83mvoeyfpx.fsf@gnu.org>> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-Spam-Score: -6.0 (------) X-Debbugs-Envelope-To: 3568 Cc: 3568@debbugs.gnu.org, larsi@gnus.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Eli Zaretskii Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -6.0 (------) > Date: Wed, 27 Apr 2016 14:18:20 -0700 (PDT) > From: Drew Adams > Cc: larsi@gnus.org, 3568@debbugs.gnu.org > > > > What the bug report mentions. I don't think that a doc string for > > > one command covers this topic. > > > > Well, I think it does. You could change my mind by telling what is it > > that you miss in that doc string. > > I'd like an explanation of character composition, in the Elisp manual. Would copying the doc string of compose-region into the manual do what you want? If not, what in that doc string is missing or not explained well enough? > As one user, I know nothing about this. And I still know nothing > about it after reading that doc string. FWIW. I don't understand this claim. You certainly know what the doc string says, which is definitely not "nothing". Is this a serious bug report? If it is, would you please help me understand what is missing in the documentation, by at least answering my questions, if not by elaborating some more about the problem? TIA. From unknown Wed Jun 25 03:52:29 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Thu, 26 May 2016 11:24:04 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator