From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Rusi Newsgroups: gmane.emacs.help Subject: Re: if vs. when vs. and: style question Date: Wed, 25 Mar 2015 09:19:28 -0700 (PDT) Message-ID: References: <87sicvwckx.fsf@wmi.amu.edu.pl> <87wq27yvqg.fsf@debian.uxu> <8d531e99-7260-4263-ac99-09c6871e2708@googlegroups.com> <87vbhq53lf.fsf@debian.uxu> <87a8z23p23.fsf@kuiper.lan.informatimago.com> <87lhilx0cf.fsf@debian.uxu> <87twx9360u.fsf@kuiper.lan.informatimago.com> <0d1d19ab-06e9-462d-8867-9a49b1e232d3@googlegroups.com> <87lhil2io1.fsf@kuiper.lan.informatimago.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: ger.gmane.org 1427300429 28859 80.91.229.3 (25 Mar 2015 16:20:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 25 Mar 2015 16:20:29 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Mar 25 17:20:29 2015 Return-path: Envelope-to: geh-help-gnu-emacs@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 1Yao2Z-0000PW-Vb for geh-help-gnu-emacs@m.gmane.org; Wed, 25 Mar 2015 17:20:24 +0100 Original-Received: from localhost ([::1]:40139 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yao2Z-0000sf-9o for geh-help-gnu-emacs@m.gmane.org; Wed, 25 Mar 2015 12:20:23 -0400 X-Received: by 10.42.89.205 with SMTP id h13mr31156231icm.25.1427300369262; Wed, 25 Mar 2015 09:19:29 -0700 (PDT) X-Received: by 10.50.43.234 with SMTP id z10mr441941igl.8.1427300369250; Wed, 25 Mar 2015 09:19:29 -0700 (PDT) Original-Path: usenet.stanford.edu!z20no4870474igj.0!news-out.google.com!qk8ni67122igc.0!nntp.google.com!z20no3194716igj.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=117.195.49.60; posting-account=mBpa7woAAAAGLEWUUKpmbxm-Quu5D8ui Original-NNTP-Posting-Host: 117.195.49.60 User-Agent: G2/1.0 Injection-Date: Wed, 25 Mar 2015 16:19:29 +0000 Original-Xref: usenet.stanford.edu gnu.emacs.help:211047 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:103328 Archived-At: On Wednesday, March 25, 2015 at 9:36:37 PM UTC+5:30, Drew Adams wrote: > > Notice, that I asked the reader to compare the ease of input. > > Before I comment further, let me say that I agree with your point. > > > => super easy, two keys to type. > > The unicode correspondance? I would start typing C-x 8 RET double TAB > > and not find it in the list. So I would have to launch clisp, > > C-- slime RET clisp RET > > wait for it to boot then type: > > (lschar :name "RIGHT_ARROW") RET > > the search for double, and not find it, then copy and paste it from your > > message, > > (char-name #\=>) > > obtain the character name as "RIGHTWARDS_DOUBLE_ARROW", then type > > C-x 8 RET rightward double arrow RET > > which, even if I had know it from the start, is still much more > > difficult to type than just =>. > > Yes and no. Yes, if you haven't used a particular Unicode char > before or use it rarely. No, if you use it often. > > If you use a particular Unicode character often, just give its > insertion a command and bind that to a key. If you have 30 such > chars, put them all on a prefix key. Or use completion on their > command names (names you created, so easy for you to type, remember, > complete to,...). > > IOW, it's not a big deal to insert Unicode characters, especially > if you insert the same ones over and over. You do not need to use > `C-x 8 RET' each time. You get the point better Drew -- thanks! ASCII (7-bit) is roughly 100 chars Full (currently defined) Unicode is 100,000 chars Choosing to go beyond ASCII does not imply an XOR: 100 or 100,000 and nothing else!! One can choose one's preferred subset with varying degrees of 'accessibility' In particular for the char => I have https://github.com/rrthomas/pointless-xcompose installed After that => is 3 chars "M=>" (M is the menu ie compose key)