all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Tury <tury.peter@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: avoid interpretation of \n, \t, ... in string
Date: Wed, 28 Jan 2009 02:16:19 -0800 (PST)	[thread overview]
Message-ID: <a65852ec-d978-477f-b10d-e42247744577@p29g2000vbn.googlegroups.com> (raw)
In-Reply-To: mailman.6050.1233129149.26697.help-gnu-emacs@gnu.org

Hi,

On Jan 28, 8:52 am, Kevin Rodgers <kevin.d.rodg...@gmail.com> 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


      parent reply	other threads:[~2009-01-28 10:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 17:13 avoid interpretation of \n, \t, ... in string Peter Tury
2009-01-27 18:26 ` Peter Dyballa
     [not found] ` <mailman.5991.1233080786.26697.help-gnu-emacs@gnu.org>
2009-01-27 18:38   ` Peter Tury
2009-01-28  7:52 ` Kevin Rodgers
2009-01-28  9:59 ` Pascal J. Bourguignon
2009-01-28 12:24   ` Peter Tury
2009-01-28 14:02     ` Pascal J. Bourguignon
     [not found] ` <mailman.6050.1233129149.26697.help-gnu-emacs@gnu.org>
2009-01-28 10:16   ` Peter Tury [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a65852ec-d978-477f-b10d-e42247744577@p29g2000vbn.googlegroups.com \
    --to=tury.peter@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.