emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Herbert Sitz <hsitz@nwlink.com>
To: emacs-orgmode@gnu.org
Subject: Re: tangle paths
Date: Mon, 27 Jun 2011 19:46:44 +0000 (UTC)	[thread overview]
Message-ID: <loom.20110627T214234-659@post.gmane.org> (raw)
In-Reply-To: 87liwrhz6g.fsf@gmail.com

Eric Schulte <schulte.eric <at> gmail.com> writes:
> skip <scp0801 <at> gmail.com> writes:
> > Is there a way I can produce output of tangle blocks to specific file paths?
> >
> The manual is useful: http://orgmode.org/manual/tangle.html

Eric --

I was wondering similar thing, but manual wasn't clearing things up for me.  As
far as I know, 'basename' conventionally refers to a filename (root plus
extension) that does _not_ include a directory path to the file itself.  See,
e.g., http://en.wikipedia.org/wiki/Basename

Is the manual using 'basename' to refer to a full path designation, minus the
extension?  E.g.,


-- Herb 

  reply	other threads:[~2011-06-27 19:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24 12:13 tangle paths skip
2011-06-24 18:13 ` Eric Schulte
2011-06-27 19:46   ` Herbert Sitz [this message]
2011-06-28 20:28     ` Eric Schulte
2011-06-28  2:05 ` Herbert Sitz

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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=loom.20110627T214234-659@post.gmane.org \
    --to=hsitz@nwlink.com \
    --cc=emacs-orgmode@gnu.org \


* 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 public inbox


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).