From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: History for query replace pairs Date: Sun, 09 Nov 2014 00:51:38 +0200 Organization: JURTA Message-ID: <87wq75nw5i.fsf@mail.jurta.org> References: <87ppe4zv0t.fsf@mail.jurta.org> <87k34ba5sn.fsf@mail.jurta.org> <87siiq4gpv.fsf@mail.jurta.org> <87iojduj9n.fsf@mail.jurta.org> <87k33nyirh.fsf@mail.jurta.org> <87sii0becx.fsf@lifelogs.com> <87ioivx2xk.fsf@mail.jurta.org> <87h9yfaihq.fsf@lifelogs.com> <87zjc6pnpg.fsf@mail.jurta.org> <87r3xhnsjb.fsf@mail.jurta.org> <87zjc2pou7.fsf@mail.jurta.org> <87zjc2fqx2.fsf@lifelogs.com> <83oasiqduw.fsf@gnu.org> <87ioiq7yre.fsf@mail.jurta.org> <83ioiqq6j8.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1415487338 32536 80.91.229.3 (8 Nov 2014 22:55:38 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 8 Nov 2014 22:55:38 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 08 23:55:35 2014 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 1XnEut-00050X-9l for ged-emacs-devel@m.gmane.org; Sat, 08 Nov 2014 23:55:35 +0100 Original-Received: from localhost ([::1]:37038 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XnEut-000283-0w for ged-emacs-devel@m.gmane.org; Sat, 08 Nov 2014 17:55:35 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47731) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XnEuP-0001aq-RG for emacs-devel@gnu.org; Sat, 08 Nov 2014 17:55:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XnEuJ-0001mJ-N3 for emacs-devel@gnu.org; Sat, 08 Nov 2014 17:55:05 -0500 Original-Received: from ps18281.dreamhost.com ([69.163.222.226]:35236 helo=ps18281.dreamhostps.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XnEu0-0001ib-NO; Sat, 08 Nov 2014 17:54:40 -0500 Original-Received: from localhost.jurta.org (ps18281.dreamhostps.com [69.163.222.226]) by ps18281.dreamhostps.com (Postfix) with ESMTP id B2899348328E50; Sat, 8 Nov 2014 14:54:39 -0800 (PST) In-Reply-To: <83ioiqq6j8.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 08 Nov 2014 13:24:27 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (x86_64-pc-linux-gnu) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 69.163.222.226 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:176597 Archived-At: > I'm okay with delaying the changes in the manual, but as for NEWS, you > cannot expect people who track the trunk to start using something > about which they have no hints at all. At the very least, post some > initial information here. Also, NEWS can explain features that have > no expression at all in user-level options; as long as there are > user-visible changes in behavior or keybindings or their meaning, this > is definitely NEWS-worthy stuff. I just added a few lines about this feature to NEWS. > You could do that test only in interactive calls It seems the only remaining place to use char-displayable-p is in the interactive call, and like isearch-text-char-description replaces every character for its display representation, this code could do something similar to convert the characters to be displayable: (setq query-replace-from-to-separator (propertize query-replace-from-to-separator 'display (mapconcat (lambda (c) (if (or (char-displayable-p c) (not (eq c ?\u2192))) (char-to-string c) "->")) (get-text-property 0 'display query-replace-from-to-separator) ""))) Or maybe better would be to create two variables with different versions of the separator?