zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: named directory expansion on strings
Date: Sat, 13 Mar 2004 06:41:00 +0000	[thread overview]
Message-ID: <1040313064100.ZM28748@candle.brasslantern.com> (raw)
In-Reply-To: <v5mfocam7x43.dlg@thorstenkampe.de>

On Mar 13,  4:29am, Thorsten Kampe wrote:
}
} Is there a way to perform "named directory" expansion on strings?

Sort of.  See "print" in "man zshbuiltins" and look at the -D option.

} Something like "autonamedirs" and the "%~" in the prompt...
} 
} % file=/etc/foo
} % ETCDIR=/etc
} % echo `bar#!$whatever($file)`

I take it that the stuff in backticks is something that you just made up
to represent an arbitrary cryptic zsh incantation?

} ~ETCDIR/foo

You'd never get that in this particular example.  "ETCDIR" has six letters,
plus the tilde makes seven.  "/etc" has four letters.  Zsh always chooses
whichever one is shorter.

If you did

% setopt auto_name_dirs
% file=/etc/foo
% E=/etc
% print -D $file

Then you'd get

~E/foo

because ~E has only two letters.


  reply	other threads:[~2004-03-13  6:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-13  3:29 Thorsten Kampe
2004-03-13  6:41 ` Bart Schaefer [this message]
2004-03-13 17:48   ` Thorsten Kampe
2004-03-14 18:54     ` Bart Schaefer
2004-03-14 21:24       ` Thorsten Kampe
2004-03-14 21:57       ` Python/zsh/perl [was: named directory expansion on strings] Vincent Stemen
2004-03-15  4:00         ` Jos Backus
2004-03-15  7:04         ` [OT]Python/zsh/perl " Bob Schmertz
2004-03-15 23:37           ` [OT]Python/zsh/perl Vincent Stemen
2004-03-17  4:03           ` [OT]Python/zsh/perl [was: named directory expansion on strings] Eric Mangold
2004-03-14 22:19       ` named directory expansion on strings Thorsten Kampe
2004-03-14 23:19         ` Bart Schaefer

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=1040313064100.ZM28748@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@sunsite.dk \
    /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 public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).