unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Trastabuga <lispercat@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: File manipulation in elisp?
Date: Wed, 20 Jun 2007 10:35:03 -0700	[thread overview]
Message-ID: <1182360903.792302.111830@i13g2000prf.googlegroups.com> (raw)

Is there an API for file management in elisp without opening files in
buffers?
What I want to do is have some special file in a directory which would
give my elisp some post-compile commands for this particular
directory. So every time I compile a project, as a post-build step I
want to look for some pre-defined file in the directory, read its
content, evaluate the content into elisp and execute it.
All I could find was insert-file-contents which is not exactly what I
need. I need something like with-open-file macro.

Thank you,
Andrew

             reply	other threads:[~2007-06-20 17:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-20 17:35 Trastabuga [this message]
2007-06-20 19:05 ` File manipulation in elisp? Stefan Monnier
2007-06-20 20:19   ` Trastabuga
2007-06-21  1:59     ` Barry Margolin

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=1182360903.792302.111830@i13g2000prf.googlegroups.com \
    --to=lispercat@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).