From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcin Borkowski Subject: Re: How to represent Emacs keystrokes in Org? Date: Thu, 19 Mar 2015 22:48:30 +0100 Message-ID: <87sid01wwh.fsf@wmi.amu.edu.pl> References: <87vbm4fvce.fsf@wmi.amu.edu.pl> <87tx1o8mwj.fsf@gmx.us> <87bnnpisgq.fsf@wmi.amu.edu.pl> <87a939is9j.fsf@wmi.amu.edu.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59348) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YYiJ1-0005q5-Et for emacs-orgmode@gnu.org; Thu, 19 Mar 2015 17:48:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YYiIx-0001aS-A8 for emacs-orgmode@gnu.org; Thu, 19 Mar 2015 17:48:43 -0400 Received: from msg.wmi.amu.edu.pl ([2001:808:114:2::50]:34470) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YYiIw-0001Z6-Uv for emacs-orgmode@gnu.org; Thu, 19 Mar 2015 17:48:39 -0400 Received: from localhost (localhost [127.0.0.1]) by msg.wmi.amu.edu.pl (Postfix) with ESMTP id E5D7F5AE90 for ; Thu, 19 Mar 2015 22:48:36 +0100 (CET) Received: from msg.wmi.amu.edu.pl ([127.0.0.1]) by localhost (msg.wmi.amu.edu.pl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k48PwG7VDOry for ; Thu, 19 Mar 2015 22:48:36 +0100 (CET) Received: from localhost (117-116.echostar.pl [213.156.117.116]) by msg.wmi.amu.edu.pl (Postfix) with ESMTPSA id 6E9385AE8F for ; Thu, 19 Mar 2015 22:48:36 +0100 (CET) In-reply-to: <87a939is9j.fsf@wmi.amu.edu.pl> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hi there, it seems that reviving old threads is my new hobby;-). On 2014-11-29, at 22:58, Marcin Borkowski wrote: > On 2014-11-29, at 22:53, Marcin Borkowski wrote: > >> On 2014-11-24, at 19:38, Rasmus wrote: >> >>> Marcin Borkowski writes: >>> >>>> Hello, >>>> >>>> I'm writing (in Org) a text on Emacs usage. How to >>>> correctly/canonically represent keystrokes, like "C-x RET f"? >>>> Currently, I use =3DC-x RET f=3D; are there any alternatives? >>> >>> That's what I'd do. Or ~C-x RET f~. You could also use a macro, if = you >>> want it to me be more semantic (I hope I use this word correctly). This might seem a good idea, but how do I do it? (See below for a concrete problem statement.) >> Houston, we've got a problem. What about =3DM-,=3D? Somehow it seems= not >> to be interpreted in the right way: it does not get fontified correctl= y, >> nor does export in the right way. What can I do about it? I found >> about org-emphasis-regexp-components, is it the only way? Also, how d= o >> I reload Org without restarting Emacs? (I am an Emacs geek and I try = to >> beat my record of emacs-uptime, you know. ;-) ) > > Wow, I got an idea, and it worked. Here's an excerpt from `C-u C-x =3D= ' > at my solution;-): > > position: 11859 of 16051 (74%), column: 253 > character: =E2=80=8D (displayed as =E2=80=8D) (codepoint 82= 05, #o20015, #x200d) > preferred charset: unicode (Unicode (ISO10646)) > code point in charset: 0x200D > syntax: . which means: punctuation > to input: type "C-x 8 RET HEX-CODEPOINT" or "C-x 8 RET NAM= E" > buffer code: #xE2 #x80 #x8D > file code: #xE2 #x80 #x8D (encoded by coding system utf-8-u= nix) > display: by this font (glyph code) > xft:-unknown-Phetsarath OT-normal-normal-normal-*-17-*-*-*-*-0-iso1= 0646-1 (#x120) > > Character code properties: customize what to show > name: ZERO WIDTH JOINER > > A bit ugly trick, but works. What are the opinions? After a while I have to say that my opinion is strongly negative: this breaks LaTeX export. (LaTeX doesn=E2=80=99t like some unicode characters= , it turns out.) Also, this was really an ugly hack... So, here is my problem: how to represent a key like M-, or e.g. a sequence \, (important in regexps) as =E2=80=9Ccode=E2=80=9D or =E2= =80=9Cverbatim stuff=E2=80=9D in org-mode? Neither =3D\,=3D nor ~\,~ work, of course. Also, I=E2=80=99= d like this to be backend-agnostic, so \texttt{M-,} doesn=E2=80=99t really work. What is the rationale behind forbidding the comma as the =E2=80=9Cborder=E2= =80=9D character in org-emphasis-regexp-components? Should I change this variable in my setup or is there a more general way to convince Org that I really want verbatim/code snippets like =3D\,=3D? Best, --=20 Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University