From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Peter Tury Newsgroups: gmane.emacs.help Subject: Re: avoid interpretation of \n, \t, ... in string Date: Wed, 28 Jan 2009 02:16:19 -0800 (PST) Organization: http://groups.google.com Message-ID: References: <665cbb9b-8140-489e-a4d8-a15acce224be@r37g2000prr.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1233139637 28914 80.91.229.12 (28 Jan 2009 10:47:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 28 Jan 2009 10:47:17 +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 Jan 28 11:48:31 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LS7y9-0002DM-I8 for geh-help-gnu-emacs@m.gmane.org; Wed, 28 Jan 2009 11:48:29 +0100 Original-Received: from localhost ([127.0.0.1]:34412 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LS7wr-0000RN-Lk for geh-help-gnu-emacs@m.gmane.org; Wed, 28 Jan 2009 05:47:09 -0500 Original-Path: news.stanford.edu!newsfeed.stanford.edu!postnews.google.com!p29g2000vbn.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 22 Original-NNTP-Posting-Host: 194.237.142.6 Original-X-Trace: posting.google.com 1233137780 8191 127.0.0.1 (28 Jan 2009 10:16:20 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Wed, 28 Jan 2009 10:16:20 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: p29g2000vbn.googlegroups.com; posting-host=194.237.142.6; posting-account=Xb8sGQoAAABwL3BYvXXbA1TD0PsAYrcM User-Agent: G2/1.0 X-HTTP-UserAgent: Opera/9.61 (Windows NT 6.0; U; en) Presto/2.1.1,gzip(gfe),gzip(gfe) Original-Xref: news.stanford.edu gnu.emacs.help:166406 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:61726 Archived-At: Hi, On Jan 28, 8:52=A0am, Kevin Rodgers wrote: > Where do these strings come from? You see the key! I would like to have my "elisp script" usable by people knowing nothing about Emacs. That is why I would like to avoid the evident solution: work as if paths are always in correct elisp form (i.e., in the example above: "c:\\directory-1\\new-dir\\temp"). While I type the paths myself I can put the extra backslashes of course. However, it would be nice to have this functionality automated. At first step the paths would come from .el files, e.g. one elisp function would get a list of paths, so when you call it you should pass something like `(list "c:\\directory-1\\new-dir\\temp")'. Later they might come from external .txt files... Thanks, P