From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Matthew Plant Newsgroups: gmane.emacs.devel Subject: Re: Raw string literals in Emacs lisp. Date: Wed, 30 Jul 2014 14:19:07 -0700 Message-ID: References: <878ungor1v.fsf@uwakimon.sk.tsukuba.ac.jp> <8761ijng08.fsf@uwakimon.sk.tsukuba.ac.jp> <871tt7lzro.fsf@fencepost.gnu.org> <53D567FD.4030708@porkrind.org> <87r412iobp.fsf@lifelogs.com> <53D9586F.6020705@porkrind.org> <87bns6in3g.fsf@lifelogs.com> <877g2uim3h.fsf@lifelogs.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=e89a8f8397ade06b3f04ff6fb4d6 X-Trace: ger.gmane.org 1406755165 24526 80.91.229.3 (30 Jul 2014 21:19:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 30 Jul 2014 21:19:25 +0000 (UTC) To: "emacs-devel@gnu.org" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 30 23:19:20 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 1XCbHL-0002Ln-UD for ged-emacs-devel@m.gmane.org; Wed, 30 Jul 2014 23:19:20 +0200 Original-Received: from localhost ([::1]:53267 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XCbHL-0005PP-Ft for ged-emacs-devel@m.gmane.org; Wed, 30 Jul 2014 17:19:19 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49632) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XCbHF-0005OP-B2 for emacs-devel@gnu.org; Wed, 30 Jul 2014 17:19:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XCbHB-0001BV-9E for emacs-devel@gnu.org; Wed, 30 Jul 2014 17:19:13 -0400 Original-Received: from mail-lb0-f177.google.com ([209.85.217.177]:53867) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XCbHB-0001BH-1m for emacs-devel@gnu.org; Wed, 30 Jul 2014 17:19:09 -0400 Original-Received: by mail-lb0-f177.google.com with SMTP id s7so1352608lbd.36 for ; Wed, 30 Jul 2014 14:19:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=OB/ctvIBnqGlGGOxDDf+c5sgTCV1HtvS7dUz5Wvyq9U=; b=F0PyeEu5fjZy5d6g/AKMFJ8f1oSj57N+WUx2oHaanvFDbiZUQi1yWm+2N8AE5p8zlt h6qY0LBdHEgN1Uwamfgbq97se1KKofeVRwMmU2+hMpJQm+adIYvlELc82ro7AVxA4e5w gVea26z9gHShh5fexgoGEAFSMcHypF4JkpR2TaezSdU0zNg7jVIwZZhpBaa9iB816dqH dRnZCJlOsPYGoQv9XboIR+1z8JHugwgOa7h4wx/xeEXz0uijGYmeww18i8KdNlCZwXQG y2VBqFmZVSIpKT5cOiV5wV5Hpfwv1KEruYlMIa3uQGqA5thwov6feFxePRYKEaiPXGpF hVdw== X-Gm-Message-State: ALoCoQkov874aei41pNKtv/IeX58jOgCWYhweEORV6KudYB/9igSn4KZx+l3995l1+jpxFPLT68M X-Received: by 10.112.60.5 with SMTP id d5mr7303551lbr.26.1406755147894; Wed, 30 Jul 2014 14:19:07 -0700 (PDT) Original-Received: by 10.112.185.99 with HTTP; Wed, 30 Jul 2014 14:19:07 -0700 (PDT) In-Reply-To: <877g2uim3h.fsf@lifelogs.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 209.85.217.177 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:173303 Archived-At: --e89a8f8397ade06b3f04ff6fb4d6 Content-Type: text/plain; charset=UTF-8 > Maybe LEFT DOUBLE ANGLE BRACKET and RIGHT DOUBLE ANGLE BRACKET would work (they look like << and >>). I'm pretty sure that those look like existing ASCII characters as well ;-) On Wed, Jul 30, 2014 at 2:16 PM, Ted Zlatanov wrote: > On Wed, 30 Jul 2014 14:01:52 -0700 Matthew Plant > wrote: > > >> How about using a Unicode character as the marker? (prepares for > stoning) > MP> I'm on the fence about this idea. It certainly would make parsing in > MP> reverse possible (assuming the reverse parsing functions do not > operate on > MP> char *) and easy, but it would also possibly mess up formatting. It > also > MP> might not add much convenience because frankly typing non-unicode > MP> characters is _hard_. > > Eh, it's really not hard. If it was the only problem with this approach, > it could be enabled in the default keybindings. > > MP> One suggestion would be to use the unicode left and right > double/single > MP> quotation marks. > > Oh, no. The markers shouldn't look like existing ASCII characters or > there will be lynchings. Maybe LEFT DOUBLE ANGLE BRACKET and RIGHT > DOUBLE ANGLE BRACKET would work (they look like << and >>). > > Ted > > > --e89a8f8397ade06b3f04ff6fb4d6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
> Maybe LEFT DOUBLE ANGLE BRACKET and RIGHT
DOUBLE ANGLE BRACKET would work (they look like << and >>).

I'm pretty sure that those look like existing ASCII characters as well = ;-)


On Wed, Jul 30, 2014 at 2:16 PM, Ted Zlatanov <tzz@lifelogs.com= > wrote:
On Wed, 30 Jul 2014 14:01:52= -0700 Matthew Plant <maplant2@= illinois.edu> wrote:

>> How about using a Unicode character as the marker? (prepares for s= toning)
MP> I'm on the fence about this idea. It certainly would make = parsing in
MP> reverse possible (assuming the reverse parsing functions do not oper= ate on
MP> char *) and easy, but it would also possibly mess up formatting. It = also
MP> might not add much convenience because frankly typing non-unicode MP> characters is _hard_.

Eh, it's really not hard. If it was the only problem with this approach= ,
it could be enabled in the default keybindings.

MP> =C2=A0One suggestion would be to use the unicode left and right doub= le/single
MP> quotation marks.

Oh, no. The markers shouldn't look like existing ASCII characters or there will be lynchings. Maybe LEFT DOUBLE ANGLE BRACKET and RIGHT
DOUBLE ANGLE BRACKET would work (they look like << and >>).

Ted



--e89a8f8397ade06b3f04ff6fb4d6--